## Purpose of the Business Case Theme

The Business Case Theme in PRINCE2 establishes mechanisms to judge whether the project is (and remains) desirable, viable, and achievable. Its primary goal is to support decision-making for the project's continued investment. This theme directly underpins the PRINCE2 principle of Continued Business Justification, ensuring that the project always has a valid reason to proceed and that its benefits outweigh its costs and risks.

## The Business Case Document

The Business Case is the key management product for this theme. It provides the justification for the project and is owned by the Executive. It evolves throughout the project lifecycle:

• An Outline Business Case is created in the Starting Up a Project process.
• A Detailed Business Case is developed in the Initiating a Project process.

Key components of the Business Case include:

• Executive Summary: A brief overview.
• Reasons: Why the project is needed.
• Business Options: Typically 'Do nothing', 'Do minimum', and 'Do something' (the recommended option).
• Expected Benefits: Measurable improvements resulting from the project's outcome.
• Expected Dis-benefits: Negative consequences of an outcome.
• Timescale: Project duration.
• Costs: Project expenditure.
• Investment Appraisal: Financial analysis (e.g., ROI, NPV).
• Major Risks: Key threats and opportunities.

## Benefits Management Approach (BMA)

The Benefits Management Approach is a plan that defines how and when the project’s benefits will be identified, measured, monitored, and reviewed. It also assigns responsibilities for benefit realization. This approach is created in the Initiating a Project process and refined as needed.

## Roles and Responsibilities

