High-yield PgMP review for key rules, traps, decision cues, formulas, and final-week reminders.
Use this as your last-mile PgMP® review. Pair it with the Syllabus for coverage and Practice for speed.
For domain weights and official exam snapshot, see Overview.
flowchart TD
A["Strategic objectives"] --> B["Program charter + mission"]
B --> C["Roadmap (projects/components)"]
C --> D["Integrated execution + controls"]
D --> E["Benefits measurement + sustainment"]
E --> F["Transition to operations"]
F --> G["Benefits realized and sustained"]
D --> C
Best-answer reflex: choose the next step that protects the benefits path and keeps governance traceability intact.
| If the scenario is really about… | Stronger answer pattern | Weaker answer pattern |
|---|---|---|
| why the program exists | go back to business case and charter logic | jump straight into component execution |
| how value will be realized | use benefits ownership, measures, and roadmap logic | treat deliverables as if they were benefits |
| whether leadership should approve the next move | use the stage-gate path and decision pack | bypass governance because the team already agrees |
| whether closure is complete | check sustainment, ownership, and post-close measurement | hand off documents and assume benefits will persist |
| Concept | Focus | Success signal |
|---|---|---|
| Project | deliver outputs | scope/schedule/cost/quality met; acceptance achieved |
| Program | realize benefits through coordinated components | outcomes/value achieved and sustained |
| Portfolio | select and prioritize investments | strategic fit and optimized allocation |
| If the question is about… | Reach for… | Why (concept) |
|---|---|---|
| strategic justification | business case + program charter | explains why this program exists |
| direction and intent | mission statement | sets decision principles |
| sequencing to value | roadmap (milestones + dependencies) | shows path to benefits |
| benefits definition/verification | benefits realization plan + benefits register | outcomes, owners, measures |
| stakeholder alignment | stakeholder matrix + engagement plan | influence + approach |
| governance and approvals | stage gate pack + decision log | auditable decisions |
| information consistency | PMIS + reporting standards | reliable, comparable data |
| operational ownership | transition + sustainment plan | benefits persist after closure |
| Need | Reach for | Not mainly for |
|---|---|---|
| define mission, scope, authority, and strategic reason | charter | sequencing detailed component work |
| show path, dependencies, and timing to value | roadmap | proving operational ownership |
| define benefit measures, owners, and timing | benefits realization plan or register | replacing governance approvals |
Stage gates are approval points. A typical pack includes:
Elimination rule: answers that bypass governance when approval is implied are often wrong.
| Situation | Better move | Weak move |
|---|---|---|
| the program needs approval to continue or redirect | stage-gate decision with clear trade-offs | informal team decision only |
| a component issue affects the benefits path | update roadmap, impacts, and gate information | treat it as a local project issue only |
| stakeholders disagree on benefits logic | reset benefit ownership and measures | focus on output completion only |
| Field | Meaning |
|---|---|
| Benefit name | outcome/value statement |
| Owner | accountable operational owner |
| Measure | KPI or metric definition |
| Baseline | starting point |
| Target | expected level |
| Timing | when measured/realized |
| Dependencies | prerequisites and risks |
| Sustainment | how it persists (process/tool/role) |
Best-answer reflex: correct the system (adoption, process, ownership), not just deliver more output.
Return on investment (ROI), concept:
\[ \text{ROI}=\frac{\text{Net Benefit}}{\text{Cost}} \]
Net present value (NPV), concept:
\[ \text{NPV}=\sum_{t=0}^{T}\frac{CF_t}{(1+r)^t} \]
Benefit-cost ratio (BCR), concept:
\[ \text{BCR}=\frac{\text{PV(Benefits)}}{\text{PV(Costs)}} \]
Payback period (concept): time until cumulative net cash flow becomes non-negative.
Operational transition checklist:
| Term | Meaning (concept) | Common trap |
|---|---|---|
| Benefit | measurable outcome/value | confusing it with deliverables |
| Benefit owner | accountable operational leader | leaving ownership with the program team |
| Roadmap | sequencing to value | treating it like a static schedule |
| Stage gate | governance approval point | bypassing it when approval is implied |
| PMIS | shared information system | inconsistent data across components |
| Sustainment | maintaining outcomes post-close | assuming benefits persist automatically |