CMI Unit 706 Assignment Help — Programme and Project Leadership

CMI Unit 706, Programme and Project Leadership, is the Level 7 unit that examines how senior leaders govern complex change at programme scale, beyond individual project management. Written as a strategic paper at Critically Analyse depth, this unit requires you to engage with the academic debate between benefits-realisation frameworks (OGC’s Managing Successful Programmes) and the empirical evidence on why large programmes systematically fail to deliver (Flyvbjerg’s megaproject research). Directors and senior leaders with responsibility for transformation portfolios find this unit particularly demanding because it challenges the planning optimism that underpins most programme business cases. If you need expert support with Unit 706, message us on WhatsApp.

What CMI Unit 706 Covers

Unit 706 addresses programme leadership as distinct from project management. The learning outcomes require understanding the theoretical basis for programme management, the relationship between programmes and strategic change, approaches to benefits realisation, and how strategic leaders govern complex, multi-project change initiatives. At Level 7, this means critically analysing MSP alongside Flyvbjerg’s empirical evidence, and producing an original synthesis on the conditions under which programme management frameworks can realistically deliver strategic benefits.

OGC (2011) — Managing Successful Programmes

The Office of Government Commerce’s Managing Successful Programmes (4th edn, The Stationery Office, 2011) is the reference framework for programme management in UK public sector and NHS contexts. MSP distinguishes programmes from projects by purpose: projects deliver outputs (a new building, a new IT system); programmes deliver outcomes and benefits (improved patient flow, reduced waiting times, integrated care pathways). The programme management role is to ensure that the sum of project outputs is configured to realise the intended organisational benefits, a fundamentally different leadership challenge from project delivery.

MSP’s architecture rests on three core principles: remaining aligned with corporate strategy, delivering a coherent capability, and realising measurable benefits. The five themes, Benefits Realisation Management, Blueprint Design and Delivery, Stakeholder Engagement, Governance, and Risk Management, form an integrated governance framework. The Benefits Realisation Management theme is the most theoretically significant: MSP argues that benefits do not realise themselves, they must be actively managed through benefit owners, realisation plans, and measurement frameworks that track benefit delivery, not just project completion.

At Level 7 critical analysis depth, the key move is recognising that MSP’s benefits-realisation emphasis represents a theoretical shift from project completion as the measure of success (the construction industry model: on time, on budget, to specification) to value creation as the measure of success (did the organisation change in the ways the programme intended?). For NHS programmes, EPR implementations, ICS integration, workforce transformation, the distinction is analytically critical: a programme can complete every project on time and on budget while failing to realise the intended benefits if the change management, training, and adoption activities that produce benefit realisation are not treated as programme deliverables.

Pellegrinelli (1997) — Programme as Strategic Change Vehicle

Sergio Pellegrinelli’s 1997 article in the International Journal of Project Management (15(3), pp. 141–149), ‘Programme Management: Organising Project-Based Change’, provides the theoretical foundation for understanding programmes as vehicles for strategic change rather than bundles of projects.

Pellegrinelli argues that the defining characteristic of a programme is not its size or complexity but its role in delivering strategic intent. Projects deliver defined outputs; programmes create the conditions for strategic transformation. The programme manager’s role is fundamentally a leadership role, managing the political, cultural, and organisational dynamics that determine whether project outputs translate into strategic outcomes.

The analytically significant contribution: Pellegrinelli distinguishes between portfolio programmes (a collection of projects managed together for efficiency), dossier programmes (projects with a common theme but independent benefits), and strategic programmes (projects that collectively deliver a strategic transformation). Most NHS programmes that are called “strategic” are in practice dossier programmes, they have a common theme (workforce development, digital transformation) but each project realises its benefits independently. Genuine strategic programmes require integration of project outputs into a new organisational capability.

Edkins, Geraldi, Morris and Smith (2013) — Front-End Loading

Edkins et al.’s (2013) research on front-end loading in major programmes establishes that the decisions made during the conceptualisation and definition phases of a programme have a disproportionate impact on ultimate success. Front-end loading is the investment of analytical, design, and planning effort before programme execution begins, establishing clear strategic rationale, realistic scope, genuine stakeholder alignment, and achievable benefits projections.

