2.1 7 PRINCE2 Principles Overview

What the seven principles are

The seven PRINCE2 principles are the guiding obligations that define whether a project is genuinely being run with PRINCE2. They were carried forward, with minor wording updates, into the PRINCE2 7th edition published by PeopleCert and AXELOS in September 2023. The official PRINCE2 7 wording is:

Note two wording changes in PRINCE2 7: the first principle gained the verb "ensure" (formerly just "continued business justification"), and the third now includes "relationships" (formerly "defined roles and responsibilities"). Foundation items can hinge on this exact phrasing, so memorize the current form.

The three shared characteristics

AXELOS states that all seven principles share three characteristics. Examiners love these as recall items:

• Universal — they apply to every project regardless of type, size, industry, geography, or culture. There is no project too small or too large for the principles.
• Self-validating — they are proven in practice over many years and many thousands of projects; they have stood the test of time rather than being a passing fad.
• Empowering — they give practitioners confidence and ability to influence and shape how the project is managed, rather than constraining them with rigid prescription.

A handy memory hook: principles are U-S-E (Universal, Self-validating, Empowering) — they are what you use to know you are doing PRINCE2.

Principles vs. practices vs. processes

PRINCE2 7 has four other integrated elements alongside the principles:

• Practices: seven aspects of management addressed continually; the 6th edition called them themes.
• Processes: the structured set of activities (e.g., starting up, initiating, directing, controlling a stage) that move a project through its lifecycle.
• People: leadership, teams, communication, culture, and organizational change.
• Project context: the environment that shapes how the method is tailored and applied.

Together with principles, these are the five integrated elements. Practices and processes are tailored to suit the project; the principles are not.

Why this matters at Foundation

The PRINCE2 Foundation exam is a 60-question, closed-book, multiple-choice paper; the pass mark is 36 out of 60 (60%) and you have 60 minutes. Principles account for 8% of the official blueprint and are usually tested through recall and recognition: name a principle, match a definition, or identify which described behaviour demonstrates a given principle.

The critical distinction in this topic is the one above: principles are mandatory and universal, and cannot be tailored away. If a project chooses to skip even one principle, it is not a PRINCE2 project. By contrast, you absolutely do tailor the practices, processes, management products, roles, and terminology to fit the project. Watch for distractors that say a principle was "tailored out" — that is always wrong.

The rest of this chapter walks principle by principle: what each means, why it qualifies as a principle, how it is applied through PRINCE2 mechanisms (business case, lessons log, tolerances, stages, product descriptions), and the traps the exam sets around each one.

Where the principles sit in PRINCE2 7

PRINCE2 7 has five integrated elements: principles, people, practices, processes, and project context. The principles are the bedrock layer; the other elements depend on them.

• Principles — the seven mandatory obligations covered in this chapter. They answer "is this even PRINCE2?"
• People — leadership, culture, change management, and communication, recognizing that projects are delivered by people, not just processes.
• Practices — the seven aspects (business case, organizing, plans, quality, risk, issues, progress) applied continually throughout the project.
• Processes — the seven processes that step the project through its lifecycle.
• Project context — the environment in which the project operates and the conditions that influence how PRINCE2 is tailored and applied.

The principles are derived from lessons learned from successful and failed projects; that is precisely why they are self-validating. Each principle is also enabling: it gives the project team a reason and a method to make good decisions rather than a checklist to obey blindly.

A clean mental model for the exam

Think of a PRINCE2 project as a building. The principles are the foundations — invisible, non-negotiable, identical under every building. The practices are the systems (electrics, plumbing) you run through the structure. The processes are the construction sequence, while people do the work and project context shapes how the whole method is tailored. You can redesign the systems and resequence the build for each project, but you can never pour a building with no foundations. This image makes the recurring exam answer obvious: whenever a choice offers "remove/skip/ignore a principle," it is the equivalent of building with no foundation — always reject it.

With that frame set, the next sections take each principle in turn and show exactly which management product or control point delivers it in practice — the pairings the Foundation exam tests most often.