PRINCE2 (PRojects IN Controlled Environments) is a project management method that separates governance from delivery. The project board makes decisions, while the project manager executes within predefined tolerances (cost, time, scope, quality, risk, and benefits). This distinction, often misunderstood, is the central mechanism that allows the method to work on projects of very different sizes.
PRINCE2 governance and Agile delivery: an underused combination
Most guides present PRINCE2 and Agile as two parallel worlds. The operational reality is more nuanced: PRINCE2 manages governance, while Agile manages delivery. They operate at different levels of the project and do not necessarily conflict.
In practice, a PRINCE2 project board approves the business case, sets tolerances for each stage, and decides whether to continue or stop the project. At the same time, the delivery team can work in Scrum sprints or use a Kanban flow within each stage. PRINCE2 version 7, published in September 2023, explicitly strengthens this compatibility with other approaches, including Agile and Lean.
For the two approaches to work together, a connection point must be defined: the PRINCE2 end-stage review coincides with the end of one or more sprints. The project manager consolidates Agile metrics (velocity, remaining backlog) in the stage report submitted to the board. The board decides what happens next without needing to understand the details of Agile ceremonies.
To gain a deeper understanding of how these approaches fit together, it helps to study the PRINCE2 method and its governance fundamentals before combining it with an iterative framework.

Tolerances and business cases: the two mechanisms that shape every decision
The business case is the reference document that justifies the project’s existence. It is not written once and then left unchanged: it is reassessed at every key decision point. If the expected benefits no longer justify the costs incurred, the project board can legitimately stop the project. This principle of continued justification is one of PRINCE2’s seven foundational principles.
Tolerances work as a measurable delegation system. For each stage, the project board sets acceptable limits across six areas: cost, time, scope, quality, risk, and benefits. As long as the project manager stays within these limits, they can act autonomously. If a tolerance is at risk of being exceeded, they trigger an exception escalation to the board.
This mechanism reduces unnecessary meetings. The board only gets involved when a decision falls outside the project manager’s authority, rather than approving every interim deliverable.
Example of applying tolerances
On an information system redesign project, the board allows a two-week time tolerance for each stage. If technical integration falls three weeks behind schedule, the project manager does not try to make up the time alone: they produce an exception report, propose a corrective plan, and wait for the board’s decision. This short escalation path prevents silent slippage that can prove costly at the end of a project.
PRINCE2 roles: who decides, who delivers, who checks
Confusion over roles is the most common cause of dysfunction in a structured project. PRINCE2 divides responsibility into four distinct levels:
- The project board (project direction) brings together three functions: the executive, who is accountable for the business case; the senior user, who represents business needs; and the senior supplier, who ensures technical feasibility.
- The project manager handles the day-to-day running of the project within the agreed tolerances. They do not make strategic decisions: they escalate exceptions and implement what has been approved.
- The team manager (or team managers, depending on the size of the project) oversees the production of deliverables. In an Agile context, this role may coincide with that of the Scrum Master or technical lead.
- Project assurance, independent of the project manager, checks that the method is being applied correctly and that the interests of each stakeholder are respected.
One person can take on several roles in a small project, provided decision-making and oversight remain separate. Combining the executive and project manager roles, for example, removes the exception escalation mechanism and weakens governance.

PRINCE2 version 7: what changes in day-to-day practice
The September 2023 update is more than a cosmetic refresh. Three changes affect how project managers apply the method in their day-to-day work.
The first concerns the emphasis placed on people and working relationships. Previous versions focused on processes and documents. Version 7 more explicitly recognizes collaboration between project participants as a success factor, bringing the method closer to the realities of day-to-day project work.
The second concerns digital technology and data management. Project decisions increasingly rely on real-time dashboards, automated tracking tools, and shared repositories. Version 7 recognizes the growing role of data in project management, whereas earlier editions were more generic.
The third change introduces sustainability as a performance objective. Environmental considerations are no longer an optional add-on: they are among the criteria that can be included in the business case from the initiation stage. For an infrastructure or digital transformation project, this means that environmental impact becomes part of the project board’s decision-making scope.
Adapting the method without losing its substance
PRINCE2 is based on the principle of tailoring: the method adapts to the project, not the other way around. For a project lasting a few weeks with a small team, documentation can be limited to a one-page business case and a simplified risk register. For a multi-year program, each document deliverable is developed in full.
The line between legitimate tailoring and bypassing the method lies in its seven principles. Removing the business case, combining decision-making with execution, or ignoring lessons from previous projects means you are no longer using PRINCE2, even if the documents still bear the right title.
The simplest test for checking that the method is still being applied is this: at the end of each stage, does the project board have enough information to decide whether to continue, make changes, or stop the project? If the answer is yes, governance is working, whatever delivery framework is being used alongside it.



