POSTER 16
Section 6 · Program Management — Foundations
Programs & Benefits Management
A program is a group of related projects, subsidiary programs & activities managed together to obtain benefits not available by managing them individually. Program management is about coordinated delivery for benefits — the components are related, and together they create synergy.
Project · Program · Portfolio
| Lens | Manages… | Delivers | Question |
|---|---|---|---|
| Project | a defined scope | an output / deliverable | build it right |
| Program | related components & their interdependencies | benefits & capabilities | realise the benefit |
| Portfolio | all work, related or not | strategic alignment | the right mix |
Why a program (not just projects)? synergy · manage interdependencies · optimise shared resources · deliver outcomes too big for one project.
The Value Chain (program-owned)
Output
component delivers ▸ Capability
ability to act ▸ Outcome
change in state ▸ Benefit
measurable gain
component delivers ▸ Capability
ability to act ▸ Outcome
change in state ▸ Benefit
measurable gain
Components produce outputs → integrated into capabilities → used to create outcomes → realised as benefits. Projects stop at outputs; programs push through to benefits.
Visual Map — The Benefits Management Life Cycle
1 · Identify
quantify & justify (business case) ▸ 2 · Analyse & Plan
benefits register, plan, metrics, map ▸ 3 · Deliver
components → capabilities ▸ 4 · Transition
integrate into operations / BAU ▸ 5 · Sustain
benefits endure after closure
quantify & justify (business case) ▸ 2 · Analyse & Plan
benefits register, plan, metrics, map ▸ 3 · Deliver
components → capabilities ▸ 4 · Transition
integrate into operations / BAU ▸ 5 · Sustain
benefits endure after closure
The benefits realisation plan & benefits register are the living artifacts. Each benefit has an owner and leading/lagging measures. Sustainment is the giveaway that programs care about value beyond the program's own life.
Exam Concepts
- Programs exist for benefits & relatedness, not size alone.
- Capability is delivered by a component; the benefit is realised in operations.
- Benefits transition hands capability to BAU; sustainment continues after closure.
- Benefits have owners & metrics — measured, not assumed.
Executive View
- Programs convert strategy → capability → benefit.
- The sponsor cares about outcomes, not outputs.
- Governance gates are benefit-driven — fund what realises value.
Industry Example
Defence
- A frigate capability program: shipbuild + combat-system + training/sustainment components. Benefit = a deployable, supportable naval capability — sustained over decades, not just a hull delivered.
Relationships
- Realises the PMBOK 7 value delivery system (Poster 4) at program scale.
- BA's solution evaluation (Poster 10) feeds benefit measurement.
- Sits beneath the portfolio (Posters 18–19) and above projects.
Memory Hooks
- "Projects make outputs; programs make BENEFITS."
- Benefits cycle — I·A·D·T·S: Identify → Analyse/plan → Deliver → Transition → Sustain.
- "A program is related; a portfolio is aligned."
60-sec Review
Define a program
Output→capability→benefit
5 benefits-cycle stages
Transition vs sustainment
Program vs portfolio
PMI Visual Wall · Poster 16 · Program — Fundamentals & Benefits · original instructional design · A3 landscape