MSP programme management
This domain tests whether you can direct a programme of business change rather than a large project. MSP defines a programme as a temporary, flexible organization created to coordinate, direct and oversee related projects and activities to deliver outcomes and benefits that serve strategic objectives. Programmes usually span several years and outlive any constituent project. Scenario questions ask you to apply principles, choose the right document or role, and explain why a benefit must be measurable.
Seven principles that drive decisions
- Lead with purpose – visible, consistent sponsorship around a clear vision.
- Collaborate across boundaries – business, programme and supplier interests aligned.
- Deal with ambiguity – programmes are inherently uncertain; plan progressively.
- Align with priorities – coherence with strategy and other change in the portfolio.
- Deploy diverse skills – blend operational and change capability.
- Realise measurable benefits – defined, baselined and tracked.
- Bring pace and value – early value release over completeness of bureaucracy.
Lifecycle and control points
Definition: a mandate (usually from the sponsoring group) is refined into a programme brief, then a vision, blueprint, business case and programme plan, forming the basis of tranche plans. Delivery: tranches group projects whose outputs create capability, which is transitioned into operational use; an end-of-tranche review re-tests the business case before the next tranche is authorized. Closure: capability is handed over, the benefits realisation plan passes to those who will measure the benefits, and benefits realisation continues after the programme disbands.
Features worth memorising
The benefits chain runs output → capability → outcome → benefit. A benefit profile states the benefit, its owner, measures with baseline and target, and dependencies. The MSP business case has four cases: economic, commercial, financial and management. The blueprint is the target operating model, not an aspiration statement – that is the vision.
Worked example
A city council runs a three-tranche "Digital First" programme. The SRO owns the business case; business change managers own benefit realisation. One benefit is "fewer telephone contacts": baseline 400,000 calls a year, target 280,000 within 18 months of tranche two. Projects deliver the self-service portal output; the blueprint described the to-be operating model, including retrained contact-centre staff. At the first tranche review, contacts have fallen only to 330,000, so the forecast is revised and the economic case re-assessed. Applying bring pace and value, the SRO releases a simple payments feature early rather than waiting for the full portal – because it already delivers measurable benefit.
Traps that cost marks
Treating benefit targets as project deliverables with no owner or baseline; mistaking the blueprint for the vision; keeping the programme open after handover instead of handing benefits to operations; skipping business case refresh at tranche boundaries; and assuming all benefits must be realised inside the programme's life.