• Executive: Responsible for the Business Case and its continued validity.
• Senior User: Specifies the benefits and ensures their realization.
• Project Manager: Prepares and updates the Business Case (under Executive's direction) and the Benefits Management Approach.
• Project Board: Approves the Business Case and monitors its ongoing viability.

## Integration with Processes

• Starting Up a Project: Create Outline Business Case.
• Initiating a Project: Create Detailed Business Case and Benefits Management Approach.
• Managing a Stage Boundary: Review and update the Business Case and Benefits Management Approach.
• Closing a Project: Final update to the Business Case and confirmation of post-project benefits review arrangements.

## Organization Theme: Defining Roles and Responsibilities

The Organization theme establishes and defines the project's structure of accountability and responsibilities. It ensures that the project management team has a clear and effective structure, with defined roles and responsibilities, enabling effective decision-making and communication. This theme addresses the PRINCE2 principle of "Defined roles and responsibilities," ensuring everyone knows their role and what is expected of them.

## Project Management Team Structure

PRINCE2 defines a scalable project management team with four levels of management:

• Corporate/Programme Management: Provides the project mandate and appoints the Executive, setting the overall strategic context.
• Directing (Project Board): Accountable for the project's success or failure. It comprises three key roles:
• Executive: Accountable for the project, ensures value for money, chairs the Project Board, and represents business interests.
• Senior User: Represents the interests of those who will use the project's products and realize the benefits. Ensures products meet user needs and are fit for purpose.
• Senior Supplier: Represents the interests of those designing, developing, and implementing the products. Ensures technical quality and integrity.
• Managing (Project Manager): Responsible for the day-to-day management of the project on behalf of the Project Board.
• Delivering (Team Manager/Team Members): Responsible for creating the specialist products according to specifications and quality requirements.

## Key Roles and Responsibilities

Beyond the core Project Board and Project Manager, other crucial roles support the project:

• Project Assurance: An independent role monitoring the project's performance and products on behalf of the Project Board. It ensures the project remains viable and adheres to standards, and cannot be delegated to the Project Manager.
• Project Support: Provides administrative, guidance, and configuration management services to the Project Manager and Project Board. This can be an individual or a Project Support Office (PSO).
• Change Authority: A role appointed by the Project Board (or delegated to the Project Manager) to approve or reject change requests within defined tolerances.

## Tailoring the Organization Theme

PRINCE2 roles are descriptions of responsibilities, not job titles. They can be combined or split depending on the project's size, complexity, and context. For instance, in a small project, the Project Manager might also perform Project Support duties, or a single person might cover both Senior User and Senior Supplier roles if appropriate skills exist and no conflict of interest arises. The key is to ensure all responsibilities are clearly allocated and understood. The Communication Management Strategy is a key management product that defines how and when communication will occur between these roles and external stakeholders.

## Quality Theme in PRINCE2

The Quality theme addresses how the project will ensure that its products are fit for purpose. It focuses on defining and implementing the means by which the project will create products that meet the agreed requirements. The aim is to deliver products that meet both the customer's expectations and the specified quality criteria.

## Key Concepts

• Customer's Quality Expectations: These are the overall quality requirements for the project's products, expressed from the customer's perspective. They are captured during the Starting Up a Project process and refined into Acceptance Criteria. They address aspects like performance, reliability, usability, and maintainability.

• Acceptance Criteria: Specific, measurable, achievable, relevant, and time-bound (SMART) criteria that the project's final product (the project product) must meet to be acceptable to the customer and other key stakeholders. They are approved by the Project Board and documented in the Project Brief and Project Initiation Documentation (PID).

• Quality Management Strategy: This document defines the specific quality techniques and standards to be applied, and the responsibilities for achieving the required quality levels. It covers quality planning, quality control, and quality assurance activities. It is created during Initiating a Project.

• Product Description: For each major product to be created by the project, this document details its purpose, composition, derivation, format, and crucially, its Quality Criteria. These criteria define the specific quality characteristics the product must meet, along with the quality methods (e.g., review, test) and responsibilities for checking quality.

• Quality Register: A log used to record all planned and completed quality activities (e.g., reviews, tests, audits), their results, and any required follow-up actions. It provides a summary of the quality status of products and helps track quality progress.

• Quality Control: The operational techniques and activities used to fulfil requirements for quality. This involves performing the quality methods defined in the Product Descriptions (e.g., product reviews, testing, inspections) and updating the Quality Register.

• Quality Assurance: An independent check that the project is following corporate or programme quality standards and procedures. This is a corporate responsibility, not a PRINCE2 project management team responsibility, but the project must cooperate with it. It focuses on the quality of the management processes.

## Responsibilities

• The Project Board (specifically the Executive) is responsible for approving the Customer's Quality Expectations and Acceptance Criteria.
• The Project Manager is responsible for creating the Quality Management Strategy, establishing the Quality Register, and ensuring that quality activities are planned and executed correctly.
• Team Managers are responsible for ensuring that the products they develop meet their defined Quality Criteria.

By effectively applying the Quality theme, PRINCE2 ensures that the project delivers products that are fit for purpose, meeting both the customer's expectations and the specified quality criteria throughout the project lifecycle.

## The Plans Theme in PRINCE2

The Plans theme in PRINCE2 provides a framework for designing, developing, and maintaining plans. Its primary purpose is to facilitate communication and control by defining *how*, *when*, and *by whom* specific products are to be created. Plans are central to how the Project Board and Project Manager exercise control and measure progress, providing a baseline for monitoring.

Levels of Plans

PRINCE2 mandates a minimum of two levels of plans and introduces an optional third:

• Project Plan: Developed by the Project Manager during the Initiating a Project process. It provides a high-level overview for the entire project, showing major products, activities, timescales, and costs. It is approved by the Project Board.
• Stage Plan: Created by the Project Manager for each management stage during the Managing a Stage Boundary process. This is a more detailed plan outlining the products, activities, resources, and timescales for that specific stage. It is also approved by the Project Board.
• Team Plan: An optional, highly detailed plan created by a Team Manager during the Managing Product Delivery process. It details the execution of one or more Work Packages and is not formally approved by the Project Board, but derived from the Work Package.

Product-Based Planning

PRINCE2 emphasizes product-based planning, a technique that focuses on identifying and defining the products required *before* considering the activities needed to create them. The steps are:

1. Design the Plan: Define the planning approach.

2. Define and Analyze Products: This key step involves creating a Product Breakdown Structure (PBS), writing Product Descriptions (PDs) for each major product, and developing a Product Flow Diagram (PFD) to show dependencies.

3. Identify Activities and Dependencies: Determine the tasks required to produce each product and their sequence.

4. Prepare Estimates: Estimate effort, duration, and cost for activities.

5. Prepare the Schedule: Allocate resources and define timescales.

6. Analyze Risks: Identify and assess risks related to the plan.

7. Document the Plan: Compile the plan into a formal document.

Key Management Products

The Plans theme is closely associated with several key management products:

• Project Plan: The overall project blueprint.
• Stage Plan: Detailed plan for a single stage.
• Product Description (PD): Defines a product's purpose, composition, quality criteria, and development skills required.
• Product Breakdown Structure (PBS): A hierarchical breakdown of all products required.
• Product Flow Diagram (PFD): Illustrates the sequence and dependencies of product creation.
• Work Package: A set of information about products to be created by a team, forming the basis for a Team Plan.

Plans provide the baseline against which progress is monitored and controlled, ensuring the project remains viable and aligned with objectives.

## The Risk Theme: Managing Uncertainty

The Risk Theme in PRINCE2 provides a structured approach to identifying, assessing, and controlling uncertainty throughout the project lifecycle. Its purpose is to ensure that the project team and stakeholders understand the project's risks, and that appropriate actions are taken to manage them, thereby improving the chances of project success.

Key Definitions

A risk is an uncertain event or set of events that, should it occur, will have an effect on the achievement of objectives. Risks can be categorized as threats (negative impacts) or opportunities (positive impacts). Risk appetite defines the amount of risk an organization or project is willing to take, typically expressed as tolerance levels.

The Risk Management Procedure (IAPIC)

PRINCE2 outlines a five-step procedure for managing risks:

• Identify: Recognize potential risks, their causes, and effects. Techniques include brainstorming, checklists, and lessons learned.
• Assess: Evaluate the probability of the risk occurring and the impact it would have on project objectives. This helps prioritize risks.
• Plan: Develop appropriate risk responses for each identified risk. This includes defining specific actions and assigning a risk owner and actionee.
• Implement: Carry out the planned risk responses. This often involves monitoring trigger events and executing contingency plans.
• Communicate: Ensure information about risks and their management is shared effectively among stakeholders, including the Project Board and team members.

Key Documents and Outputs

• Risk Management Strategy: This document defines the project's specific approach to risk management, including procedures, roles, responsibilities, scales, and reporting formats. It is created during the Starting Up a Project process.
• Risk Register: The central record for all identified risks. It details each risk's description, status, probability, impact, proximity, risk owner, actionee, and planned responses. It is maintained throughout the project.
• Daily Log: Used by the Project Manager to record informal risks and issues that do not warrant inclusion in the formal Risk Register.

Risk Responses

Responses are tailored based on whether the risk is a threat or an opportunity:

• Threat Responses: Avoid (eliminate the threat), Reduce (lessen probability/impact), Transfer (shift responsibility to a third party), Accept (take no action, but monitor).
• Opportunity Responses: Exploit (ensure the opportunity occurs), Enhance (increase probability/impact), Share (partner with a third party), Reject (take no action, but monitor).

Effective risk management ensures that project decisions are made with a clear understanding of potential future events.

## The Purpose of the Change Theme

The Change theme in PRINCE2 provides a framework for identifying, assessing, and controlling any potential changes to the project's baselines (products, plans, and requirements). Its primary purpose is to ensure that only worthwhile changes are approved and implemented, preventing uncontrolled scope creep and maintaining the project's viability. It ensures that all project products are correctly identified, managed, and protected throughout their lifecycle.

## Key Concepts and Definitions

• Issue: A relevant event that has happened, was not planned, and requires management action. Issues are categorized into:
• Request for Change: A proposal for a change to a baseline.
• Off-Specification: Something that should be provided but currently isn't, or has been provided but does not meet its specification.
• Problem/Concern: Any other issue that the Project Manager needs to resolve or escalate.
• Configuration Item (CI): A product, component, or service that is subject to configuration management.
• Configuration Item Record (CIR): A record describing the status, version, and relationships of a CI.
• Change Authority: The person or group authorized by the Project Board to approve or reject Requests for Change and Off-Specifications. This could be the Project Board itself, a dedicated group, or the Project Manager for minor changes within agreed tolerances.
• Change Budget: A sum of money allocated to fund the implementation of approved changes, helping to manage financial impact.

## Managing Issues and Changes

The approach to managing issues and changes is defined in the Configuration Management Strategy. This strategy outlines how the project's products will be controlled, including planning, identification, control, status accounting, and verification. It also details the Change Control Approach, which describes the procedure for managing issues.

When an issue arises, it is captured in the Issue Register and detailed in an Issue Report. The Project Manager will analyze the issue, assess its impact on objectives, and recommend actions. For significant issues, particularly Requests for Change and Off-Specifications, they are referred to the Change Authority for a decision. The Change Authority will decide whether to approve, reject, defer, or seek more information. Approved changes are then implemented and tracked.

## Management Products and Responsibilities

Key management products for the Change theme include:

• Configuration Management Strategy: Defines how products are controlled and how changes are managed.
• Issue Register: A log of all formal issues raised.
• Issue Report: Provides details for a specific issue.

Responsibilities: The Project Board appoints the Change Authority and approves the Configuration Management Strategy. The Project Manager prepares the strategy, manages the Issue Register, and prepares Issue Reports. The Change Authority makes decisions on significant changes.

## Progress Theme Overview

The Progress Theme in PRINCE2 establishes mechanisms to monitor and compare actual achievements against planned objectives, forecast future performance, and control deviations. Its primary purpose is to ensure the project remains viable against its Business Case and to provide transparency to stakeholders regarding performance.

## Management by Exception and Tolerances

A core principle of PRINCE2, Management by Exception, is fundamental to progress control. This involves setting specific tolerances for each management level (project, stage, work package) across six performance targets: time, cost, quality, scope, benefits, and risk. Management by Exception means that the next level of management is only involved if these agreed tolerances are forecast to be exceeded, or have already been exceeded. This allows for efficient decision-making and saves management time.

## Reporting and Review Mechanisms

Effective progress control relies on regular reporting and reviews. Key reports include:

• Checkpoint Report: Produced by the Team Manager for the Project Manager, detailing work package progress.
• Highlight Report: Produced by the Project Manager for the Project Board, providing regular summaries of stage progress, issues, and forecasts.
• End Stage Report: Produced by the Project Manager at the end of each management stage, reviewing performance against the Stage Plan and updating the Business Case. This report is crucial for the Stage Boundary Review by the Project Board.
• End Project Report: Produced by the Project Manager at project closure, reviewing overall project performance and lessons learned. This supports the Project Closure Review.
• Exception Report: Raised by the Project Manager to the Project Board if a stage or project tolerance is forecast to be exceeded. This triggers the Project Board to decide on an Exception Plan.
• Lessons Report: Captures valuable lessons learned throughout the project or at stage/project end, contributing to organizational learning.

## Baselines and Control

All plans (Project Plan, Stage Plan, Team Plan) are baselined once approved. These baselines serve as the fixed reference points against which actual progress is measured. By monitoring progress against these baselines and reporting deviations, the Project Manager can maintain control, escalate issues when necessary, and ensure the project stays aligned with its objectives and the Business Case.

## Tailoring PRINCE2 to the Project Environment

Tailoring is the act of adapting PRINCE2 to suit the specific context of a project. It ensures that PRINCE2 is applied effectively and efficiently, avoiding unnecessary overhead while maintaining control. PRINCE2 is not a one-size-fits-all solution; it must be adjusted to fit the project's unique characteristics.

## Why Tailor?

The primary goal of tailoring is to ensure the project management method is appropriate for the project's scale, complexity, risk, and environment. This maximizes the benefits of using PRINCE2 by making it practical and effective, rather than a bureaucratic burden. Tailoring helps integrate PRINCE2 with the organization's existing management systems and culture.

## What to Tailor?

Tailoring involves adapting various elements of PRINCE2:

• Processes: Steps within processes can be combined, split, or adapted. For example, a simple project might combine aspects of Starting Up a Project and Initiating a Project.
• Themes: The level of detail and formality for applying each of the seven themes (e.g., Business Case, Organization, Quality, Plans, Risk, Change, Progress) should be tailored. A low-risk project might require less formal risk management.
• Roles: While the minimum structure of the Project Board, Project Manager, and Team Manager must remain, responsibilities can be combined or delegated. For instance, a Project Manager might also act as a Team Manager on a small project.
• Management Products: The content, format, frequency of updates, and recipients of management products (e.g., Project Brief, PID, Checkpoint Report) should be tailored. A small project might use a combined Project Brief/Business Case and less formal reports.

## Factors Influencing Tailoring

Several factors dictate how PRINCE2 should be tailored:

• Project Scale: Size, duration, and complexity.
• Project Type: Commercial, internal, R&D, IT, construction, etc.
• Organizational Context: Culture, maturity, existing standards, governance structures.
• Project Environment: Regulatory requirements, geographical distribution, supplier relationships, security needs.
• Project Approach: Whether an agile, waterfall, or hybrid approach is used.

## Who is Responsible and When?

The Project Manager is typically responsible for proposing the tailored approach. This proposal is then reviewed and approved by the Project Board, often as part of the Project Initiation Documentation (PID). Tailoring decisions are primarily made during the Starting Up a Project and Initiating a Project processes, and documented in the Project Approach section of the PID. Tailoring should be periodically reviewed and adjusted if the project context changes.

## Key Principles of Tailoring

Crucially, the seven PRINCE2 Principles are non-negotiable and must always be applied. Tailoring is about *how* these principles are applied, not *whether* they are applied. The aim is to achieve effective project governance and control without adding unnecessary bureaucracy.