Chapter overview
Comprehensive undergraduate Project Management chapter on programme, portfolio and benefits management, with detailed explanations, applied frameworks, case study, revision questions and print-ready notes. The chapter develops conceptual understanding, applied analytical skill and professional judgement. Students should connect the methods to project context, organisational strategy, stakeholder needs and sustainable outcomes rather than treating techniques as isolated procedures.
Learning outcomes: explain the major concepts; interpret frameworks and evidence; apply methods to realistic projects; evaluate assumptions and limitations; consider ethical and legal responsibilities; and communicate justified recommendations.
Study approach: read the sections, create a glossary, reproduce the diagram, work through the integrated application, attempt the case study and answer the assessment questions independently before reviewing the model guidance.
Chapter learning model
This learning model links specialist techniques to a continuous cycle of accountable project decisions. Adapt the steps to the chapter's subject and the project's governance requirements.
Chapter contents
1. Projects, programmes and portfolios distinguished2. Strategic alignment and investment selection3. Programme vision and blueprint4. Programme governance and leadership5. Programme architecture and component projects6. Dependency and interface management7. Benefits identification and mapping8. Benefits profiles and ownership9. Benefits realisation planning10. Financial and non-financial benefits appraisal11. Portfolio prioritisation and balancing12. Portfolio capacity and resource management13. Portfolio risk and interdependency14. Investment appraisal and economic evaluation15. Programme planning and transition waves16. Organisational change and adoption17. Programme assurance and strategic review18. Disinvestment and portfolio termination19. Case study: national digital education programme20. Programme closure and sustained benefitsIntegrated applicationExtended case studyAssessment questions1. Projects, programmes and portfolios distinguished
A project is a temporary endeavour delivering defined outputs or outcomes. A programme coordinates related projects and activities to achieve benefits that would be difficult to realise through separate management. A portfolio is a collection of projects, programmes and other work managed to achieve strategic objectives and optimise investment. These structures operate at different levels. A project manager focuses on delivery; a programme manager coordinates dependencies and benefits; portfolio leaders balance strategic value, capacity, risk and investment across the organisation.
Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.
Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.
Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.
2. Strategic alignment and investment selection
Portfolio management begins by translating strategy into investment criteria. Proposed initiatives may be assessed for strategic contribution, expected benefits, cost, risk, urgency, legal obligations, resource demand and organisational readiness. A scoring model can make assumptions visible, but should not replace governance judgement. Mandatory compliance work may need to proceed even when its financial return is limited. Strategic alignment should be revisited when external conditions change. A portfolio that contains many individually attractive projects can still be unaffordable or collectively inconsistent.
Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.
Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.
Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.
3. Programme vision and blueprint
A programme vision describes the future state the organisation intends to achieve. A blueprint translates that vision into capabilities, operating models, processes, technology, people and organisational changes required. The blueprint is not merely a technical architecture; it explains how the organisation will work differently and how benefits will arise. Validate it with operational leaders and users. Identify the gap between current and target states, sequencing constraints and assumptions. Update the blueprint as evidence emerges, while controlling changes to the intended outcomes.
Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.
Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.
Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.
4. Programme governance and leadership
Programme governance establishes decision rights, sponsorship, assurance, escalation, resource allocation and accountability for benefits. A programme board may include the sponsor, senior users, delivery leads and other authorised stakeholders. Governance should make timely decisions and resolve cross-project conflicts. Programme leadership maintains the overall vision while allowing component projects to manage their own delivery. Roles must be clear where project and operational authority overlap. Governance that only receives status reports but cannot make decisions adds overhead without improving control.
Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.
Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.
Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.
5. Programme architecture and component projects
A programme is decomposed into projects, workstreams and business change activities that collectively create capabilities. The architecture identifies outputs, interfaces, dependencies and sequencing. Component projects should have clear boundaries and acceptance conditions, but programme outcomes depend on integration across them. A technology platform may be delivered before staff training or process redesign, yet benefits may not occur until all are ready. Maintain an integrated roadmap and identify critical dependencies. Avoid optimising individual project schedules at the expense of programme-level outcomes.
Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.
Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.
Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.
6. Dependency and interface management
Dependencies may be technical, resource-based, contractual, regulatory, organisational or temporal. Map predecessor and successor relationships and identify the owner of each interface. A dependency register should state what is needed, by when, from whom and what happens if it is late. Cross-project planning meetings should focus on decisions and constraints rather than duplicating every project meeting. Escalate conflicts over shared specialists or environments to the level with authority to prioritise. Reassess dependencies when scope or delivery sequence changes.
Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.
Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.
Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.
7. Benefits identification and mapping
A benefit is a measurable improvement resulting from an outcome that stakeholders value. Benefits may be financial, service-related, social, environmental, capability-based or risk-reducing. A benefits map connects strategic objectives to changes in behaviour or capability, outputs and enabling activities. It makes assumptions visible and helps identify whether a project output plausibly leads to the intended result. Distinguish benefits from deliverables and activities. Identify disbenefits as well, such as transition disruption, increased workload or unequal access.
Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.
Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.
Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.
8. Benefits profiles and ownership
A benefits profile describes the benefit, strategic link, baseline, target, measurement method, expected timing, dependencies, risks and accountable owner. The owner should have authority to influence the operational changes required. Project managers may deliver outputs, but operational leaders often own benefit realisation after transition. Assigning benefits to a project team that dissolves at closure creates an accountability gap. Review profiles regularly and update forecasts transparently when assumptions or context change.
Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.
Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.
Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.
9. Benefits realisation planning
A benefits realisation plan specifies when and how outputs will be adopted, who will change behaviour, what support is needed and how outcomes will be measured. It should include baselines, targets, data collection, review dates and governance. Benefits may require process redesign, training, communications, new policies or changes to incentives. Plan these activities as part of the programme rather than treating them as optional tasks after technical delivery. Ensure operational teams have capacity and funding to sustain the new arrangements.
Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.
Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.
Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.
10. Financial and non-financial benefits appraisal
Financial benefits may include revenue, cost avoidance, productivity gains and reduced losses. Non-financial benefits may include service access, safety, equity, satisfaction, resilience and environmental improvement. Convert outcomes to monetary values only where assumptions are defensible and useful. Avoid double counting and distinguish cash-releasing savings from capacity released but not removed from budgets. Use a balanced appraisal that recognises public value and distributional effects. Document valuation methods and uncertainty so decision-makers understand what is measurable and what remains qualitative.
Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.
Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.
Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.
11. Portfolio prioritisation and balancing
Portfolio balancing considers strategic contribution, risk exposure, time horizon, sector, geography, resource demand and interdependencies. A portfolio may need a mix of innovation and essential renewal, short-term and long-term work, high-risk and lower-risk initiatives. Prioritisation is dynamic: a project may be paused when funding falls or strategy changes. Use transparent criteria and record why decisions are made. Avoid allowing sunk costs to justify continued investment when future benefits no longer outweigh remaining costs and risks.
Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.
Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.
Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.
12. Portfolio capacity and resource management
Portfolio capacity management compares demand for skills, funding, equipment and organisational attention with available supply. Resource conflicts can delay several projects simultaneously. Map scarce skills, critical roles and operational constraints. Consider sequencing, recruitment, outsourcing, training or reducing work in progress. Do not assume that all resources can be shared without productivity loss. Include the capacity of business units to absorb change; too many simultaneous transformations can overwhelm users and reduce benefit realisation.
Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.
Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.
Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.
13. Portfolio risk and interdependency
Portfolio risks include concentration in a supplier or technology, correlated market exposure, strategic misalignment, shared resource shortages and cumulative change fatigue. A risk that appears small within one project may be material across the portfolio. Aggregate exposure carefully and avoid double-counting the same event. Scenario planning can test the effects of funding cuts, regulatory change or a major supplier failure. Portfolio leaders should understand both individual project risk and systemic exposure created by dependencies.
Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.
Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.
Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.
14. Investment appraisal and economic evaluation
Investment appraisal compares expected costs and benefits over time. Techniques may include payback period, net present value, internal rate of return, cost-benefit analysis and cost-effectiveness analysis. Net present value discounts future net cash flows using an appropriate rate. Public and social projects may require economic appraisal that includes externalities and distributional effects. Results depend on assumptions about demand, inflation, discount rates, asset life and residual value. Sensitivity analysis should show how conclusions change when key assumptions vary.
Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.
Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.
Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.
15. Programme planning and transition waves
Programme plans coordinate component projects and business change across stages or waves. A transition wave may move a defined group of users, sites or services to the new operating model. Sequencing should consider readiness, dependencies, capacity, geographic context and risk. Pilots can reveal issues before wider rollout, but pilot conditions may not represent all users. Define entry and exit criteria for each wave, including training, data, support, security and operational readiness. Keep rollback or contingency options available where consequences justify them.
Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.
Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.
Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.
16. Organisational change and adoption
Programme outcomes often require changes to roles, processes, systems, culture and behaviour. Assess impacts by stakeholder group and location. Engage users early, explain the case for change, provide training and support, and measure adoption. Resistance may signal genuine problems such as inaccessible systems, workload increases or loss of trust. Do not label all criticism as resistance. Change activities need owners, budget and schedule integration. Adoption indicators should examine whether new practices are used effectively and produce the intended outcome.
Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.
Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.
Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.
17. Programme assurance and strategic review
Programme assurance examines whether the programme remains viable, coherent and likely to deliver benefits. Reviews should test the business case, blueprint, governance, dependencies, risk, capacity, change readiness and benefit forecasts. Independent challenge can identify optimism bias and weak assumptions. Strategic reviews should consider whether the programme remains aligned with organisational priorities. Decisions may include continuing, redirecting, pausing or closing components. Assurance findings need accountable actions and follow-up, not merely a report stored in a repository.
Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.
Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.
Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.
18. Disinvestment and portfolio termination
Disinvestment is the deliberate decision to stop or reduce investment when strategic fit, feasibility or expected value has changed. Sunk costs are not a reason to continue spending. Assess termination costs, contractual obligations, staff impacts, asset reuse, data retention and stakeholder commitments. Communicate decisions respectfully and preserve useful learning. Some work may be redirected to a different initiative. A transparent termination decision can protect resources for higher-value priorities and strengthen portfolio discipline.
Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.
Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.
Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.
19. Case study: national digital education programme
A ministry plans a multi-year programme covering school connectivity, digital content, teacher development, learner devices and data systems. Projects have separate budgets but depend on shared infrastructure and adoption by schools. Students should build a programme blueprint, map dependencies, identify benefits and owners, propose rollout waves and define portfolio selection criteria. Include rural access, accessibility, teacher workload, cybersecurity, procurement integrity and long-term operating costs. Explain how leaders should respond if connectivity improves but learner outcomes do not change as expected.
Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.
Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.
Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.
20. Programme closure and sustained benefits
Programme closure occurs when the intended capabilities are delivered, remaining work is transferred and governance confirms that programme-level objectives have been addressed or formally revised. Some benefits continue long after closure, so owners and measurement arrangements must remain in the operating organisation. Confirm residual risks, contracts, assets, knowledge transfer and funding for ongoing support. Evaluate actual benefits against profiles and explain gaps. Capture lessons about strategic alignment, dependencies, change adoption and investment decisions for future portfolios.
Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.
Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.
Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.
Integrated worked application
Consider a regional organisation implementing a service improvement across several sites. The sponsor has approved a strategic outcome, but the delivery team must translate it into an achievable plan. Begin with the intended user and organisational outcomes, then define the scope, constraints, assumptions and acceptance evidence. Map the stakeholders and identify who can approve decisions. Break the work into manageable packages, estimate the resources and sequence dependencies. Establish a baseline and a proportionate set of indicators. During implementation, compare actual evidence with the plan, investigate material differences and decide whether corrective action or formal change approval is required.
Suppose a new requirement emerges after a pilot reveals that a group of users cannot access the service through the intended channel. Do not treat this only as a technical defect. Analyse the requirement, accessibility implications, affected users, cost and schedule consequences, data and security considerations, operational support and expected benefits. Develop options such as adapting the interface, adding assisted access or revising rollout sequence. Evaluate each option against user outcomes, compliance, affordability and delivery risk. Present a recommendation with assumptions and an explicit decision request.
After approval, update the relevant plans and communicate the change to delivery and operational teams. Test the revised solution with representative users and collect evidence against acceptance criteria. At transition, confirm training, support, ownership, documentation and unresolved issues. Later, evaluate whether the service is used and whether the intended outcome has improved. This sequence demonstrates integration: project success is not a collection of separate documents but a coherent chain from need to sustainable benefit.
Extended case study: multi-site public service transformation
A public organisation intends to modernise a service delivered through twelve regional offices. The current process relies on paper records, repeated data entry and manual approvals. Users report long waiting times and inconsistent decisions. The proposed project introduces a shared digital platform, revised operating procedures and staff development. The organisation has a fixed funding envelope, varied internet connectivity, limited internal technical capacity and a target launch period. Some stakeholders support rapid implementation; others are concerned about privacy, job changes, accessibility and disruption.
Prepare a structured project response. Define the intended outcomes and measurable indicators. Identify stakeholders, their interests and engagement needs. Set out scope, exclusions, assumptions and constraints. Propose a delivery approach that allows learning while maintaining necessary governance. Develop a high-level schedule, budget logic, risk responses and quality criteria. Explain procurement and supplier oversight where external services are required. Plan training, data migration, operational readiness and post-launch support. Include an evaluation design that can distinguish outputs from outcomes and consider whether observed changes are plausibly connected to the intervention.
During implementation, the pilot identifies data inconsistencies and a connectivity gap in three offices. The supplier requests a variation and the sponsor asks whether the launch date can be retained. Analyse the decision using evidence rather than preference. Consider a phased release, additional validation, offline capability, targeted support or a revised timetable. Identify approval authority, impact on cost and benefits, and how users will be informed. State what evidence would justify proceeding, pausing or changing the plan. Your response should demonstrate professional judgement, ethical awareness and a clear audit trail.
University assessment questions and model answer guidance
1. Explain the principal concepts and purpose addressed in this chapter.
Model answer guide: Define the key terms accurately, explain their relationship to project objectives and distinguish them from related concepts. Use a relevant example and show why the concepts matter to project decisions.
2. Compare two approaches or frameworks relevant to the chapter.
Model answer guide: Identify the purpose and assumptions of each approach, compare their strengths and limitations, and explain which project conditions would make each more suitable. Avoid claiming that one method is universally superior.
3. Apply the chapter's methods to a project experiencing a major challenge.
Model answer guide: Define the problem, establish the evidence, identify affected stakeholders, develop feasible options, assess impacts on scope, time, cost, quality, risk and benefits, recommend an action and specify how it will be monitored.
4. Evaluate the ethical, legal and sustainability implications of a project decision.
Model answer guide: Identify relevant duties and affected groups, assess possible harm and distribution of benefits, explain applicable controls and show how transparency, participation and monitoring can improve the decision.
5. Discuss how performance should be measured and reported.
Model answer guide: Select indicators aligned to outcomes, define sources and frequency, explain thresholds and limitations, and distinguish activity, output, outcome and impact measures. Recommend a reporting format suited to decision-makers.
6. Explain how lessons learned should influence future projects.
Model answer guide: Use evidence to identify causes and context, distinguish effective practice from isolated success, formulate actionable recommendations and assign responsibility for embedding improvements.
7. Prepare a concise recommendation for a project sponsor.
Model answer guide: State the decision required, preferred option, evidence, assumptions, costs, benefits, main risks, alternatives, approvals, implementation responsibilities and review triggers.
8. Essay: project success requires integration of technical delivery and organisational change. Discuss.
Model answer guide: Explain the role of outputs and technical controls, then analyse user adoption, governance, operational readiness, benefits, ethics and sustainability. Support the argument with examples and a balanced conclusion.
Revision checklist and independent study
- Define the chapter's key concepts and explain how they connect.
- Draw and interpret the relevant framework or process diagram.
- Apply the methods to a project context different from the case study.
- Identify assumptions, limitations, risks and ethical considerations.
- Support recommendations with evidence and state how success will be measured.
- Explain how the work connects to the wider project life cycle and sustainable benefits.
For deeper study, consult current academic texts, peer-reviewed research, recognised professional standards, institutional library resources and applicable national laws or sector guidance. Confirm the edition and jurisdiction relevant to your course. Professional standards and legislation can change, and students should not treat these study notes as a substitute for official institutional or regulatory requirements.
Official Education References
Use these official organisations for curriculum guidance, examinations and further learning information.