1. What is PRINCE2 and who uses it?
PRINCE2 is the world's most widely used structured project management method outside North America. It was developed in 1989 by the UK Government's Central Computer and Telecommunications Agency — originally for government IT projects. Today it is owned by AXELOS (a Capita joint venture) and applied in more than 150 countries, with strongholds in the UK, the Netherlands, Germany, Australia and Poland.
Typical adopters are public sector (mandated by the UK Government), banks and insurers (clear audit trails through documented decisions), consultancies (a scalable framework across projects) and infrastructure companies (large projects with many stakeholders). In the UK over 60 % of project managers hold a PRINCE2 certification.
What sets PRINCE2 apart: while PMBOK is a knowledge base and Scrum is a delivery framework, PRINCE2 prescribes a concrete end-to-end flow — from pre-project preparation to formal closure. It is also one of the few methods that elevates tailoring to a first-class principle: you do not apply PRINCE2 1:1, you adapt it to your project.
2. The 7 Principles
The principles are the foundation — they apply always, in every PRINCE2 project, without exception. They are universal, self-explanatory and shape the project manager's mindset.
- Continued business justification: The business case must remain valid at every point. If the justification disappears, the project is stopped or adjusted — not continued by inertia.
- Learn from experience: Lessons are collected at the start (from past projects), documented during delivery and fed back to the organisation at the end. Mandatory artefact: the Lessons Log.
- Defined roles and responsibilities: Three stakeholder groups must be represented: the business (executive), users (senior user) and supplier (senior supplier). Without this triad, it isn't a PRINCE2 project.
- Manage by stages: The project is split into at least two stages (initiation + ≥1 delivery stage). At the end of each stage the Project Board decides whether to continue.
- Manage by exception: Every level has defined tolerances (time, cost, quality, scope, risk, benefit). As long as the project runs within tolerances, the project manager has autonomy. Only on breach does it escalate upwards.
- Focus on products: Plan around deliverables (products), not activities. Each product has a Product Description with quality criteria. This forces clarity on the "what" before the "how".
- Tailor to the environment: PRINCE2 is a method, not a rulebook. Adapt it to project size, complexity, sector and culture. Tailoring choices are documented in the PID with reasoning.
Common mistake: Tailoring is confused with "leaving PRINCE2 bits out". Tailoring means: all 7 principles still apply, you only adapt how (documentation depth, role combinations, number of stages) to the project reality.
3. The 7 Themes
Themes are continuous aspects you must manage throughout the project. They answer: what must I keep paying attention to?
| Theme | Core question | Key artefact |
|---|---|---|
| Business Case | Why? | Business Case document |
| Organization | Who? | Org chart + role descriptions |
| Quality | What must the result achieve? | Quality Management Approach + Quality Register |
| Plans | How and when? | Project Plan, Stage Plan, Team Plan |
| Risk | What can go wrong? | Risk Register |
| Change | How do we handle adjustments? | Issue Register, Change Control Approach |
| Progress | Where are we? | Highlight Report, Checkpoint Report, Exception Report |
The themes interlock: the Business Case drives decisions, the Organization defines who decides, the Plans translate strategy into activities — while Risk, Quality, Change and Progress monitor the live work.
4. The 7 Processes
Processes describe the chronological flow of the project — from first idea to formal closure. Each process has a clear purpose, defined inputs, activities and outputs.
- Starting up a Project (SU): Before the project officially starts. Check whether the project even makes sense. Outputs: a Project Brief, a first risk assessment, the appointed project management team. Duration: typically 1–3 weeks.
- Directing a Project (DP): The Project Board decides at stage boundaries whether the project continues, is adjusted or stopped. This process runs in parallel across the whole life cycle.
- Initiating a Project (IP): The real project setup. Outputs: the PID (Project Initiation Documentation), the detailed Business Case, the Project Plan and all strategies (risk, quality, configuration, communication).
- Controlling a Stage (CS): The project manager's day-to-day work during each delivery stage: authorise work packages, monitor progress, manage issues and risks, write Highlight Reports.
- Managing Product Delivery (MP): The Team Manager / supplier view: accept work packages, execute, ensure quality, mark complete.
- Managing a Stage Boundary (SB): At the end of each stage: assess the current stage, plan the next stage, update the Business Case and Risk Register, present to the Project Board for sign-off.
- Closing a Project (CP): Planned or premature project closure. Handover to operations, lessons learned, acceptance documentation, formal end of project.
5. PRINCE2 vs PMBOK vs Agile
The most frequent question during method selection: when PRINCE2, when PMBOK, when Agile?
| Criterion | PRINCE2 | PMBOK | Agile (Scrum) |
|---|---|---|---|
| Type | Process model | Knowledge standard | Delivery framework |
| Origin | UK Government, 1989 | PMI USA, 1987 | Agile Manifesto, 2001 |
| Strength | Governance, clear decision points | Breadth, completeness (49 processes, 10 knowledge areas) | Adaptiveness, fast feedback |
| Weakness | Documentation-heavy, few prescribed tools | Very broad, hard to apply in full | Weaker for fixed scope / fixed date |
| Best fit | Public sector, compliance, large projects | Diverse project types, US-centric | Software, product, R&D |
| Certification | Foundation + Practitioner | PMP, CAPM | PSM, CSM, PSPO |
Practical takeaway: the three methods are not mutually exclusive. PRINCE2 Agile (official since 2015) combines PRINCE2's governance strength with agile delivery flexibility. Concretely: PRINCE2 governs "management", Scrum or Kanban govern "doing".
6. When PRINCE2 pays off — and when it doesn't
PRINCE2 is not universally the best choice. It earns its weight in structure-hungry environments.
PRINCE2 pays off when:
- The project has multiple sponsors/stakeholder groups that must align on decisions
- There are regulatory or compliance requirements (banks, pharma, public sector)
- The business case is volatile and needs regular reviews
- The project runs over months or years and needs clear stage boundaries
- You manage suppliers (clear Team Manager ↔ Supplier interface)
PRINCE2 is not the best fit when:
- The project is small (< 3 months, < 5 people) and the overhead isn't justified
- Requirements are extremely volatile and a fully agile setup fits better
- The team has never used structured methodology (steep learning curve)
- There is no appetite for separating roles cleanly (Board, PM, Team Manager)
Field tip: If your project exceeds £50k / €50k and has more than 2 stakeholder groups, tailored PRINCE2 is almost always better than freestyle PM. Cut documentation to 4-5 core docs (Business Case, PID, Risk Register, Highlight Report, Lessons Log) and keep the principles.
7. Certification: Foundation and Practitioner
Official PRINCE2 certification runs through accredited training organisations (ATOs). Two levels:
PRINCE2 Foundation
Confirms basic understanding. Multiple-choice exam: 60 questions in 60 minutes, pass mark 55 % (33/60). No prerequisites. Prep time: 3-day course + 8–12 hours of self-study. Cost in DACH/UK: €1,200–2,000 / £1,000–1,800 incl. exam.
PRINCE2 Practitioner
Confirms the ability to apply PRINCE2 to real projects. Scenario-based exam: 70 questions in 150 minutes, pass mark 55 %. Prerequisite: passed Foundation. Prep time: another 2-day course + 15–20 hours self-study. Extra cost: €900–1,500 / £800–1,300.
Re-registration: Practitioner is valid for 3 years; renew via a shorter re-registration exam — or stay current with CPD points through the My AXELOS programme.
8. PRINCE2 in practice: a compact example
Example: rolling out a new CRM at a 500-employee company. Budget €280k, duration 9 months.
Start-up (SU, 2 weeks): The Sales Director (Project Sponsor) commissions a Project Mandate. The Project Brief emerges: pain points in the current tool, target state, rough budget €280k, projected ROI 18 months. Project Board is formed: Executive (CFO), Senior User (Sales Director), Senior Supplier (Head of IT).
Initiation (IP, 4 weeks): PID with detailed Business Case, four stages (Setup, Migration, Pilot, Roll-out), Risk Register with 23 risks, Communication Strategy. Project Board signs off — Stage 1 starts.
Stages 1–4 (CS + SB, 6–10 weeks each): Highlight Reports every 2 weeks, stage-boundary reviews at each handover. During migration: a critical risk materialises (data quality worse than expected). Tolerance breached — Exception Report to the Board. Decision: +6 weeks, +€32k. Business Case still valid. Continue.
Closure (CP, 2 weeks): Lessons Learned documented (notably "test data quality earlier"). Handover to operations. Project Board formally accepts — project closed.
What was PRINCE2-specific here? Three things: (1) The clear triad (Executive / Senior User / Senior Supplier) forced decision-makers to one table. (2) Manage-by-exception avoided permanent escalation — only one real escalation in 9 months. (3) The stage structure allowed adjustment without putting the whole project at risk.
9. Bottom line
PRINCE2 is not a favourite-method debate — it's a proven tool for situations where clarity over roles, stages and escalation paths matters more than flexibility. Calling it "bureaucratic" usually means missing that all 7 principles — including tailoring — apply. The effort can be radically scaled to project size.
For English-speaking project managers, PRINCE2 is particularly valuable with clients in the UK, NL, AU or the public sector — and on projects with complex stakeholder landscapes. Foundation is a solid entry point (3 days investment), Practitioner a clear career signal (another 2). Even without certification, the 7 principles are universally applicable.