Developing and Maintaining the Business Case is a core activity within the Justification theme of MSP (Managing Successful Programmes) 5th edition. The Business Case is the central document that justifies the programme, capturing the balance of costs, benefits, risks, and timescales to demonstrate …Developing and Maintaining the Business Case is a core activity within the Justification theme of MSP (Managing Successful Programmes) 5th edition. The Business Case is the central document that justifies the programme, capturing the balance of costs, benefits, risks, and timescales to demonstrate that the investment remains worthwhile and desirable throughout its lifecycle. Developing the Business Case begins during programme identification and definition, drawing on the target operating model, the benefits map, and the delivery plan. It aggregates individual project business cases and includes programme-level costs such as change management and business-as-usual impacts. The Business Case is not a one-off document; it must be maintained and regularly reviewed as the programme progresses, particularly at the boundaries between tranches, when circumstances change, or when new information emerges. This ongoing validation ensures the programme continues to align with organisational strategy and delivers value for money. Links to the Structure theme are significant: the Sponsoring Group and Senior Responsible Owner (SRO) own the Business Case and are accountable for its ongoing viability. The Programme Board supports the SRO, while the Business Change Manager provides input on benefits realisation and the impact on business operations. Governance structures ensure the Business Case is scrutinised and challenged appropriately. Links to the Knowledge theme are also important: maintaining the Business Case relies on accurate information management, knowledge capture, and lessons learned. Reliable data on costs, benefits, and risks supports informed decision-making. Knowledge gained from earlier tranches and other programmes helps refine estimates and assumptions, improving the accuracy of the Business Case over time. Ultimately, the Business Case underpins the decision to continue, adjust, or stop the programme. By developing and maintaining it rigorously, and integrating structural accountability and robust knowledge management, MSP ensures programmes remain justified, focused on outcomes, and capable of delivering strategic benefits to the organisation and its stakeholders.
Developing and Maintaining the Business Case
Introduction In MSP (Managing Successful Programmes), the Business Case is a central element of the Justification structure and one of the key knowledge themes. Developing and Maintaining the Business Case is a continuous activity that ensures a programme remains desirable, viable and achievable throughout its lifecycle. This guide explains why it matters, what it is, how it works, and how to answer exam questions on the topic.
Why It Is Important The Business Case is the justification for the programme. Programmes consume significant resources over long periods and operate in changing environments, so it is vital to continually check that the investment remains worthwhile.
Key reasons the Business Case matters: Justification: It confirms that the expected benefits outweigh the costs, risks and time involved. Decision-making: It provides the basis for go/no-go decisions at key review points. Alignment: It links the programme to organisational strategy and objectives. Accountability: It gives the Senior Responsible Owner (SRO) a clear reference for accountability. Control: It allows the programme to be stopped, adjusted or continued based on evidence rather than momentum.
What It Is The Business Case is an aggregation of specific information used to judge whether the programme is, and remains, desirable, viable and achievable. It brings together: • The costs of the programme (including transition and ongoing operational costs). • The expected benefits and their value. • The associated risks. • The timescales for delivery.
The three key tests of a sound Business Case are: Desirable: Do the benefits justify the costs and risks? (cost-benefit balance) Viable: Can the organisation deliver the capability and afford it? Achievable: Can the operations realise the benefits from the capabilities delivered?
The Business Case is developed from the vision, the blueprint, the benefits, and the programme plan, drawing on financial and risk information.
How It Works Developing and maintaining the Business Case is an ongoing, iterative process, not a one-off document created at the start.
Developing: An outline Business Case is created early (linked to the programme mandate and brief). It is refined during Identifying a Programme and completed during Defining a Programme, drawing on the blueprint, benefits profiles and programme plan.
Maintaining: Throughout Managing the Tranches and delivery, the Business Case is reviewed and updated. It is formally reviewed at the end of each tranche and at other key decision points to confirm ongoing justification. Changes in costs, benefits, risks, or the wider environment trigger updates.
Confirming: During Closing a Programme, the Business Case is assessed to confirm that expected benefits have been (or will be) realised and the programme has delivered value.
The SRO is ultimately accountable for the Business Case, ensuring it remains valid and that the programme continues to be a worthwhile investment.
Relationship to Other Themes The Business Case draws heavily on other MSP elements: • Benefits management supplies the value side of the equation. • Blueprint design and delivery defines the target capability and its costs. • Risk management feeds the risk assessment. • Planning and control provides costs and timescales.
How to Answer Exam Questions Exam questions may test your understanding of the purpose, contents, review timing, roles, and the three tests (desirable, viable, achievable). Foundation-level questions are typically factual recall; Practitioner-level questions apply concepts to a scenario.
Read questions carefully to identify whether they ask about developing (creating/refining) or maintaining (reviewing/updating) the Business Case. Watch for the roles involved, especially the SRO's accountability.
Exam Tips: Answering Questions on Developing and Maintaining the Business Case • Memorise the three tests: desirable, viable, achievable — and be able to define each. • Remember the Business Case is an aggregation of costs, benefits, risks and timescales, not a standalone document. • Know that it is reviewed at the end of each tranche and at key decision points. • Link the Business Case to the SRO as the accountable role. • Emphasise that it is iterative and continuously maintained, not fixed. • In scenario questions, look for triggers (cost overruns, changed benefits, new risks) that require a Business Case update. • Distinguish the Business Case from the Benefits Realisation Plan and the Blueprint — examiners often test these distinctions. • Use precise MSP terminology and avoid vague answers. • For 'why' questions, focus on justification and value-for-money over the programme lifecycle.
Summary Developing and Maintaining the Business Case ensures a programme stays justified from start to finish. By continually testing that it is desirable, viable and achievable, and by keeping the Business Case current, the organisation can make informed decisions to continue, adjust or stop the programme. Mastering the definitions, the three tests, the review timing and the SRO's role will help you answer exam questions confidently.
