MSP Practice - lifecycle, governance and the practice areas
The practice dimension is where MSP's delivery machinery sits: the programme lifecycle, its governance and assurance arrangements, and the practice areas that must be run well (programme strategy and direction, programme planning, benefits management, risk and issue management, stakeholder engagement, quality and assurance, and the management of the programme's information and reporting). Knowledge of how these practices interact matters more than memorising document names.
Concepts to know
- Lifecycle. Identify the programme → define it → deliver the tranches → close. A tranche is a group of projects and activities whose outputs together deliver a step-change in capability; tranche boundaries are decision points where the business case, blueprint and plan are re-confirmed before the next tranche commits investment.
- Blueprint vs. business case vs. benefits map. The blueprint describes the future operating model (target state); the business case justifies the investment and shows expected benefits, costs, risks and timescales; the benefits map links outputs → capabilities/outcomes → benefits → strategic objectives.
- Benefits management. Benefits need an owner, a measurable definition, a realisation plan and evidence. Outputs are not benefits; capability is what enables benefits.
- Governance and assurance. Direction, decision-making and oversight sit with the programme board; assurance gives independent confidence that the programme is on track and claims are credible.
Traps
- Confusing outputs with benefits. "Delivered a new CRM" is an output; "reduced customer response time" is a benefit.
- Tranche vs. stage vs. project phase. Tranches belong to the programme and end in a benefit step-change; projects plan their own phases.
- Assuming the business case is written once. It should be refreshed at tranche boundaries and when material change occurs.
- Treating assurance as the same as audit or as project testing. Assurance is independent and decision-focused.
Rule of thumb
At any tranche boundary ask three questions: is the case still worth it, is the blueprint still achievable, and is the next tranche planned and resourced? Worked example: a programme discovers a new regulatory constraint mid-tranche; the correct action is to update the business case and blueprint and take a decision at the next boundary - not to silently re-baseline the plan.