Programme Lifecycle
The programme lifecycle provides a structured approach to delivering transformational change, from initial identification of the need through to realising benefits and closing the programme.
Programme Lifecycle Overview
a Programme] --> B[Defining
a Programme] B --> C[Managing
the Tranches] C --> D[Closing
a Programme] C -.-> C classDef blue fill:#108BB9,stroke:none,color:#fff class A,B,C,D blue
| Phase | Purpose | Duration |
|---|---|---|
| Identifying | Establish need and viability | 2-4 weeks |
| Defining | Plan the programme | 4-12 weeks |
| Managing Tranches | Deliver the change | Months to years |
| Closing | Transition and close | 4-8 weeks |
Identifying a Programme
Purpose
Confirm there is a viable programme that will achieve the strategic objectives and deliver the required benefits.
Need] --> B[Mandate] B --> C[Programme
Brief] C --> D[Approval to
Define] classDef blue fill:#108BB9,stroke:none,color:#fff class A,B,C,D blue
Key Activities
| Activity | Description |
|---|---|
| Appoint SRO | Identify and appoint Senior Responsible Owner |
| Confirm mandate | Obtain executive mandate for programme |
| Develop brief | Create Programme Brief |
| Outline vision | Define Vision Statement |
| Initial assessment | High-level benefits and risks |
| Approval | Decision to proceed to definition |
Key Deliverables
| Deliverable | Description | Link |
|---|---|---|
| Programme Mandate | Authority to investigate | Template |
| Programme Brief | Summary of programme | Template |
| Vision Statement | Description of end state | Template |
| Sponsoring Group Terms of Reference | Governance structure | Guide |
Gate: Approval to Define
| Criteria | Evidence |
|---|---|
| Strategic alignment clear | Vision Statement |
| SRO appointed | Mandate signed |
| Resources for definition | Budget approved |
| Viability confirmed | Programme Brief |
Defining a Programme
Purpose
Establish the programme’s governance, organisation, plans, and controls, providing a solid foundation for delivery.
Brief] --> B[Blueprint] B --> C[Benefit
Profiles] C --> D[Programme
Plan] D --> E[Business
Case] E --> F[Approval to
Deliver] classDef blue fill:#108BB9,stroke:none,color:#fff class A,B,C,D,E,F blue
Key Activities
| Activity | Description |
|---|---|
| Design Blueprint | Define future state using POPIT model |
| Identify benefits | Create Benefit Profiles and Map |
| Plan tranches | Develop Programme Plan |
| Establish governance | Set up Programme Board and PMO |
| Develop business case | Create detailed Business Case |
| Design projects | Define constituent projects |
| Risk assessment | Identify and assess programme risks |
Key Deliverables
| Deliverable | Description | Link |
|---|---|---|
| Blueprint | Future state definition (POPIT) | Template |
| Benefit Profiles | Individual benefit definitions | Template |
| Benefits Map | Benefits dependency network | Guide |
| Programme Plan | High-level schedule | Template |
| Business Case | Investment justification | Template |
| Governance Framework | Roles, boards, controls | Guide |
| Stakeholder Map | Stakeholder analysis | Template |
| Risk Register | Programme-level risks | Template |
| Quality Management Strategy | Quality approach | Guide |
Gate: Approval to Deliver
| Criteria | Evidence |
|---|---|
| Blueprint complete | POPIT model defined |
| Benefits quantified | Benefit Profiles complete |
| Business Case positive | NPV/ROI acceptable |
| Risks acceptable | Risk Register reviewed |
| Resources identified | Resource plan in place |
| Governance established | Board and PMO in place |
Managing the Tranches
Purpose
Deliver the programme through coordinated tranches, each delivering a step-change in capability and benefits.
Tranche Structure
| Element | Description |
|---|---|
| Tranche | Group of projects delivering related capabilities |
| Transition | Moving to new operational state |
| Benefits Review | Assessing benefits realised |
Key Activities
| Activity | Description |
|---|---|
| Manage projects | Coordinate constituent projects |
| Monitor progress | Track against Programme Plan |
| Manage transitions | Embed changes into operations |
| Realise benefits | Track and measure benefits |
| Manage risks | Monitor and respond to risks |
| Stakeholder engagement | Maintain support and manage resistance |
| Update business case | Refresh forecasts |
| Governance | Regular board meetings, assurance |
Key Deliverables
| Deliverable | Description | Link |
|---|---|---|
| Tranche Plan | Detailed tranche schedule | Template |
| Project Briefs | Initiation of projects | Guide |
| Highlight Reports | Regular progress reports | Template |
| Transition Plans | Operational transition | Template |
| Benefits Realisation Reports | Benefits tracking | Template |
| End Tranche Reports | Tranche completion | Template |
| Updated Business Case | Refreshed justification | Guide |
Tranche Review Gate
| Criteria | Evidence |
|---|---|
| Tranche objectives met | End Tranche Report |
| Benefits on track | Benefits Realisation Report |
| Business case valid | Updated Business Case |
| Risks acceptable | Risk Register |
| Next tranche planned | Tranche Plan |
Closing a Programme
Purpose
Confirm that the programme has delivered its objectives, transition to business as usual, and formally close.
Transition] --> B[Benefits
Confirmed] B --> C[Lessons
Captured] C --> D[Programme
Closed] classDef blue fill:#108BB9,stroke:none,color:#fff class A,B,C,D blue
Key Activities
| Activity | Description |
|---|---|
| Final transition | Complete handover to operations |
| Confirm benefits | Final benefits assessment |
| Lessons learned | Capture and share learning |
| Close projects | Ensure all projects closed |
| Release resources | Return resources to organisation |
| Archive documentation | Store programme records |
| Formal closure | Programme Board sign-off |
Key Deliverables
| Deliverable | Description | Link |
|---|---|---|
| End Programme Report | Final programme report | Template |
| Benefits Realisation Review | Final benefits assessment | Template |
| Lessons Learned Report | Captured learning | Template |
| Handover Documentation | Operational handover | Guide |
| Closure Notification | Formal closure | Template |
Gate: Programme Closure
| Criteria | Evidence |
|---|---|
| Objectives achieved | End Programme Report |
| Benefits realised/on track | Benefits Review |
| Operations stable | Handover complete |
| Lessons captured | Lessons Learned Report |
| Board approval | Closure sign-off |
Ongoing Processes
These processes run throughout the programme lifecycle:
Lifecycle] --> B[Benefits Management] A --> C[Stakeholder Engagement] A --> D[Risk Management] A --> E[Quality Management] A --> F[Issue Management] A --> G[Information Management] classDef blue fill:#108BB9,stroke:none,color:#fff class A,B,C,D,E,F,G blue
| Process | Purpose | Link |
|---|---|---|
| Benefits Management | Track and realise benefits | Guide |
| Stakeholder Engagement | Manage stakeholders | Guide |
| Risk Management | Identify and manage risks | Guide |
| Quality Management | Ensure quality | Guide |
| Issue Management | Resolve issues | Guide |
| Information Management | Manage programme information | Guide |
Lifecycle Comparison
Programme vs Project Lifecycle
| Aspect | Project | Programme |
|---|---|---|
| Duration | Months | Years |
| Focus | Outputs | Outcomes |
| Structure | Stages | Tranches |
| Benefits | Enabled | Realised |
| Change | Controlled | Embraced |
| Scope | Fixed | Evolving |
Lifecycle Alignment
Programme Healthcheck
Use the Programme Healthcheck to assess programme health at any point in the lifecycle:
| Phase | Focus Areas |
|---|---|
| Identifying | Vision clarity, stakeholder support |
| Defining | Blueprint quality, benefit definition |
| Tranches | Delivery progress, benefit realisation |
| Closing | Transition success, lessons captured |
Related Resources
- Programme Governance - Governance framework
- Blueprint - Future state definition
- Stakeholder Management - Stakeholder engagement
- Programme Healthcheck - Health assessment
- Project Lifecycle - Project lifecycle comparison