PRINCE2
Also known as: PRojects IN Controlled Environments, PRINCE2 Methodology
A structured project management methodology that divides projects into manageable stages with defined roles, processes, and controls, providing clear governance and accountability for project delivery.
Quick Reference
Memory Aid
Justify → Plan in stages → Control with tolerances → Escalate exceptions → Review business case at every gate.
TL;DR
Divide projects into managed stages with board go/no-go decisions at each gate. The PM manages within tolerances; exceptions are escalated. The business case is reviewed at every stage — if it no longer holds, stop.
What Is PRINCE2?
PRINCE2 gives you a structured approach to running projects with clear stages, roles, and decision points. The project board (senior management) makes go/no-go decisions at each stage gate, and the project manager manages day-to-day within defined tolerances.
PRINCE2 is a structured project management method based on experience drawn from thousands of projects — and from the contributions of countless project sponsors, project managers, project teams, academics, trainers, and consultants.
— AXELOS, Managing Successful Projects with PRINCE2
PRINCE2 is built on seven principles (continued business justification, learn from experience, defined roles, manage by stages, manage by exception, focus on products, tailor to the environment), seven themes (business case, organization, quality, plans, risk, change, progress), and seven processes (starting up, directing, initiating, controlling a stage, managing product delivery, managing stage boundaries, closing). The methodology separates direction (project board) from management (project manager) from delivery (team managers).
PRINCE2 Process Model
Seven processes that guide a project from startup through controlled stages to a managed close.
Starting Up
Is the project viable?
Initiating
Plan the project
Controlling a Stage
Manage day-to-day
Managing Boundaries
Stage gate reviews
Closing
Hand over & evaluate
Origin & Context
Originally developed by the UK government's Central Computer and Telecommunications Agency. PRINCE2 is widely used in the UK, Europe, Australia, and globally, especially in government and regulated industries.
Core Components
Business Case
A living document that justifies the project and is reviewed at every stage gate.
Example
If the business case no longer holds at a stage gate, the project board can stop the project — preventing good money chasing bad.
Stages
The project is divided into management stages, each requiring board approval to proceed.
Example
A large IT project divided into: Feasibility, Design, Build, Test, Deploy — each requiring a go/no-go decision.
Tolerances
Defined ranges for time, cost, quality, scope, risk, and benefit that the project manager can operate within.
Example
The PM has tolerance of +/- 10% on budget. If exceeding, they must escalate to the project board.
Exception Management
When tolerances are forecast to be exceeded, escalation to the next management level occurs.
Example
The PM forecasts the stage will exceed budget by 15% (beyond 10% tolerance), so escalates to the board with an exception report and options.
Did You Know?
PRINCE2 is used in over 150 countries and is the de facto standard for project management in the UK, Australia, and many European governments. The original PRINCE (Projects IN Controlled Environments) was developed in 1989 by the UK government's Central Computer and Telecommunications Agency.
When to Use PRINCE2
Government and public sector projects
Problem it solves: Provides the governance, accountability, and audit trail required in public sector environments.
Real-World Application
UK government mandates PRINCE2 for all IT projects, ensuring consistent governance and the ability to stop failing projects at stage gates.
Regulated industry projects
Problem it solves: Creates the documentation, controls, and approval processes that regulated industries require.
Real-World Application
A pharmaceutical company uses PRINCE2 for clinical trial management, ensuring regulatory compliance at each stage gate.
PRINCE2 is designed to be tailored. The biggest mistake is applying it rigidly. Tailor the method to fit the project's size, complexity, and environment.
How to Apply PRINCE2: Step by Step
Before You Start
- →Understanding of PRINCE2 principles and processes
- →Project board with authority to make go/no-go decisions
- →Clear project mandate from corporate management
Starting Up
Appoint the project team, create the project brief, and plan the initiation stage.
Tips
- ✓Keep this short — it's about deciding whether to invest in proper initiation
Common Mistakes
- ✗Spending too long on startup when the real planning happens in initiation
Initiation
Create the detailed project plan, business case, and project management strategies.
Tips
- ✓Define tolerances clearly at this stage
Common Mistakes
- ✗Creating plans that are too detailed for the level of uncertainty
Stage-by-Stage Delivery
Execute the project in stages, with board approval at each gate.
Tips
- ✓Use exception management — don't wait until problems are critical to escalate
Common Mistakes
- ✗Hiding problems instead of escalating when tolerances are threatened
Closing
Formally close the project, capture lessons, and hand over products.
Tips
- ✓Always capture lessons learned — this feeds into future projects
Common Mistakes
- ✗Rushing closure without proper handover and lessons learned
Value & Outcomes
Primary Benefit
Provides clear governance and accountability with stage-gate decision points that prevent failing projects from continuing.
Additional Benefits
- ✓Continued business justification principle ensures projects remain worthwhile
- ✓Exception management prevents micromanagement while maintaining control
What You'll Learn
- →How to structure projects with clear governance
- →How to use stage gates and tolerances for effective project control
Typical Outcomes
Best Practices
📋 Preparation
- •Tailor the method to the project size and complexity
- •Ensure the project board has the right authority and availability
🚀 Execution
- •Use tolerances and exception management actively
- •Review the business case at every stage gate
🔄 Follow-Up
- •Capture and share lessons learned
- •Verify benefits realization after project closure
💎 Pro Tips
- •PRINCE2 and Agile are not mutually exclusive — PRINCE2 Agile combines PRINCE2 governance with agile delivery
The continued business justification principle is PRINCE2's greatest contribution. At every stage gate, the question 'Is this project still worth doing?' must be answered affirmatively — or the project should stop.
London 2012 Olympics
The London 2012 Olympic Games delivery program used PRINCE2 to manage 70+ major infrastructure projects worth over £9.3 billion, delivered on time and under budget — one of the most successful megaproject deliveries in history.
Limitations & Pitfalls
Can be document-heavy and bureaucratic if not tailored
Mitigation: Tailor aggressively — use only the documents and processes the project needs
Sequential stage approach may not suit fast-changing environments
Mitigation: Use PRINCE2 Agile for projects needing flexibility within governance
Apply PRINCE2 with Stratrix
Turn this framework into a professional strategy deck in under a minute. Stratrix applies PRINCE2 automatically to your business context.
Try Stratrix Free