9.3 Process 3: Plan Progressive Delivery

9.3 Process 3: Plan Progressive Delivery

[!NOTE] Core MSP Lifecycle Definition: Plan Progressive Delivery is the third process within the MSP 5th edition lifecycle. Having defined what will be delivered in Process 2 (the Vision, TOM, and Benefit Profiles), Process 3 establishes how, when, in what sequence, and with what resources the transformation will be executed. It delivers the completed programme strategy, the baselined programme plans — including the delivery plan — and the governance baselines required to initiate delivery.

Designing a compelling Target Operating Model (TOM) and business case is meaningless if the enterprise lacks an achievable, disciplined plan to build and transition those capabilities into reality. Large-scale transformations frequently collapse not from flawed architectural vision, but from executing delivery in an uncoordinated, monolithic fashion that overwhelms operational capacity.

Process 3 directly resolves this execution challenge. By translating the design into staged delivery tranches, operationalizing rolling-wave planning, and establishing the seven core governance approaches, Process 3 creates the control framework needed to mobilize teams and commit capital with confidence.

---

Formulating the Overarching Programme Strategy (The 7 Governance Approaches)

In MSP 5th edition, a programme does not rely on ad-hoc project management rules. During Process 3, the Programme Manager, in close consultation with the Senior Responsible Owner (SRO) and Business Change Managers (BCMs), formulates the Programme Strategy.

The Programme Strategy is the master governance framework that consolidates seven specialized approaches, each derived from a core MSP Theme:

                             THE PROGRAMME STRATEGY
                 (Consolidated Operational & Governance Approaches)
       ┌─────────────────────────────────┼─────────────────────────────────┐
       ▼                                 ▼                                 ▼
[ DELIVERY APPROACH ]          [ RESOURCING APPROACH ]       [ STAKEHOLDER APPROACH ]
- Agile vs Linear vs Hybrid    - Internal vs External        - Stakeholder mapping
- Release rhythms & cadences   - Capacity modeling           - Engagement cadences
- Quality & acceptance gates   - Knowledge retention         - Resistance management
       │                                 │                                 │
       ├─────────────────────────────────┼─────────────────────────────────┤
       ▼                                 ▼                                 ▼
[ BENEFITS APPROACH ]          [ KNOWLEDGE APPROACH ]        [ ASSURANCE APPROACH ]
- Measurement protocols        - Digital asset management    - Three lines of defence
- Realization audits           - Lessons learned capture     - Gateway review points
- Post-transition tracking     - Configuration control       - Independent audits
                                         │
                                         ▼
                              [ DECISIONS APPROACH ]
                              - Risk appetite & escalation
                              - Issue management thresholds
                              - Decision Register protocols

The 7 Core Governance Approaches Detailed

---

Defining Delivery Tranches and Tranche Boundaries

A central mandate of Process 3 is decomposing the multi-year transformation into discrete, manageable stages called Tranches.

[!IMPORTANT] Definition of a Tranche in MSP: A tranche is a distinct, formal phase of programme delivery designed to group related projects and business change activities together to deliver a step-change in capability and enable the realization of a specific cohort of strategic benefits.

[ TRANCHE 1: Foundation & Early Wins ] ──► [ TRANCHE 1 GATE ] ──► [ TRANCHE 2: Enterprise Scaling ]
  - Cloud Infrastructure Build               Formal SRO Review      - Core System Cutover
  - Initial Workflow Redesign                 Benefits Audit        - Branch Network Transition
  - Pilot User Rollout                        Re-baseline Case      - Advanced Data Analytics

Why MSP Deploys Tranche-Based Delivery

• Mitigating Big-Bang Risk: Monolithic, single-cutover transformations carry catastrophic failure risks. Tranches allow the enterprise to transition incrementally, protecting business-as-usual from widespread operational disruption.
• Early Benefits Harvesting: Rather than waiting years for value, each tranche produces tangible capabilities that allow early benefits to be realized and reinvested.
• Continuous Learning & Adaptation: Lessons learned during early tranches directly refine the technical specifications, supplier contracts, and change approaches of subsequent tranches.
• Executive Governance Decision Gates: Tranches are separated by formal tranche review gates where the SRO and Sponsoring Group evaluate delivered capabilities, audit realized benefits, re-affirm continued business justification, and authorize capital for the next tranche.

