Definition of PRINCE2
PRINCE2, for PRojects IN Controlled Environments, is a structured project management method. Defining PRINCE2 amounts to describing what it sets: who decides, when and on the basis of which documents. It is generic, meaning independent of the sector and the nature of the project, and says nothing about the techniques specific to a given profession.
The method was born in the UK civil service, initially for IT projects, before being extended to all projects. It is particularly widespread in the United Kingdom and the rest of Europe. It has gone through successive editions, the most recent being version 7, published in 2023. It is now maintained by PeopleCert, which acquired AXELOS, its previous owner, in 2021.
What PRINCE2 is for
PRINCE2 addresses a governance problem more than a planning one. Three ideas follow from this.
A project only exists as long as it remains justified. The business case, which sets out why the project is worth its cost, is re-examined at each stage rather than filed away after launch.
Directing and managing the project are separated. A project board, made up of the representative of the business interest (the executive), that of the users and that of the suppliers, takes the decisions. The project manager runs the work day to day within the limits set for them.
The project moves forward in stages. At the end of each one, the board decides to continue, redirect or stop. Between two decisions, the project manager has tolerances (on time, cost or scope, in particular) and only alerts the board if they forecast exceeding them: this is management by exception.
The seven principles
The principles are the rules a project must comply with in order to claim to follow the method.
- Continued business justification.
- Learning from experience.
- Defined roles and responsibilities.
- Management by stages.
- Management by exception.
- A focus on products, that is, on what must be delivered.
- Tailoring the method to the project environment.
The last principle is often forgotten. Applying every PRINCE2 document to a small project is a methodological error, not an excess of rigour.
Themes and processes
The themes are the aspects of project management to be addressed continuously. There are seven of them: business case, organisation, quality, plans, risk, change and progress. Version 7 speaks of “practices” rather than themes and keeps seven of them.
The processes describe how the project unfolds, from the initial mandate to closure, and specify who does what at each moment.
| Process | Purpose |
|---|---|
| Starting up a project | Check, before any commitment, that the project is viable and worth initiating |
| Directing a project | Project board decisions, from start to finish |
| Initiating a project | Establish the foundations: plan, detailed business case, management approaches |
| Controlling a stage | Assign work, track progress, handle issues and change requests |
| Managing product delivery | Delivery of work packages by the teams |
| Managing a stage boundary | Review of the stage and preparation of the next one for decision |
| Closing a project | Final acceptance, handover to operations, review |
The Foundation and Practitioner levels
The method comes with individual certifications at two main levels. Foundation attests to knowledge of the method and its vocabulary. Practitioner attests to the ability to apply it to a project situation and tailor it.
Entry requirements, exam format and renewal rules are set by the organisation that owns the method and change over time. They should be checked with it or with an accredited training organisation.
PRINCE2, PMBOK and PMP: not to be confused
| PRINCE2 | PMBOK Guide | PMP | |
|---|---|---|---|
| Nature | Method | Body of knowledge guide | Individual certification |
| Origin | UK civil service | Project Management Institute | Project Management Institute |
| Question addressed | Who decides what, and when? | Which practices and techniques should be used? | Can this person lead a project? |
PRINCE2 is prescriptive about governance and says little about techniques: it details neither effort estimation nor team leadership. The PMBOK does the opposite: it catalogues practices without imposing an organisational model. The two therefore combine well. PMI credentials are described in our entry on PMI certifications.
Nor should PRINCE2 be confused with ITIL, which comes from the same administration and deals with IT service management rather than projects.
Example: management by exception in practice
A project to replace an invoicing application is divided into four stages. For the second, the project board grants the project manager a time and cost tolerance. Halfway through, data migration turns out to be heavier than planned and the forecast exceeds the tolerance.
The project manager does not decide alone and does not wait for the next board meeting. They write an exception report setting out the situation, the options and their consequences for the business case. The board chooses: reduce the migration scope, grant more time or stop. The decision is taken by those who own the project’s justification, at a moment when it is still useful.
To set up a management framework inspired by these principles, see our page devoted to setting up and strengthening a PMO.