How to Use This Quick Reference
This independent Quick Reference supports candidates preparing for the PMI Program Management Professional (PgMP), exam code PgMP. Use it to review how PMI expects a program manager to think: strategically, benefit-first, governance-aware, and focused on coordinated outcomes across related components.
High-yield PgMP mindset:
| If the scenario says… | Think first… | Avoid… |
|---|
| A component is late or over budget | Impact on program benefits, dependencies, roadmap, governance thresholds | Managing the component like the project manager |
| Stakeholders disagree | Analyze influence, expectations, engagement gaps, and communication needs | Picking the loudest stakeholder’s preference |
| Sponsor wants a scope change | Assess strategic alignment, benefits, risks, funding, and governance approval | Adding work informally |
| Benefits are not appearing | Check adoption, transition, measurement, ownership, and benefit assumptions | Assuming deliverables equal benefits |
| Strategy changes | Revalidate business case, roadmap, components, and benefits | Continuing because the program was already approved |
| A risk crosses a threshold | Escalate through the approved governance path | Hiding, delaying, or solving outside authority |
| Multiple projects conflict for resources | Optimize at program level against benefits and priorities | First-come, first-served allocation |
Program, Project, Portfolio: Exam Distinctions
| Concept | Primary purpose | Success measured by | PgMP exam cue |
|---|
| Project | Create a unique product, service, or result | Scope, schedule, cost, quality, stakeholder satisfaction | Temporary effort with defined deliverable |
| Program | Coordinate related components to obtain benefits not available from managing them separately | Benefits realization, strategic alignment, integrated outcomes, stakeholder value | Related projects/subprograms/operations with shared outcomes |
| Portfolio | Select, prioritize, and govern investments to achieve strategy | Strategic value, balance, risk, return, resource optimization | Investment mix, prioritization, funding allocation |
| Operations | Sustain ongoing business | Stable performance, service levels, efficiency | Receives transitioned capabilities and sustains benefits |
PgMP “Best Answer” Pattern
- Confirm alignment with organizational strategy.
- Evaluate impact on benefits, stakeholders, risks, dependencies, and governance.
- Use approved plans, thresholds, and decision rights.
- Collaborate with the right role before escalating.
- Update program artifacts and communicate decisions.
- Escalate only when authority, threshold, or strategic impact requires it.
Core Program Performance Domains
| Domain | What the program manager does | Key artifacts | Common exam traps |
|---|
| Strategic alignment | Keeps the program tied to organizational objectives and portfolio priorities | Business case, program charter, roadmap, strategic alignment assessment | Continuing a program after strategy or value assumptions no longer support it |
| Benefits management | Identifies, plans, delivers, transitions, and sustains benefits | Benefits realization plan, benefits register, benefits map, KPI dashboard | Confusing outputs, capabilities, outcomes, and benefits |
| Stakeholder engagement | Identifies, analyzes, engages, and communicates with stakeholders across the program | Stakeholder register, engagement plan, communications plan | Communicating only with sponsors or only after problems occur |
| Governance | Establishes decision rights, escalation paths, oversight, controls, and compliance | Governance plan, decision log, change control records, issue/risk thresholds | Treating governance as bureaucracy rather than value protection |
| Program life cycle management | Coordinates components from definition through delivery and closure | Program management plan, roadmap, component register, dependency register, transition plan | Managing component tasks instead of interdependencies and benefits |
Program Life Cycle Reference
| Phase / activity group | Main purpose | Program manager focus | Outputs / evidence |
|---|
| Pre-program / opportunity identification | Determine whether a program is justified | Strategic fit, value proposition, high-level benefits, initial stakeholders | Opportunity statement, initial business case inputs |
| Program definition | Authorize and shape the program | Charter, sponsor support, governance model, initial roadmap, funding approach | Program charter, business case, initial stakeholder analysis |
| Program preparation | Build the management foundation | Plans, benefits framework, component structure, risk and dependency approach | Program management plan, benefits realization plan, governance plan |
| Benefits delivery | Coordinate components to create capabilities and outcomes | Dependency management, issue/risk control, stakeholder engagement, benefit tracking | Benefit reports, roadmap updates, change decisions |
| Transition | Move capabilities into operations or receiving organizations | Adoption, training, operational readiness, handover acceptance | Transition plan, acceptance records, sustainment ownership |
| Program closure | Close or transition the program when objectives are met or no longer justified | Benefit sustainment, component closure, lessons learned, resource release | Closure report, archived records, final benefits status |
Lifecycle Decision Cues
| Scenario cue | Best program-level response |
|---|
| Program is not yet authorized | Develop or validate the business case and charter; secure sponsorship |
| Components are proposed | Confirm they contribute to program benefits and strategic outcomes |
| Work is underway but benefits are unclear | Revisit benefits map, measures, assumptions, and ownership |
| Deliverables are complete but users are not adopting | Strengthen transition, change management, training, and operational readiness |
| Strategy changes mid-program | Reassess alignment and recommend continue, modify, pause, or terminate through governance |
| Benefits will continue after closure | Transfer ownership, metrics, and sustainment responsibilities to operations or benefit owners |
Role and Responsibility Matrix
| Role | Primary responsibility | Program manager interaction |
|---|
| Program sponsor | Champions the program, secures support, owns strategic justification | Keep informed of strategic risks, benefit status, escalated decisions |
| Program manager | Coordinates components to deliver strategic benefits | Leads integration, governance execution, stakeholder engagement, benefit tracking |
| Program governance board / steering committee | Provides oversight, decision authority, prioritization, and escalation resolution | Submit decisions exceeding authority or thresholds |
| Portfolio manager | Balances investments and priorities across the organization | Align program with portfolio strategy, funding, and priorities |
| Component project manager | Delivers project scope within the program | Coordinate dependencies, milestones, risks, and changes without micromanaging |
| Subprogram manager | Manages a subset of related components | Align subprogram outcomes with overall program benefits |
| Benefits owner | Accountable for realizing and sustaining a benefit | Define measures, targets, ownership, reporting, and transition accountability |
| PMO | Provides standards, methods, tools, and reporting support | Use organizational processes; request support for consistency and governance |
| Operations / receiving organization | Uses transitioned capabilities to realize sustained value | Confirm readiness, adoption, support model, and benefit measurement |
| Key stakeholders | Influence, receive, fund, regulate, support, or resist outcomes | Analyze needs, expectations, power, interest, and engagement level |
Artifact Selection Matrix
| Need | Use this artifact | What it should answer |
|---|
| Justify the program | Business case | Why this program, why now, what value, what alternatives |
| Formally authorize the program | Program charter | Who sponsors it, what outcomes are expected, who has authority |
| Show sequencing and direction | Program roadmap | What capabilities/components occur when and why |
| Track components | Component register | Which projects/subprograms/operations are in the program and their status |
| Link work to value | Benefits realization plan | Which benefits, owners, metrics, baselines, targets, timing |
| Manage benefit details | Benefits register | Benefit description, measure, owner, dependency, status, risk |
| Control decisions | Governance plan | Decision rights, thresholds, escalation paths, reporting cadence |
| Coordinate related work | Dependency register | Cross-component dependencies, owners, dates, constraints, impacts |
| Manage uncertainty | Risk register | Threats/opportunities, responses, owners, triggers, residual risk |
| Handle active problems | Issue log | Current issue, owner, due date, resolution path, escalation status |
| Manage stakeholders | Stakeholder register | Influence, interest, expectations, engagement, communication needs |
| Communicate consistently | Communications plan | Audience, message, method, frequency, owner |
| Control approved direction | Change log / decision log | What changed, why, who approved, impact on baselines and benefits |
| Transition capabilities | Transition plan | Readiness, acceptance, training, support, benefit ownership |
| Close the program | Closure report | Final status, benefits disposition, lessons, resource release |
Benefits Management Quick Reference
Benefits Chain
| Level | Meaning | Example cue |
|---|
| Output | Deliverable produced by a component | New customer portal deployed |
| Capability | New ability enabled by outputs | Customers can self-serve account changes |
| Outcome | Changed business result or behavior | Fewer calls to service center |
| Benefit | Measurable value from the outcome | Lower service cost, higher satisfaction |
| Strategic objective | Organizational goal supported by benefits | Improve customer retention |
Benefits Management Steps
| Step | Program manager focus | Exam emphasis |
|---|
| Identify | Define expected benefits and link to strategy | Benefits must be explicit, measurable, and owned |
| Analyze and plan | Establish baselines, targets, timing, dependencies, and assumptions | A weak metric makes realization hard to prove |
| Deliver | Coordinate components that create capabilities | Component completion does not guarantee benefit realization |
| Transition | Transfer capability and measurement responsibility to operations | Benefits often occur after project closure |
| Sustain | Monitor continued realization and corrective action | Ownership must remain after program closure |
Benefit Metric Design
| Good metric characteristic | Ask |
|---|
| Strategic | Does it support an approved objective? |
| Measurable | Is there a baseline, target, and data source? |
| Time-bound | When should value appear? |
| Owned | Who is accountable for realization? |
| Traceable | Which components and capabilities enable it? |
| Controllable enough | Can the program influence it? |
| Sustainable | Who monitors it after transition? |
Benefits Traps
| Trap | Better PgMP answer |
|---|
| “The project delivered, so the benefit is realized.” | Verify adoption, outcomes, and metric movement |
| “Benefits belong only to the sponsor.” | Sponsors support; benefit owners and operations often sustain |
| “All benefits are financial.” | Benefits may be financial, strategic, compliance-related, operational, customer, social, or risk-reduction oriented |
| “Benefits are fixed once approved.” | Reassess when strategy, assumptions, risks, or stakeholders change |
| “Negative outcomes are just risks.” | Disbenefits should be identified, managed, and communicated |
Governance and Escalation
Governance protects strategic value. On PgMP questions, use governance when decisions exceed program manager authority, affect strategic alignment, change benefits, alter funding, cross thresholds, or create major stakeholder impact.
flowchart TD
A[Trigger: change, risk, issue, conflict, or opportunity] --> B{Within program manager authority and thresholds?}
B -- Yes --> C[Analyze impact on benefits, roadmap, dependencies, stakeholders]
C --> D[Take action per approved plan]
D --> E[Update artifacts and communicate]
B -- No --> F[Prepare recommendation with options and impacts]
F --> G[Escalate to sponsor or governance board]
G --> H[Record decision]
H --> I[Update plans, baselines, roadmap, and communications]
Governance Decision Table
| Situation | Program manager should… | Usually should not… |
|---|
| Component requests major scope change | Assess program benefit, dependency, risk, schedule, cost, and governance impact | Approve solely because component sponsor wants it |
| Sponsor bypasses change process | Explain governance impact and route decision through approved authority | Publicly challenge or ignore the sponsor |
| Benefits no longer justify cost | Prepare options: realign, descope, pause, terminate, or continue with rationale | Continue without transparent review |
| Cross-component conflict cannot be resolved | Facilitate resolution; escalate if authority or thresholds require | Let component PMs fight it out indefinitely |
| Regulatory/compliance concern appears | Assess impact, involve appropriate experts, escalate per governance | Treat as ordinary low-level project issue |
| Risk exceeds tolerance | Activate response and escalate per threshold | Wait for the next routine status meeting if urgent |
| Governance board decision conflicts with program data | Present evidence, options, assumptions, and consequences | Make the decision alone if it exceeds authority |
Change Control at Program Level
| Change type | Program-level concern | Likely decision path |
|---|
| Component scope change | Does it affect program benefits, dependencies, roadmap, or funding? | Component control first, then program review if impact crosses boundaries |
| Program roadmap change | Does sequencing still optimize benefits and constraints? | Program governance review |
| Benefit target change | Is the business case still valid? | Sponsor/governance approval |
| Funding change | Which components or benefits are affected? | Portfolio/sponsor/governance decision |
| Strategic priority change | Should the program continue, pivot, or close? | Portfolio and governance review |
| Stakeholder-driven change | Does it add value or just satisfy preference? | Analyze impact and decide through approved process |
Change Impact Checklist
Before recommending approval or rejection, check:
- Strategic alignment
- Benefit value, timing, and ownership
- Component scope, schedule, cost, quality, and risk
- Cross-component dependencies
- Resource and funding constraints
- Stakeholder impact and communication needs
- Operational readiness and transition impact
- Contract, compliance, security, or policy implications
- Governance thresholds and decision rights
Stakeholder Engagement
| Tool / lens | Use when… | Exam cue |
|---|
| Power-interest grid | Prioritizing communication and engagement | High power/high interest stakeholders require close management |
| Influence-impact grid | Understanding ability to affect outcomes | Influential resistors can threaten benefits |
| Salience model | Assessing power, legitimacy, urgency | Urgent legitimate concerns need timely response |
| Engagement assessment | Comparing current vs desired engagement | Move resistant or unaware stakeholders toward supportive/leading |
| Communications matrix | Matching message, medium, frequency, owner | Different stakeholders need different information |
Engagement Responses
| Stakeholder state | Best response |
|---|
| Unaware | Educate on program purpose, benefits, and impact |
| Resistant | Understand concerns, involve early, address impacts, use sponsor support when appropriate |
| Neutral | Provide targeted information and show relevance |
| Supportive | Keep informed and engaged; use as advocate if appropriate |
| Leading | Empower to champion adoption and benefit realization |
Common Stakeholder Scenarios
| Scenario | Best program manager action |
|---|
| Business unit resists transition | Engage leaders, identify adoption barriers, update transition and communications plans |
| Executive demands optimistic reporting | Report transparently with facts, impacts, options, and risks |
| Component teams receive conflicting priorities | Align priorities to program benefits and roadmap; escalate unresolved conflicts |
| Stakeholder group was missed | Update stakeholder register, assess impact, adjust engagement plan |
| Stakeholder wants direct control over component work | Clarify roles, decision rights, and governance path |
Risk, Issue, and Dependency Management
| Concept | Definition | Program-level focus |
|---|
| Risk | Uncertain event or condition that may affect objectives | Aggregate threats/opportunities across components and benefits |
| Issue | Current condition requiring action | Resolve or escalate based on impact and authority |
| Dependency | Relationship where one activity/component depends on another | Sequence, monitor, and manage cross-component impacts |
| Assumption | Something considered true for planning | Validate; convert uncertainty into risk when needed |
| Constraint | Limiting factor | Optimize within or escalate if benefits are threatened |
Program Risk Types
| Risk type | Example | Response focus |
|---|
| Strategic risk | Strategy changes or market shifts | Revalidate alignment and business case |
| Benefit risk | Expected value may not be realized | Adjust components, transition, metrics, or adoption approach |
| Dependency risk | One component delay affects several others | Resequence, add mitigation, escalate resource conflicts |
| Resource risk | Scarce experts needed by multiple components | Prioritize by benefit and governance direction |
| Stakeholder risk | Resistance blocks adoption | Engagement, sponsorship, change management |
| Governance risk | Slow or unclear decisions threaten value | Clarify thresholds, cadence, and authority |
| Operational risk | Receiving organization not ready | Transition planning and readiness checks |
| Compliance risk | Policy or regulatory expectation may be missed | Involve experts and escalate promptly |
Risk Response Quick Reference
| Threat response | Meaning |
|---|
| Avoid | Change plan to eliminate the threat |
| Mitigate | Reduce probability or impact |
| Transfer | Shift ownership or financial impact to another party |
| Accept | Acknowledge and monitor; may use contingency |
| Escalate | Move outside program authority to appropriate level |
| Opportunity response | Meaning |
|---|
| Exploit | Ensure the opportunity occurs |
| Enhance | Increase probability or impact |
| Share | Partner to capture benefit |
| Accept | Take advantage if it occurs |
| Escalate | Move outside program authority to appropriate level |
Use formulas as decision support, not as a substitute for governance judgment.
Earned Value
\[
\begin{aligned}
\text{CV} &= \text{EV} - \text{AC} \\
\text{SV} &= \text{EV} - \text{PV} \\
\text{CPI} &= \frac{\text{EV}}{\text{AC}} \\
\text{SPI} &= \frac{\text{EV}}{\text{PV}}
\end{aligned}
\]
| Metric | Interpretation |
|---|
| CV greater than 0 | Under budget |
| CV less than 0 | Over budget |
| SV greater than 0 | Ahead of schedule in earned value terms |
| SV less than 0 | Behind schedule in earned value terms |
| CPI greater than 1 | Cost efficiency favorable |
| CPI less than 1 | Cost efficiency unfavorable |
| SPI greater than 1 | Schedule efficiency favorable |
| SPI less than 1 | Schedule efficiency unfavorable |
Forecasting
\[
\begin{aligned}
\text{EAC} &= \frac{\text{BAC}}{\text{CPI}} \\
\text{ETC} &= \text{EAC} - \text{AC} \\
\text{VAC} &= \text{BAC} - \text{EAC}
\end{aligned}
\]
Use earned value carefully at program level. A component can be on budget while the program is still failing to realize benefits.
Risk and Expected Monetary Value
\[
\text{Risk Exposure} = \text{Probability} \times \text{Impact}
\]\[
\text{EMV} = \sum(\text{Probability of outcome} \times \text{Monetary impact of outcome})
\]
| Use | PgMP relevance |
|---|
| Compare risk responses | Choose response proportionate to exposure |
| Analyze decision trees | Support governance recommendations |
| Aggregate component risk | Understand program-level exposure |
| Evaluate opportunities | Include upside value, not only threats |
Benefits and Investment Measures
\[
\text{ROI} = \frac{\text{Total Benefits} - \text{Total Costs}}{\text{Total Costs}} \times 100
\]\[
\text{BCR} = \frac{\text{Benefits}}{\text{Costs}}
\]\[
\text{NPV} = \sum_{t=1}^{n}\frac{\text{Cash Flow}_t}{(1+r)^t} - \text{Initial Investment}
\]
| Measure | Favorable signal | Trap |
|---|
| ROI | Higher positive return | Ignores timing if used alone |
| BCR | Greater than 1 suggests benefits exceed costs | Does not show absolute value or strategic fit |
| NPV | Higher positive value after discounting | Depends on assumptions and discount rate |
| Payback period | Shorter recovery time | Ignores value after payback |
| Weighted scoring | Higher weighted score | Can hide biased weights or weak criteria |
Agile, Predictive, and Hybrid Program Management
PgMP scenarios may include agile, predictive, or hybrid components. The program manager’s job remains benefit coordination, governance, stakeholder alignment, and dependency management.
| Situation | Program-level approach |
|---|
| High uncertainty and evolving requirements | Use iterative planning, adaptive roadmaps, frequent feedback, and benefit validation |
| Stable regulatory or infrastructure work | Predictive planning and formal controls may be appropriate |
| Mixed component delivery methods | Standardize reporting at program level without forcing identical team methods |
| Agile teams deliver increments | Track value, dependencies, integration, release readiness, and stakeholder feedback |
| Executive wants fixed benefits from uncertain work | Clarify assumptions, ranges, risks, and decision points |
| Component teams use different cadences | Align key milestones, integration points, and governance reviews |
Agile/Hybrid Traps
| Trap | Better answer |
|---|
| Program manager runs team standups | Let teams manage delivery; coordinate program-level impediments and dependencies |
| Agile means no governance | Tailor governance cadence and decision rights; do not remove accountability |
| Product increments equal benefits | Validate adoption, outcomes, and strategic value |
| Predictive plans never change | Use change control and reforecast when facts change |
| Hybrid means duplicate reporting only | Integrate information into useful program decisions |
“What Should the Program Manager Do Next?” Table
| Scenario | Best next action |
|---|
| A component delay may affect a major benefit milestone | Analyze dependency and benefit impact, coordinate recovery options, update risk/issue records, escalate if thresholds are crossed |
| A project manager requests more resources | Evaluate program priorities, resource constraints, benefit impact, and alternatives before reallocating |
| Sponsor asks to add a new component | Assess strategic alignment, business case, benefits, risks, funding, and governance approval needs |
| Governance board asks for a recommendation | Provide options with impacts, assumptions, risks, benefits, and preferred path |
| A benefit metric is not measurable | Work with benefit owner to define baseline, data source, target, timing, and reporting method |
| A stakeholder complains they were not consulted | Update stakeholder analysis, assess impact, engage directly, adjust communication plan |
| Component PM hides bad news | Reinforce transparent reporting, assess impact, update issue/risk logs, escalate if necessary |
| Program is delivering outputs but business value is declining | Reassess benefits and strategy; recommend corrective action or realignment |
| Two components have incompatible technical approaches | Facilitate integration analysis, involve experts, evaluate benefit/risk impact, escalate unresolved decisions |
| Team proposes a workaround outside policy | Assess risk/compliance impact and use approved governance path |
| Operations refuses handover | Determine readiness gaps, update transition plan, engage sponsor/operations leadership |
| A major opportunity appears | Analyze potential benefit, risk, cost, and strategic fit; submit recommendation through governance |
| Program manager lacks authority to solve conflict | Prepare facts and options; escalate to sponsor/governance board |
| Lessons from a component reveal systemic issue | Share across components, update plans and risk responses, prevent recurrence |
| Program objectives are achieved | Confirm benefit transition/sustainment, close components, archive records, release resources |
Reporting and Communication
Program Status Should Include
| Area | Useful content |
|---|
| Strategic alignment | Still aligned, at risk, or needing decision |
| Benefits | Planned vs actual/forecast, leading indicators, owner updates |
| Roadmap | Milestones, sequencing, dependency health |
| Components | Summary status, exceptions, cross-component impacts |
| Risks and issues | Top items, owners, response status, escalation needs |
| Changes | Approved/pending changes and benefit impact |
| Financials | Budget, forecast, variance, funding concerns |
| Stakeholders | Engagement risks, adoption readiness, communication actions |
| Decisions needed | Clear options, recommendation, deadline, consequences |
Communication Principles
| Principle | Exam application |
|---|
| Tailor to audience | Executives need decisions and impacts; teams need coordination details |
| Be transparent | Do not hide unfavorable information |
| Use the plan | Follow agreed cadence, channel, and escalation path |
| Communicate impact | Explain effect on benefits, strategy, risk, and stakeholders |
| Close the loop | Record decisions and confirm understanding |
Program Closure and Transition
| Closure concern | What to verify |
|---|
| Benefits | Realized, forecasted, transferred, or no longer valid |
| Ownership | Benefit owners and operations accept ongoing accountability |
| Components | Completed, closed, transitioned, or formally terminated |
| Contracts | Closed or transitioned according to approved process |
| Resources | Released or reassigned |
| Knowledge | Lessons learned captured and shared |
| Records | Program documentation archived |
| Stakeholders | Closure communicated and expectations managed |
| Unfinished value | Remaining benefits, risks, and actions assigned |
Close, Continue, Pause, or Terminate?
| Condition | Likely recommendation |
|---|
| Objectives met and sustainment owner ready | Close program after transition |
| Benefits still valid but components need adjustment | Continue with corrective action |
| Strategy uncertain or funding paused | Pause or replan through governance |
| Business case no longer valid | Recommend termination or major realignment |
| Benefits achieved before all planned work is done | Consider closing or descoping remaining work if no longer justified |
| Benefits cannot be measured | Fix measurement approach before claiming success |
Ethics and Professional Conduct Cues
PMI exam scenarios often reward professional, transparent, and responsible behavior.
| Scenario | Expected behavior |
|---|
| Conflict of interest | Disclose and follow organizational policy |
| Pressure to alter reports | Report accurately with evidence and context |
| Confidential information | Protect it and share only with authorized parties |
| Cultural or stakeholder conflict | Act respectfully and seek understanding |
| Unethical procurement or favoritism | Follow policy, document concerns, escalate appropriately |
| Safety, compliance, or legal concern | Treat seriously; involve appropriate authority |
Common PgMP Answer Traps
| Trap answer | Why it is weak |
|---|
| Immediately escalate every problem | Program managers should analyze and act within authority first |
| Personally fix a component task | Component managers own component delivery |
| Ignore governance to move faster | Governance protects strategic value and decision accountability |
| Focus only on schedule and cost | Programs are judged by benefits and strategic outcomes |
| Treat stakeholder communication as status distribution | Engagement is two-way and influence-based |
| Accept sponsor direction without analysis | Sponsor authority does not replace impact assessment and governance |
| Close when deliverables are complete | Closure requires transition, benefit ownership, and records |
| Continue because sunk cost is high | Decisions should be based on future value and strategic fit |
| Use one communication style for everyone | Stakeholders need tailored engagement |
| Assume agile eliminates planning | Adaptive programs still need roadmap, governance, and benefit tracking |
Final Review Checklist
Before exam day, make sure you can answer these quickly:
- What benefit does this program produce that separate projects would not?
- Who owns each benefit during and after transition?
- Which decision rights belong to the program manager, sponsor, governance board, portfolio, or component PM?
- What artifact would prove the decision, assumption, risk, change, or benefit?
- Does the best answer preserve strategic alignment?
- Is the issue inside or outside program manager authority?
- Are stakeholders being engaged, not merely informed?
- Are component metrics being translated into program benefit impact?
- Has the program manager analyzed before escalating?
- Does closure include sustainment and operational handover?
Practical Next Step
Use this Quick Reference as a scenario-review checklist: take a set of PgMP-style practice questions, identify the domain being tested, name the correct artifact or governance path, and explain why the best answer protects program benefits and strategic alignment.