4.1 Business Case Practice

4.1 Business Case Practice

In PRINCE2 7, project management is rooted in continuous business justification. A project is not merely an exercise in creating technical deliverables or completing activities within budget; it is an investment undertaken to achieve tangible business improvements and organizational strategic objectives. The Business Case Practice provides the structured mechanisms required to establish, monitor, and re-verify that a project remains desirable, viable, and achievable throughout its entire lifecycle.

---

Purpose of the Business Case Practice

PRINCE2 7 Definition: The purpose of the Business Case practice is to establish mechanisms to judge whether the project is (and remains) desirable, viable, and achievable as a means to support decision-making in its investment.

The Business Case practice answers the fundamental question: Is the project investment justified, and should it continue? If at any point during project execution the business justification ceases to exist—because costs have escalated, market conditions have changed, or expected benefits can no longer be realized—the project should be stopped or redirected.

The Three Dimensions of Justification

PRINCE2 evaluates project justification across three core dimensions:

1. Desirable: The balance of costs, benefits, and risks is acceptable to the organization and aligns with corporate or programme strategies.
2. Viable: The project can deliver the required outputs within financial, technical, and operational constraints such that the benefits exceed costs.
3. Achievable: The organization possesses or can acquire the capabilities, resources, and technical means to successfully deliver the products and embed the required operational change.

---

Key Concepts: Outputs, Outcomes, Benefits, and Dis-benefits

A critical requirement for the PRINCE2 7 Foundation exam is distinguishing between the four core elements of value creation: Outputs, Outcomes, Benefits, and Dis-benefits.

[ Specialist Project Work ] 
        │
        ▼
   ┌─────────┐
   │ Output  │  (System, Product, or Asset delivered by project)
   └────┬────┘
        │
        ▼
   ┌─────────┐
   │ Outcome │  (Operational change resulting from using the Output)
   └────┬────┘
        │
        ├──────────────────────────┐
        ▼                          ▼
   ┌─────────┐               ┌──────────────┐
   │ Benefit │               │ Dis-benefit  │
   └─────────┘               └──────────────┘
(Measurable Positive)      (Expected Negative Side-Effect)

Definitions and Characteristics

• Output (Deliverable): A specialist product that is created and handed over by the project. Examples include a new e-commerce web platform, a physical warehouse building, or a newly designed employee training curriculum.
• Outcome: The change in operational capability or behavior resulting from the use of the project's outputs. Examples include sales staff utilizing the new e-commerce platform to process orders online, or logistics staff operating inside the new warehouse.
• Benefit: The measurable improvement resulting from an outcome that is perceived as an advantage by one or more stakeholders and supports organizational objectives. Examples include a 25% increase in annual online retail revenue, or a 15% reduction in warehouse order fulfillment costs.
• Dis-benefit: An outcome perceived as negative by one or more stakeholders. Dis-benefits are expected downsides of the project investment that will occur as a result of achieving the outcomes. Examples include a temporary drop in call center productivity during software migration, or increased monthly cloud hosting fees.

Exam Tip: Do not confuse Dis-benefits with Risks! A dis-benefit is a certain or expected negative consequence of the project outcome. A risk is an uncertain event that may or may not occur. Both must be factored into the Business Case, but dis-benefits are included in financial payback calculations from the outset.

---

Business Case Management Products

The Business Case practice relies on three primary management products created and maintained during the project lifecycle:

1. Outline Business Case

Drafted during the Starting up a project (SU) process by the Executive (with assistance from the Project Manager). It provides initial high-level justification to enable the Project Board to decide whether to authorize the initiation stage.

2. Business Case

Developed during the Initiating a project (IP) process by refining the Outline Business Case. It incorporates detailed cost estimates, financial calculations (e.g., ROI, Net Present Value, Payback Period), risk assessments, and major milestone dates. Once approved by the Project Board as part of the Project Initiation Documentation (PID), it becomes the baseline for monitoring business justification throughout the project.

3. Benefits Management Approach

Created during Initiating a project (IP) by the Project Manager alongside the Business Case. It defines:

• What benefits will be measured.
• How and when benefit measurements will take place (including post-project tracking).
• Who is accountable for measuring each benefit (typically the Senior User).
• What resources are required for benefit realization reviews.

---

Business Case Lifecycle & Continual Verification

The Business Case is not a static document created once and filed away; it is a dynamic management tool actively reviewed at key decision points:

1. Starting up a project (SU): Outline Business Case created to justify spending resources on detailed project initiation planning.
2. Initiating a project (IP): Detailed Business Case and Benefits Management Approach baseline created and approved by Project Board.
3. Managing a Stage Boundary (SB): Updated at the end of every management stage to reflect actual costs/time spent, revised forecasts, and current risk landscape. The Project Board re-verifies justification before authorizing the next stage.
4. Controlling a Stage (CS): Continually referenced when assessing issues, changes, or risk escalations. If an exception occurs, the Project Manager evaluates its impact on the Business Case.
5. Closing a project (CP): Finalized to summarize actual costs vs. budget, actual delivery timelines, and expected schedule for post-project benefit realization reviews.

---

Roles & Responsibilities in the Business Case Practice

• Corporate, Programme Management, or Customer: Provides organizational strategy and strategic targets with which the Business Case must align.
• Executive: Holds ultimate accountability for the Business Case and project success. Ensures the project delivers value for money.
• Senior User: Responsible for specifying, quantifying, and committing to the expected benefits. Owns the realization of benefits post-project.
• Senior Supplier: Confirms that products can be delivered within estimated costs and technical parameters, ensuring the Business Case is viable.
• Project Manager: Responsible for drafting and updating the Business Case and Benefits Management Approach on behalf of the Executive.
• Project Assurance (Business): Independently monitors the Business Case for continued viability against corporate standards.