What is PRINCE2?
PRINCE2 (PRojects IN Controlled Environments) is a structured project management methodology originally developed by the UK government in 1989 and now owned by PeopleCert, which acquired AXELOS in 2021. It provides a process-driven framework that divides projects into manageable and controllable stages, with clear templates, defined roles, and built-in governance at every level.
Unlike methodologies that focus on a single aspect of delivery, PRINCE2 addresses the full project lifecycle from initial concept through to controlled closure. It is process-based rather than prescriptive, meaning it can be tailored to suit projects of any scale, industry, or complexity. The methodology is structured around three interconnected pillars: 7 principles that act as guiding obligations, 7 themes that describe aspects of project management to be addressed continuously, and 7 processes that define the step-by-step journey from start-up to close.
PRINCE2 remains mandatory for all UK central government projects and is widely adopted across the NHS, local authorities, defence, financial services, and the private sector. Its strength lies in its emphasis on business justification, defined roles, and the ability to tailor the framework without losing control.
The 7 Principles
The 7 principles are the non-negotiable foundations of PRINCE2. They are universal obligations that apply to every PRINCE2 project regardless of its size, sector, or complexity. If any principle is not applied, the project is not being run as a PRINCE2 project. Think of them as the rules of the game — you can tailor how you play, but you cannot remove the rules themselves.
The 7 PRINCE2 Principles Explained
| Principle | What It Means | In Practice |
|---|---|---|
| Continued Business Justification | The project must have a valid, documented reason to exist throughout its lifecycle | Review the Business Case at every stage boundary; stop the project if justification no longer holds |
| Learn from Experience | Teams must seek, record, and act on lessons from previous and current projects | Maintain a Lessons Log from day one; review lessons from similar past projects during initiation |
| Defined Roles & Responsibilities | Everyone involved must understand what they are accountable for and what authority they hold | Use the PRINCE2 organisation structure: Project Board, Project Manager, Team Manager, Project Assurance |
| Manage by Stages | The project is planned, monitored, and controlled one management stage at a time | Break the project into at least two stages (initiation + delivery); seek board approval at each boundary |
| Manage by Exception | Tolerances are set for each level of management; escalation happens only when tolerances are forecast to be exceeded | Define time, cost, scope, risk, quality, and benefit tolerances; report by exception rather than constant oversight |
| Focus on Products | The project is output-driven; what will be delivered is defined before how it will be delivered | Write Product Descriptions with clear quality criteria before planning activities; use a Product Breakdown Structure |
| Tailor to Suit the Project Environment | PRINCE2 must be adapted to the project's size, complexity, importance, and risk | Scale management products up or down; combine roles on small projects; adjust reporting frequency |
Source: PRINCE2 7th Edition (PeopleCert / AXELOS, 2023)
Tailoring Is Not Optional — It Is a Principle
One of the most common mistakes practitioners make is applying PRINCE2 "by the book" without adapting it. The 7th principle explicitly requires you to tailor the methodology to your project environment. A three-month internal project does not need the same governance structure as a multi-year government programme. Under-tailoring creates unnecessary bureaucracy; over-tailoring removes the controls that make PRINCE2 effective.
The 7 Themes
The 7 themes are aspects of project management that must be addressed continuously throughout the project. While the principles tell you what you must always do, the themes tell you what you must always manage. Each theme provides guidance on how to handle a critical dimension of the project, and each can be tailored in terms of the level of detail and formality applied.
The 7 PRINCE2 Themes
| Theme | Key Question It Answers | Core Activities |
|---|---|---|
| Business Case | Why is this project worth doing? | Develop, maintain, and verify the Business Case; ensure continued justification at each stage gate |
| Organisation | Who is responsible for what? | Define the project management team structure; assign roles across four levels (corporate, directing, managing, delivering) |
| Quality | What are the acceptance criteria and how will we verify them? | Define quality expectations, write Product Descriptions, plan quality reviews, maintain the Quality Register |
| Plans | How will we deliver, how much will it cost, and when? | Create Project Plan, Stage Plans, and Team Plans; use product-based planning technique |
| Risk | What if things go wrong (or right)? | Identify, assess, and manage threats and opportunities; maintain the Risk Register; apply risk responses (avoid, reduce, transfer, accept, share, exploit) |
| Change | How do we handle requests for change and off-specification items? | Operate issue and change control procedures; assess impact on time, cost, quality, scope, risk, and benefits; maintain the Issue Register |
| Progress | Where are we now, where are we going, and should we continue? | Establish controls (tolerances, reporting, reviews); produce Highlight Reports and End Stage Reports; trigger exception management when needed |
Source: PRINCE2 7th Edition (PeopleCert / AXELOS, 2023)
Each theme is interwoven with the others. For example, the Business Case theme relies on the Risk theme to quantify threats to the investment, and the Plans theme depends on the Quality theme to define what products need to be delivered. Understanding these connections is the key to applying PRINCE2 effectively rather than treating each theme in isolation.
The Business Case Is the Golden Thread
If there is one theme that underpins everything else, it is the Business Case. Every decision in PRINCE2 — whether to approve a stage, accept a change, or close the project — should be traced back to the question: does this still deliver value? If the Business Case is weak, the entire project governance structure has nothing meaningful to protect.
The 7 Processes
The 7 processes describe the chronological journey of a PRINCE2 project from the initial trigger through to formal closure. Each process contains a set of activities, each with defined inputs, outputs, and recommended responsibilities. Together, they provide a complete lifecycle that ensures nothing is overlooked and that governance is maintained at every stage.
The 7 PRINCE2 Processes
| Process | Purpose | Who Leads It |
|---|---|---|
| Starting Up a Project (SU) | Ensure the prerequisites for initiating the project are in place; appoint the team, create the Project Brief and outline Business Case | Executive and Project Manager |
| Directing a Project (DP) | Enable the Project Board to make key decisions, authorise stages, and provide overall direction throughout the project | Project Board |
| Initiating a Project (IP) | Establish a solid foundation by creating the PID, detailed Business Case, Project Plan, and all control strategies | Project Manager |
| Controlling a Stage (CS) | Assign work, monitor progress, deal with issues, report to the board, and take corrective action within a management stage | Project Manager |
| Managing Product Delivery (MP) | Ensure products are created, quality-checked, and approved according to the agreed Work Packages | Team Manager |
| Managing a Stage Boundary (SB) | Report on the current stage, update the Business Case and Project Plan, and prepare the next Stage Plan for board approval | Project Manager |
| Closing a Project (CP) | Confirm product acceptance, hand over deliverables, record lessons, plan post-project benefits reviews, and formally close | Project Manager |
Source: PRINCE2 7th Edition (PeopleCert / AXELOS, 2023)
In practice, Directing a Project runs throughout the entire lifecycle — it is the process through which the Project Board exercises its authority. The other six processes are sequential or iterative. Controlling a Stage and Managing Product Delivery run in parallel within each management stage, while Managing a Stage Boundary occurs at the transition between stages.
The Project Board Must Actually Direct
One of the most frequent failures in PRINCE2 projects is a passive Project Board. The Directing a Project process is not ceremonial — it requires the board to actively authorise each stage, make decisions on escalated issues, and confirm the project should continue. If your board only meets at the start and end, you are missing the governance that makes PRINCE2 work.
Tailoring PRINCE2 for Small Projects
PRINCE2 is often criticised as being "too heavy" for smaller projects, but this is a misunderstanding. The methodology is explicitly designed to be scaled. The 7th principle — Tailor to Suit the Project Environment — makes adaptation a core requirement, not an afterthought. The challenge is knowing what to scale down and what to keep.
For a small project with a budget under £50,000 and a duration of three months or less, you might have a single delivery stage (after initiation), combine the Project Manager and Team Manager roles into one person, and reduce the Project Board to a single Executive who acts as the decision-maker. Documentation can be simplified — a one-page Business Case, a combined PID and Stage Plan, and verbal Highlight Reports — as long as the intent behind each management product is preserved.
Tailoring Guide: Full vs. Small Project
| Element | Full PRINCE2 Project | Small Project Tailoring |
|---|---|---|
| Management Stages | Multiple stages with formal stage gates | Two stages: initiation + single delivery stage |
| Project Board | Executive, Senior User, Senior Supplier (separate people) | One person as Executive combining user/supplier interests |
| Business Case | Detailed document with investment appraisal, options analysis, benefits management | One-page justification covering costs, benefits, risks, and timescales |
| PID | Comprehensive document referencing all strategies and plans | Combined with Stage Plan into a single short document |
| Highlight Reports | Formal written reports at regular intervals | Brief email update or verbal report at weekly stand-up |
| Risk Register | Detailed register with probability, impact, proximity, response actions | Simple risk list with owner, likelihood, impact, and planned response |
| Quality Reviews | Formal quality reviews with chair, presenter, and reviewers | Peer review or sign-off by a single quality checker |
Source: PRINCE2 7th Edition — Tailoring Guidance
What You Should Never Skip
No matter how small the project, never remove the Business Case, defined roles, or stage-gate governance. These are the minimum controls that distinguish a managed project from an uncontrolled task. You can simplify how you document them — a paragraph instead of a 20-page report — but the thinking behind them must still happen. A project without a Business Case is just activity without justification.
PRINCE2 Management Products
PRINCE2 defines 26 management products (documents and records) that support the governance and control of the project. You do not need to produce all 26 on every project — the principle of tailoring applies — but you need to understand what each one does so you can make informed decisions about which to include and at what level of detail.
The table below covers the most important management products that you are likely to use on the majority of projects. Each serves a specific purpose at a specific point in the lifecycle.
Key PRINCE2 Management Products
| Management Product | Purpose | When It Is Used |
|---|---|---|
| Business Case | Documents the justification for the project including costs, benefits, risks, and timescales | Created in Starting Up; refined in Initiation; reviewed at every stage boundary |
| Project Initiation Documentation (PID) | Provides a single reference point for what the project is about, how it will be managed, and what it will deliver | Created during Initiating a Project; baselined and used throughout |
| Project Plan | High-level plan showing major products, milestones, costs, and timescales for the entire project | Created during Initiation; updated at each stage boundary |
| Stage Plan | Detailed plan for the current management stage including activities, resources, and schedules | Created during Managing a Stage Boundary (or Initiation for the first stage) |
| Highlight Report | Regular progress report from the Project Manager to the Project Board | Produced at agreed intervals during each management stage (e.g. fortnightly) |
| End Stage Report | Reviews the current stage's performance against the Stage Plan and updates the Business Case | Produced at the end of each management stage for board review |
| Risk Register | Records identified risks, their assessment, owners, and planned responses | Created during Initiation; maintained throughout the project |
| Issue Register | Records all issues (problems, requests for change, off-specifications) and their status | Created during Initiation; maintained throughout the project |
| Lessons Log | Records lessons learned during the project for use on current and future projects | Created in Starting Up; updated throughout; summarised in Lessons Report at close |
| Work Package | Agreement between the Project Manager and a Team Manager defining the work to be done and its constraints | Created during Controlling a Stage; accepted in Managing Product Delivery |
| Product Description | Defines a product's purpose, composition, quality criteria, and quality method | Created during product-based planning; used to verify product quality |
| End Project Report | Reviews the project's overall performance, compares actuals to plan, and summarises lessons and follow-on actions | Produced during Closing a Project |
Source: PRINCE2 7th Edition — Management Products
In practice, the Business Case, PID, and Risk Register are the three products you will reference most frequently. The Highlight Report is the primary communication tool between the Project Manager and the board. On smaller projects, several products can be combined — for example, the Stage Plan can be incorporated into the PID, and the Issue Register and Risk Register can be maintained in a single spreadsheet with separate tabs.
Management Products Are Tools, Not Bureaucracy
The purpose of management products is to support decision-making, not to fill filing cabinets. Every document should answer a question that someone needs answered: "Should we continue?" (Business Case), "What has been delivered?" (End Stage Report), "What could go wrong?" (Risk Register). If a document does not help anyone make a better decision, it needs to be simplified or removed.
Get Qualified in Project Management
PRINCE2 is essential knowledge for anyone managing or contributing to projects in the UK. Our accredited Project Management course covers the full PRINCE2 framework — principles, themes, processes, and management products — along with practical application techniques that prepare you to manage real projects with confidence and control.
Explore Our Project Management Course