PgMP® Cheatsheet — Program Artifacts, Decision Rules, Checklists & Glossary

High-yield PgMP® review: program artifacts (charter/roadmap/benefits plan), governance and stage gates, stakeholder engagement tools, benefits measurement and sustainment checklists, and a practical glossary.

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.


Program management in one picture (benefits path)

    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.


Program vs project vs portfolio (fast distinctions)

ConceptFocusSuccess signal
Projectdeliver outputsscope/schedule/cost/quality met; acceptance achieved
Programrealize benefits through coordinated componentsoutcomes/value achieved and sustained
Portfolioselect and prioritize investmentsstrategic fit and optimized allocation

High-yield program artifacts (what to reach for)

If the question is about…Reach for…Why (concept)
strategic justificationbusiness case + program charterexplains why this program exists
direction and intentmission statementsets decision principles
sequencing to valueroadmap (milestones + dependencies)shows path to benefits
benefits definition/verificationbenefits realization plan + benefits registeroutcomes, owners, measures
stakeholder alignmentstakeholder matrix + engagement planinfluence + approach
governance and approvalsstage gate pack + decision logauditable decisions
information consistencyPMIS + reporting standardsreliable, comparable data
operational ownershiptransition + sustainment planbenefits persist after closure

Stage gate reviews (what governance expects)

Stage gates are approval points. A typical pack includes:

  • current status vs plan (scope/schedule/cost/quality)
  • benefits outlook (value realized vs expected; forecast)
  • top risks/issues + escalations needed
  • decision requested (go/hold/redirect) + trade-offs
  • updated roadmap impacts (dependencies, milestones, funding)

Elimination rule: answers that bypass governance when approval is implied are often wrong.


Stakeholder tools (quick patterns)

Stakeholder matrix (simple model)

  • Influence (high/low) × Interest (high/low)
  • Position (supporter/neutral/resister)
  • Engagement strategy (inform/consult/collaborate/empower)

Negotiation checklist (support + acceptance criteria)

  • Define what “support” means (time, approvals, resources, decisions).
  • Set acceptance criteria for benefits (KPIs + measurement method).
  • Confirm decision rights and escalation paths.

Benefits management (core PgMP muscle)

Benefits register (minimum fields)

FieldMeaning
Benefit nameoutcome/value statement
Owneraccountable operational owner
MeasureKPI or metric definition
Baselinestarting point
Targetexpected level
Timingwhen measured/realized
Dependenciesprerequisites and risks
Sustainmenthow it persists (process/tool/role)

Benefit drift signals

  • adoption below expectation
  • capability delivered but not used
  • leading indicators degrade (quality, cycle time, customer outcomes)
  • operational owner not engaged

Best-answer reflex: correct the system (adoption, process, ownership), not just deliver more output.


Simple value formulas (for program cases)

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.


Program controls (what to do when things drift)

Variance thinking (fast)

  • Identify variance (what moved?)
  • Diagnose root cause (why?)
  • Decide corrective action (what changes?)
  • Update plans and communicate through governance (who approves?)

Common corrective actions

  • re-sequence roadmap milestones
  • shift resources across components
  • reduce scope to protect benefits-critical work
  • strengthen risk responses and contingencies
  • adjust transition/adoption work to sustain outcomes

Program closure and transition (must not be an afterthought)

Operational transition checklist:

  • ownership assigned (roles + responsibilities)
  • training and knowledge transfer complete
  • support model defined (SLAs, escalation)
  • documentation archived and accessible
  • benefits measurement continues post-close

Glossary (high-yield terms)

TermMeaning (concept)Common trap
Benefitmeasurable outcome/valueconfusing it with deliverables
Benefit owneraccountable operational leaderleaving ownership with the program team
Roadmapsequencing to valuetreating it like a static schedule
Stage gategovernance approval pointbypassing it when approval is implied
PMISshared information systeminconsistent data across components
Sustainmentmaintaining outcomes post-closeassuming benefits persist automatically