The Operationalization of Rolling-Wave Planning

Process 3 applies rolling-wave planning to balance near-term execution certainty with long-term strategic adaptability:

1. The Near-Term Horizon (Tranche 1): Planned in exhaustive, granular detail. Project briefs are baselined, resources are named, supplier contracts are finalized, and exact operational transition schedules are established.
2. The Medium-Term Horizon (Tranche 2): Maintained at a directional, intermediate level of detail. Projects are scoped as indicative project briefs with broad resource estimates and dependency interfaces.
3. The Distant Horizon (Future Tranches): Maintained at a high-level, strategic milestone level aligned with the Target Operating Model. Granular details are deliberately deferred until the programme nears those tranche boundaries.

---

Constructing the Delivery Plan

Process 3 completes the five programme plans, of which the delivery plan is the one that integrates all delivery schedules and all commissioned work into a single control baseline.

1. The Delivery Plan as the Master Roadmap

The Delivery Plan is the authoritative programme-level schedule used by the Programme Manager to direct delivery and by the SRO to monitor progress against corporate strategy. Unlike a simple roll-up of daily project tasks, it coordinates multi-layered transformational dimensions:

• Tranche Horizons & Decision Gates: Schedule of formal tranche review gates and Sponsoring Group re-authorization windows.
• Project Timelines: Major deliverable milestones, testing windows, and handover dates for all constituent projects.
• Business Change & Transition Windows: Scheduled operational activities essential for adoption—such as staff retraining, operational dry-runs, union consultations, dual-running periods, and legacy asset decommissioning.
• Operational Blackout Windows: Business-as-usual operational constraints (e.g., peak retail holiday trading freezes, financial year-end accounting closes, seasonal clinical surges) during which no systems can be cut over.
• The Cross-Project Critical Path: The single continuous sequence of dependent project outputs and operational transitions that dictates the earliest possible completion of a tranche or the overall transformation.
• Benefits Realization Milestones: Scheduled points where intermediate operational performance improvements will be formally measured by the BCMs.

2. The Delivery Plan as the Record of Commissioned Work

As well as coordinating time and dependencies, the Delivery Plan is the record of every project and every other piece of work commissioned under the programme. In MSP 4th edition this content sat in a separate projects dossier; in the 5th edition it is part of the same delivery plan.

                               DELIVERY PLAN: WORK RECORDS
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │  PROJECT MANDATES  │ Authorizes project startup and defines initial scope    │
 ├────────────────────┼─────────────────────────────────────────────────────────┤
 │  PROJECT BRIEFS    │ Baselines project scope, deliverables, budget & risks   │
 ├────────────────────┼─────────────────────────────────────────────────────────┤
 │  DELIVERABLE MATRIX│ Maps project outputs directly to Target Operating Model │
 ├────────────────────┼─────────────────────────────────────────────────────────┤
 │  HEALTH DASHBOARDS │ Regular RAG status reports on schedule, cost, and risk  │
 └─────────────────────────────────────────────────────────────────────────────┘

The Delivery Plan provides complete deliverable traceability: every project output in the dossier maps directly to a capability facet in the Target Operating Model and an outcome on the Benefits Map.

---

Resource Mobilization and Financial Commitments

Before delivery begins, the programme must secure physical, financial, and digital resources:

• Tranche 1 Capital Release: While the Programme Business Case models the multi-year investment, the Sponsoring Group formally commits and releases capital on a tranche-by-tranche basis. Process 3 establishes the financial drawdown schedule and budget tolerances for Tranche 1.
• Mobilizing the Programme Office (PMO): Establishing PMO facilities, scheduling software, risk registers, document repositories, and communication channels.
• Commercial Procurement & Supplier Onboarding: Finalizing vendor contracts, establishing service level agreements (SLAs), and defining intellectual property and knowledge transfer requirements.

---

The Formal Decision Gate: Approval to Deliver Tranche 1

