PRINCE2 7, published in September 2023, renamed the former “themes” as practices and added sustainability to the project performance targets, alongside cost, time, quality, scope, risk and benefits.
An article that still refers to “themes” describes an outdated version of the method. Managing a project with PRINCE2 today means mastering this new terminology, but also understanding how its governance mechanisms work alongside lighter ways of working.
PRINCE2 governance and agile teams: avoiding administrative overhead
Management by exception remains the most underused way to reconcile PRINCE2 with agility. The principle is simple: the project board sets tolerances (budget, time and scope), and the project manager has the freedom to manage as long as the project stays within those limits. Escalation is triggered only when a tolerance is about to be exceeded.
In an agile context, this means a team can work in sprints without seeking formal approval for every iteration. Tolerances replace systematic checkpoints. The project board retains visibility through end-stage reports, but does not get involved in day-to-day operations.
A common pitfall is piling PRINCE2 governance documents (business case, risk register, quality register) on top of an agile backlog that is already managed with dedicated tools. Version 7 partly addresses this issue by emphasizing tailoring to the project environment. In practice, a software development project running two-week sprints does not need the same level of formality as a public infrastructure program.
We recommend combining the PRINCE2 risk register with the agile impediment backlog in a single tool, and limiting the business case to one page, updated at the end of each stage. This is enough to meet the principle of continued business justification without creating parallel documentation. Exploring the PRINCE2 method can help you identify which documents are genuinely mandatory and which are simply customary in your organization.

PRINCE2 7 practices: how the new framework changes project management
The terminology overhaul is not just cosmetic. The seven PRINCE2 7 practices reshape how project managers organize their day-to-day work.
Sustainability as a performance target
Adding sustainability to the management criteria means addressing it in the business case, just like return on investment. A project that delivers a net benefit but worsens an environmental or social indicator can now be challenged during an end-stage review. Sustainability becomes a decision-making criterion, not an appendix.
Issues instead of Change
The former “Change” practice is now called “Issues.” This renaming broadens its scope: it is no longer just about managing change requests, but all the problems, questions and concerns raised by the team or stakeholders. The issue register brings everything together, reducing the number of documents that need to be maintained.
People and change adoption
PRINCE2 7 explicitly recognizes people as a central component of project management. The method provides an organizational change management approach that links project deliverables to their actual adoption and the expected benefits. A deliverable that is not adopted is no longer considered a success, even if it meets the schedule and budget.
Digital and data management
Version 7 adds a dedicated approach to managing digital tools and project data. Teams define how information is shared, stored and protected. For project managers, this means documenting tool choices (which tool for which purpose, and who has access) from the outset.
PRINCE2 stage process: adding structure without rigidity
PRINCE2 divides each project into management stages, each of which must be approved by the project board before the next one begins. This stage-control mechanism is often seen as rigid, but it is the framework’s main safeguard.
Every stage end is an explicit decision point: continue, adjust the tolerances or stop the project. This is what sets PRINCE2 apart from informal project management, where overruns accumulate without being addressed. The number of stages depends on the project: two may be enough for a short project, while a complex program may need four or five.
A common mistake is to define stages that are too short, multiplying formal reviews and slowing delivery. A sensible rule of thumb is that each stage should match a realistic planning horizon for the project manager. When uncertainty is high, shorter stages make sense. When the scope is stable, longer stages reduce the administrative burden.
- Initiation stage: prepare the business case, define the project approach, identify major risks and appoint the project management team.
- Delivery stages: execute work packages, monitor tolerances, update the issue register and report progress to the project board.
- Closing stage: assess the benefits achieved, document lessons learned and formally hand over the product to the operational team.
PRINCE2 certification: renewals and pathways to know
Two certification levels structure the pathway: Foundation (understanding the method) and Practitioner (the ability to apply it). The Practitioner exam allows candidates to consult the official manual during the test, making it more a test of applied reasoning than memorization.
Certifications must be renewed within three years, either through recertification or a continuing professional development pathway administered by PeopleCert. Missing this deadline means losing your certification without notice. It is wise to check the exact requirements directly with PeopleCert, as they may change.
- Foundation: multiple-choice exam, no prerequisites, validating knowledge of the framework.
- Practitioner: case study with scenario-based questions, manual allowed, minimum passing score required.
- Renewal: recertification or continuing professional development credits every three years through PeopleCert.

The update to PRINCE2 7 makes the framework more compatible with digital environments and teams accustomed to agile ways of working. Projects that fail with PRINCE2 generally do not suffer from too much methodology, but from controls that have not been sufficiently adapted to their real-world context.