The implications for Level 7 analysis: programmes that fail typically do so because of flawed front-end decisions, unclear strategic rationale, unrealistic benefits cases, scope that has not been rigorously tested against organisational capacity, and stakeholder commitment that is notional rather than contractual. Front-end loading research supports Flyvbjerg’s explanations for overrun and underperformance but locates the causal mechanism in the pre-execution phase rather than execution failure per se.

Flyvbjerg (2014) — Megaproject Overrun

Bent Flyvbjerg’s 2014 article in the Project Management Journal (45(2), pp. 6–19), ‘What You Should Know About Megaprojects and Why: An Overview’, presents empirical evidence from 2,000+ large-scale programmes across 20 nations that should fundamentally challenge the optimism of programme business cases. Flyvbjerg’s three findings are: cost overrun is the norm, not the exception (average 45% for IT projects); benefits are systematically overestimated (often by 50–200%); and programme completion time is regularly underestimated.

Flyvbjerg identifies two mechanisms for these systematic failures. Optimism bias (Kahneman’s cognitive psychology) is the tendency of decision-makers to underestimate costs, timescales, and risks and overestimate benefits, a cognitive error that affects even experienced programme leaders. Strategic misrepresentation is theoretically more troubling: it occurs when programme sponsors and promoters deliberately present misleading projections in order to secure programme approval, knowing that the business case does not accurately reflect the likely programme performance. In the NHS context, where programme business cases require Treasury Green Book approval and ICS board endorsement, strategic misrepresentation creates a governance failure at the system level.

The Central Academic Debate: Benefits Realisation vs Empirical Evidence of Systemic Overrun

The central academic debate in Unit 706 is whether programme management frameworks such as MSP provide the governance mechanisms needed to deliver strategic benefits, or whether Flyvbjerg’s empirical evidence reveals structural tendencies toward overrun and underperformance that frameworks cannot overcome.

MSP’s answer is process-based: rigorous benefits realisation management, blueprint design, and stakeholder engagement will deliver the programme’s strategic intent. Flyvbjerg’s answer is structural: optimism bias and strategic misrepresentation are not failures of process, they are predictable outcomes of the incentive structures and cognitive patterns that operate on all large programme decisions, including those governed by MSP-compliant frameworks.

The original synthesis position that earns distinction: MSP and Flyvbjerg are not mutually exclusive. MSP’s benefits realisation management provides the governance structure; Flyvbjerg’s research identifies the specific failure modes that governance must be designed to counteract. A programme governance framework that incorporates reference class forecasting (Flyvbjerg’s evidence-based approach to realistic projection), explicit bias challenge processes at business case approval, and independent benefits validation provides more reliable programme governance than either MSP compliance alone or Flyvbjerg-informed scepticism that produces decision paralysis.

Pass / Merit / Distinction

Pass: The student applies MSP’s principles and themes, introduces the benefits vs outputs distinction, and references Flyvbjerg’s evidence. Pellegrinelli’s programme types are applied. Sources are cited in Harvard format.

Merit: MSP’s benefits realisation theme is evaluated for its sufficiency in addressing the gap between project completion and benefit realisation. Flyvbjerg’s optimism bias and strategic misrepresentation are distinguished and evaluated separately. Pellegrinelli’s strategic programme type is applied to the specific organisational context. Front-end loading connected to business case quality.

Distinction, worked example: “OGC (2011) MSP’s benefits realisation management framework provides the governance architecture for translating project outputs into organisational outcomes, a theoretical advance over project management frameworks that measure success at project completion. However, Flyvbjerg (2014) presents empirical evidence that challenges the assumption that rigorous governance is sufficient: across 2,000+ major programmes, optimism bias and strategic misrepresentation produce systematic cost overrun and benefits shortfall that occur within, not despite, formal governance frameworks. The synthesis position is that MSP governance is necessary but not sufficient for programme success. The critical addition is Flyvbjerg’s reference class forecasting: programme business cases should be validated against the empirical track record of comparable programmes, not against the programme team’s internal projections. Edkins et al. (2013) add the front-end loading dimension: if the strategic rationale, scope, and benefits case are not rigorously stress-tested before execution, no amount of execution-phase governance will compensate. For NHS ICS integration programmes, this synthesis suggests that programme governance must be designed to challenge the business case itself, not merely to execute against it.”

