The principles compared with other approaches

PRINCE2 is not the only body of guidance built on principles. The PMBOK Guide from the Project Management Institute, the Agile Manifesto, Scrum, ISO 21502 and many organizations' own methods all state principles or values. Comparing them is useful for two reasons. In practice, many organizations blend approaches, and project professionals often hold more than one credential. And seeing what PRINCE2's principles have in common with others, and where they differ, deepens understanding of why PRINCE2 phrases its principles as it does. This lesson keeps the comparisons brief and practical; PMP-110 covers the PMBOK Guide in depth.

PRINCE2 and the PMBOK Guide

The PMBOK Guide, eighth edition, released in late 2025, sets out six principles: adopt a holistic view, focus on value, embed quality, be an accountable leader, integrate sustainability and build an empowered culture. The seventh edition had twelve broader principles. The two sets of principles do different jobs. PRINCE2's principles are obligations that define whether a project is being run using the method; they are closely tied to specific practices and processes. The PMBOK principles describe behaviors and mindsets for good project management in any approach; they are not tied to a specific governance structure.

The mapping is worth a closer look: it is many-to-many and approximate. PMBOK's "integrate sustainability" has no single PRINCE2 principle counterpart, though PRINCE2 7 addresses sustainability through the sustainability performance target and its tolerances. PRINCE2's manage by stages and manage by exception have no exact PMBOK equivalents, because PMBOK does not prescribe a governance structure.

For practitioners who hold both PMP and PRINCE2 credentials, a common way to combine them is to use PRINCE2 for project governance, roles and decision points, and the PMBOK Guide's broad toolkit for planning techniques, estimating and stakeholder engagement. The two fit together because PRINCE2 deliberately does not cover specialist techniques in depth.

PRINCE2 and the Agile Manifesto

The Agile Manifesto of 2001 states four values: individuals and interactions over processes and tools; working software over comprehensive documentation; customer collaboration over contract negotiation; and responding to change over following a plan. It also lists twelve supporting principles. At first sight PRINCE2 seems to sit on the right-hand side of each value, with its processes, management products, contracts and plans. A closer look shows more agreement than conflict.

The real difference is about where control sits. Agile approaches push decisions to self-organizing teams and rely on short feedback loops. PRINCE2 provides a governance layer above delivery that decides whether to invest, sets limits and handles exceptions. The two are complementary when PRINCE2 governs and agile delivers, and they conflict only when one tries to do the other's job.

PRINCE2 and Scrum

Scrum is a delivery framework with roles (product owner, scrum master, developers), events (sprint, sprint planning, daily scrum, sprint review, retrospective) and artifacts (product backlog, sprint backlog, increment). It also states values: commitment, focus, openness, respect and courage. Scrum does not address whether a project should be funded or continue, how a multi-team project is governed, or how supplier contracts are managed. PRINCE2 does. In a combined approach, the product owner often works closely with, or acts on behalf of, the senior user, and a sprint review gives evidence for highlight reports and stage boundary decisions.

PRINCE2 and ISO 21502

ISO 21502:2020, Project, program and portfolio management: guidance on project management, is an international standard describing practices for project management. It does not define a method, but it describes governance, roles, practices and the project life cycle in terms that are broadly consistent with PRINCE2. Organizations that need to show alignment with an international standard often map their PRINCE2-based method to ISO 21502. Like PMBOK, ISO 21502 emphasizes tailoring and business justification but does not prescribe PRINCE2's specific tolerance levels or product-based planning.

Common ground across approaches

Across all of these approaches, a few ideas recur. Projects should deliver value and stop when they no longer can. Accountability must be clear. Quality must be defined and built in. Plans should be adapted as more is known. Learning should be continuous. Methods must be tailored to fit. PRINCE2's distinctive contribution is to turn these ideas into specific, checkable obligations, backed by defined roles, decision points, tolerances and management products. That is why PRINCE2 can say clearly whether a project is, or is not, being run using the method.

Choosing and combining

Organizations rarely choose one approach exclusively. A typical pattern in both Canada and the US is a corporate method based on PRINCE2 or PMBOK for governance, with agile delivery for software and product work and traditional planning for construction or infrastructure. The PRINCE2 principles can act as a common governance standard across those delivery styles, because they say what must be true rather than how the work is done.

People and behavior behind the principles

Every approach in this lesson recognizes that principles depend on behavior. A business case cannot be honestly reviewed if people fear delivering bad news. Exceptions will be hidden if escalation is punished. Lessons will not be recorded if mistakes lead to blame. PRINCE2 7's people element addresses this directly, with guidance on leadership, communication, culture and managing change. In practice, the most important behavior for applying the principles is honest, early communication about problems, combined with leaders who respond to bad news by solving problems rather than punishing messengers.

Common misconceptions when comparing approaches

A few misconceptions come up repeatedly when practitioners compare PRINCE2 with other approaches. The first is that PRINCE2 is only for large government IT projects. Its origins were in UK government IT, but the principles are written to apply to any project, and the method is used in construction, health care, finance, charities and small businesses around the world. The second is that PRINCE2 requires a long, fixed plan. In fact manage by stages exists precisely to avoid detailed long-range plans. The third is that PRINCE2 is document-heavy by design. The tailoring principle requires documents to be scaled to the project, and PRINCE2 7 explicitly emphasizes using management products as tools rather than as compliance artifacts.

There are misconceptions about agile too. Agile does not mean no planning, no documentation or no governance. Agile teams plan continuously, document what is useful and work within constraints set by their organizations. When a PRINCE2 board sets time and cost tolerances and lets an agile team manage scope within them, both approaches are being used as intended.

Credentials and careers

In the US, the PMP is the most widely referenced project management credential, and PRINCE2 is less common but valued by employers with international operations, UK or European links, or a focus on governance. Holding a PMP, CAPM or IPMA certificate can satisfy the prerequisite for PRINCE2 7 Practitioner, as PRIN-101 explained, so practitioners often add PRINCE2 to an existing PMI credential. Understanding how the principles map to other frameworks makes that transition easier.

Whichever credentials you hold, the most valuable skill is the one this course builds: looking at a real project and judging whether it is being managed well. Principles, from any framework, are the lens for that judgment.

Why PRINCE2 phrases principles as obligations

Comparing frameworks also shows why PRINCE2 chose to phrase its principles as obligations rather than aspirations. An aspiration such as "focus on value" is hard to audit: almost any project can claim to be doing it. An obligation such as "ensure continued business justification", backed by a business case that must be reviewed at each stage boundary, can be checked against evidence. This makes PRINCE2 particularly useful for organizations that need clear accountability and auditable decisions, such as public bodies and regulated firms. The trade-off is that PRINCE2 can feel more structured than approaches built on values alone, which is why the tailoring principle is so important.

In practice, the best project professionals use both kinds of principle. They apply PRINCE2's obligations to make governance clear and checkable, and they draw on broader principles, such as building an empowered culture or embedding quality, to shape how they lead teams day to day.