Process 3 culminates at a decisive, formal executive review gate. The Programme Board reviews the assembled baselines, and the Senior Responsible Owner (SRO) presents the package to the Sponsoring Group for formal authorization.

                    ┌────────────────────────────────────────┐
                    │        PROCESS 3 DECISION GATE         │
                    │   (Sponsoring Group & Board Review)    │
                    └───────────────────┬────────────────────┘
                                        │
         ┌──────────────────────────────┼──────────────────────────────┐
         ▼                              ▼                              ▼
[ AUTHORIZE TRANCHE 1 ]        [ REQUIRE PLAN REVISION ]     [ TERMINATE PROGRAMME ]
- Baselined Delivery Plan     - Re-sequence critical path   - Strategic alignment lost
- Baselined Business Case      - Resolve resource contention - Business case collapsed
- Releases Tranche 1 Budget    - Adjust tranche scope        - Capital preserved
- Initiates Process 4          - Re-submit to gate             before delivery loss

Evaluation Criteria at the Gate

1. Robustness of the Delivery Plan: Does the plan feature realistic activity durations, manageable operational transition windows, and a fully analyzed cross-project critical path?
2. Viability of the Baselined Programme Business Case: Does the updated financial model demonstrate robust ROI and affordable capital drawdowns in light of detailed Tranche 1 supplier quotes?
3. Operational Change Capacity: Have the Business Change Managers confirmed that operational business units can absorb Tranche 1 changes without unacceptable performance drops?
4. Governance Readiness: Are the seven approaches of the Programme Strategy fully defined, approved, and staffed?

The Gate Decision

Upon successful review, the Sponsoring Group and Programme Board formally:

• Approve the Programme Strategy, Delivery Plan, and baselined Business Case.
• Authorize the release of funding and resources for Tranche 1.
• Formally trigger the transition into Process 4: Deliver the Capabilities.

---

Real-World Organizational Transformation Scenario

Aethelgard Telecom Metropolitan Smart Grid & Fiber Modernization

Context: Aethelgard Telecom, a major telecommunications provider, embarked on a $350M transformation to deploy next-generation 5G small-cell networks, high-density fiber, and smart IoT grid management across three metropolitan regions.

Executing Process 3 (Plan Progressive Delivery):

• Formulating the Programme Strategy: The Programme Manager established a hybrid Delivery Approach: civil fiber excavations followed predictive linear engineering, while IoT telemetry platforms utilized agile Scrum sprints. The Resourcing Approach mandated that specialized fiber-splicing contractors embed internal technicians in 1-to-1 pairings to ensure permanent knowledge transfer.
• Tranche Structuring & Blackouts: The three-year initiative was structured into three tranches:
  • Tranche 1: Core data centers and downtown high-density pilot.
  • Tranche 2: Northern municipal expansion and public utility IoT integration.
  • Tranche 3: Full metropolitan cutover and legacy copper decommissioning.
  • Crucially, the Delivery Plan scheduled an operational blackout window from November 1 to January 15 across all three years, prohibiting road excavations and core network maintenance during peak municipal winter weather and holiday trading.
• The Decision Gate: At the Process 3 gate review, the SRO presented the baselined Delivery Plan (sequencing 14 constituent projects into tranches), and the updated Business Case. The Sponsoring Group approved $85M in capital for Tranche 1, formally authorizing the initiation of Process 4.

---

Exam Tips & Common Traps

• Exam Tip (The 7 Governance Approaches): Be prepared to identify the seven approaches that comprise the Programme Strategy: Delivery, Resourcing, Stakeholder Engagement, Benefits Realization, Knowledge & Information, Assurance, and Decisions.
• Exam Tip (Rolling-Wave Horizon): On the exam, remember that rolling-wave planning requires high detail and baselined commitments for the immediate tranche only (Tranche 1), while keeping distant tranches directional.
• Common Trap (Process 3 vs. Process 4): Do not assume that projects begin construction or software coding during Process 3. Process 3 is strictly a planning and governance authorization process. Physical delivery of capabilities begins in Process 4 (Deliver the Capabilities).
• Common Trap (Scope of the Delivery Plan): A frequent exam trap suggests that the Delivery Plan only contains software development and engineering schedules. In MSP, the Delivery Plan must integrate business change activities, operational transition windows, blackout periods, and benefits realization milestones alongside project timelines.