Strategic Paper Format for Unit 706

Common Questions About CMI Unit 706

What is the difference between programme management and project management at Level 7? The Level 7 answer draws on Pellegrinelli (1997) and OGC (2011) MSP. A project delivers a defined output within a specified scope, time, and cost. A programme delivers outcomes and benefits through a coordinated set of projects, but the defining characteristic is strategic intent: a programme creates the conditions for organisational transformation, not just the delivery of a technical output. At Level 7, the critical analysis adds a further distinction: the governance challenge for programmes is managing the relationship between project delivery and benefit realisation, which requires leadership of organisational change, not just project oversight. A Trust building a new EPR system is managing a project if success is measured by system go-live; it is managing a programme if success is measured by clinical workflow transformation, staff adoption, and measurable patient outcome improvement.

How should I use Flyvbjerg’s research in the Unit 706 paper without being entirely negative about programme management? The sophisticated answer is to use Flyvbjerg diagnostically, not as a reason to abandon programme management. Flyvbjerg’s (2014) evidence establishes that optimism bias and strategic misrepresentation are predictable failure modes, the Level 7 analytical contribution is to identify which programme governance mechanisms directly address these failure modes. Reference class forecasting addresses optimism bias in business case projections. Independent programme assurance (the OGC Gateway Review process) addresses the incentive structures that enable strategic misrepresentation. The synthesis argument is that Flyvbjerg’s research is not an argument against programme management; it is an evidence base for what strong programme governance must do differently from what conventional MSP compliance alone achieves.

Do I need to use MSP as a framework even if my organisation uses PRINCE2 or Agile methods? At Level 7, you should engage with MSP as the theoretical reference for programme-level governance regardless of the operational methods your organisation uses. PRINCE2 is a project management method; MSP is a programme management framework, they operate at different levels. Agile delivery methods can be incorporated within a programme governance structure without replacing the programme-level governance framework. The critical analysis opportunity is to assess whether the organisation’s operational delivery methods (PRINCE2 or Agile at project level) are appropriately integrated within programme-level governance, or whether the absence of programme-level oversight means the organisation is running a collection of projects rather than a genuine programme.

What is reference class forecasting and why does it matter for Unit 706? Flyvbjerg (2014) argues that programme cost and benefit projections based on the specific programme’s internal analysis are systematically biased because of optimism bias and strategic misrepresentation. Reference class forecasting is an evidence-based alternative: before producing internal projections, business case developers gather empirical data on the actual outcomes of comparable programmes (the reference class) and use that data to calibrate projections. For NHS digital transformation programmes, the reference class would include EPR implementations across comparable NHS Trusts, if the empirical distribution shows that 80% of comparable implementations exceed budget by 30–50%, an internal projection of on-budget delivery requires explicit justification. At Level 7, citing reference class forecasting demonstrates engagement with Flyvbjerg’s practical implications, not just his critique.

How does Unit 706 connect to Unit 703 Strategy and Unit 709 Change Leadership? Unit 706 operates at the intersection of strategy (703) and change leadership (709). Strategy defines the transformation agenda that programmes are designed to deliver. Change leadership determines whether the human and cultural dimensions of transformation are managed effectively enough that project outputs translate into the intended strategic outcomes. Programme leadership (706) is the governance layer that connects strategic intent (703) to change realisation (709). At Level 7, demonstrating awareness of this cross-unit theoretical architecture, and the risk that programmes which are strong on project governance but weak on change leadership will deliver outputs without realising benefits, is an indicator of strategic thinking that markers look for.

The Financial Reporting Council publishes corporate governance and financial reporting standards that provide the regulatory framework for the strategic finance content assessed at Critically Analyse depth in this CMI Level 7 unit.

Related CMI Assignment Help

• CMI 703 Assignment Help, Developing and Implementing Strategy: Mintzberg deliberate vs emergent strategy, Barney RBV, Teece dynamic capabilities
• CMI 709 Assignment Help, Leading Strategic Change: Beer & Nohria Theory E vs Theory O, Weick sensemaking
• CMI 714 Assignment Help, Digital Transformation and Technology Leadership: Westerman digital maturity, Christensen disruption
• CMI 708 Assignment Help, Strategic Relationships and Collaboration