PRINCE2 (PRojects IN Controlled Environments) is a structured, process-based project management methodology developed by the UK government. It is one of the most widely used methodologies globally, especially in Europe, Australia, and government sectors. Unlike Agile, which is a mindset, PRINCE2 is a prescriptive framework — it tells you exactly what to do, when, and by whom.
The 7 Principles
PRINCE2 is built on seven principles that are non-negotiable. If a project doesn't follow all seven, it's not a PRINCE2 project:
1. Continued Business Justification
There must be a valid reason to start and continue the project. If the business case is no longer valid, the project should be stopped.
2. Learn from Experience
Teams seek and use lessons from previous projects. Lessons are documented throughout, not just at the end.
3. Defined Roles & Responsibilities
Everyone knows who does what. There's no ambiguity about authority, decision-making, or accountability.
4. Manage by Stages
The project is planned, monitored, and controlled on a stage-by-stage basis, with formal go/no-go decisions between stages.
5. Manage by Exception
Each management level sets tolerances (time, cost, scope, risk). Issues only escalate when tolerances are forecast to be exceeded.
6. Focus on Products
PRINCE2 is output-oriented. The project is driven by the agreed product descriptions — what needs to be delivered and to what quality standard.
7. Tailor to the Environment
PRINCE2 must be adapted to suit the project's size, complexity, importance, and risk. It should never be applied blindly.
The 7 Themes
Themes are aspects of project management that must be addressed continuously throughout the project:
- Business Case: Why is the project worth doing? This is a living document, reviewed at each stage boundary.
- Organization: Who is involved and what are their roles? PRINCE2 defines a clear hierarchy — Project Board, Project Manager, Team Manager.
- Quality: What are the quality expectations and how will they be verified? Product descriptions define acceptance criteria upfront.
- Plans: How, how much, and when? PRINCE2 uses three levels of plans — Project Plan, Stage Plan, and Team Plan.
- Risk: What if things go wrong? Risks are identified, assessed, and managed using a structured approach (identify, assess, plan, implement, communicate).
- Change: How do we handle changes to the agreed baseline? All changes go through a formal change control process.
- Progress: Where are we now, where are we going, and should we carry on? PRINCE2 uses tolerances and exception reports to monitor progress.
The 7 Processes
PRINCE2 defines seven processes that cover the project lifecycle from start to finish:
SU
Starting Up a Project
Appoint the team, create outline business case, define the project approach. Pre-project phase.
IP
Initiating a Project
Build the Project Initiation Document (PID): detailed business case, plans, risk register, quality approach.
DP
Directing a Project
The Project Board makes key decisions — authorize stages, respond to exceptions, and close the project.
CS
Controlling a Stage
The Project Manager's day-to-day work — assign work, monitor progress, handle issues, report to the Board.
MP
Managing Product Delivery
The Team Manager accepts, executes, and delivers work packages. Bridge between PM and the team.
SB
Managing a Stage Boundary
Review the current stage, plan the next, update the business case. The Board decides to continue or stop.
CP
Closing a Project
Formal handover, document lessons learned, confirm acceptance, release resources, evaluate benefits.
PRINCE2 Roles
| Role | Responsibility |
|---|---|
| Project Board | Strategic direction and decision-making. Comprises the Executive (business), Senior User (user needs), and Senior Supplier (delivery capability). |
| Project Manager | Day-to-day management within the tolerances set by the Board. Produces plans, manages risk, and reports progress. |
| Team Manager | Manages work package delivery. Reports to the PM. In small projects, the PM may fill this role. |
| Project Assurance | Independent oversight ensuring the project stays on track. Each Board member may delegate assurance to specialists. |
| Change Authority | Delegated authority to approve or reject change requests within defined limits. |
When to Use PRINCE2
- Government and public sector — PRINCE2 is often mandatory or strongly preferred
- Large, complex projects — the structured governance and stage gates provide necessary control
- Projects requiring formal accountability — clear audit trails and defined decision rights
- Multi-vendor environments — the roles and responsibilities framework helps manage multiple suppliers
- Regulated industries — the documentation and process rigor support compliance requirements
PRINCE2 is often compared to PMBOK, but they serve different purposes. PMBOK is a body of knowledge — a reference of best practices. PRINCE2 is a methodology — a step-by-step process you follow. Many practitioners combine both: using PRINCE2's structure with PMBOK's detailed techniques for estimating, scheduling, and risk analysis. Since 2017, PRINCE2 Agile has also been available, blending PRINCE2 governance with Agile delivery methods.