Performance domains I — governance, scope, schedule

• QuestionWhat is "Governance domain"?Tap to revealAnswerGovernance is the system of who-decides-what. Make it appropriate for the project's risk and size.
• QuestionIn "Governance domain", explain:Tap to revealAnswerThree layers: portfolio / program / project governance.
• QuestionIn "Governance domain", explain:Tap to revealAnswerRight-sized governance: enough rigour, no bureaucracy.
• QuestionIn "Governance domain", explain:Tap to revealAnswerCCB / steering committee handles change requests above PM threshold.
• QuestionIn "Governance domain", explain:Tap to revealAnswerPM escalates when decision exceeds their authority or cross-program impact.
• QuestionWhat is "Scope domain (and the WBS)"?Tap to revealAnswerScope is what you're committed to building. The WBS lists it. Anything not on the list isn't your job.
• QuestionIn "Scope domain (and the WBS)", explain:Tap to revealAnswerWBS = hierarchical decomposition of *all* scope. Deliverable-oriented.
• QuestionIn "Scope domain (and the WBS)", explain:Tap to revealAnswer100% rule: WBS contains 100% of the work, nothing extra.
• QuestionIn "Scope domain (and the WBS)", explain:Tap to revealAnswerScope creep = uncontrolled stakeholder additions. Gold plating = team-added extras.
• QuestionIn "Scope domain (and the WBS)", explain:Tap to revealAnswerNot in WBS = not in scope.
• QuestionWhat is "Schedule domain (critical path basics)"?Tap to revealAnswerThe critical path is the chain that controls when you finish. To go faster, either spend more (crash) or take on risk (fast-track).
• QuestionIn "Schedule domain (critical path basics)", explain:Tap to revealAnswerCritical path = longest sequence; zero float.
• QuestionIn "Schedule domain (critical path basics)", explain:Tap to revealAnswerEstimate: analogous, parametric, PERT (3-point) = (O + 4M + P)/6.
• QuestionIn "Schedule domain (critical path basics)", explain:Tap to revealAnswerCompress: crash (more $, same risk profile) vs fast-track (more risk, same $).
• QuestionIn "Schedule domain (critical path basics)", explain:Tap to revealAnswerAdaptive uses velocity instead of date-based estimation.

1. 1Outline the core idea

   Analyse~10 min

   In your own words, outline the central idea of "Governance domain". Aim for one paragraph, no jargon you haven't earned.

   Done when: A non-expert could read your paragraph and explain it back to you.

   Re-read the source concept

2. 2Apply it to a real situation

   Apply~15 min

   Find a real situation from your own work / life where "Schedule domain (critical path basics)" applies. Apply the idea — describe the situation, the move you'd make, and the alternative you considered first.

   Done when: You can name a specific situation (not a hypothetical), state your move, and explain the trade-off in one paragraph.

   Re-read the source concept

3. 3Teach it back

   Evaluate~5 min

   Pick someone (a colleague, a peer, a rubber duck) and explain the section to them in under 5 minutes. Use your own example, not the one from the lesson.

   Done when: Your listener can repeat the core idea + the trade-off back to you without prompting.

Why this matters. Reading + quizzing prove recall; applying it in a real situation is the only evidence of transfer. Treat at least one of these as non-negotiable before you move on.