What principles are and why PRINCE2 has them

This is an independent course. PRINCE2 is a registered trade mark of the PeopleCert group. The scenarios, questions and examples in this course are original and are not taken from any PeopleCert exam. Amounts in the examples are in US dollars unless stated otherwise.

In PRIN-101 you met the seven PRINCE2 principles in a single overview lesson. This course studies them in depth. Each principle gets its own lesson, with scenarios, failure modes, worked numbers and the links between the principle and the practices and processes that put it into effect. By the end you should be able to look at any project, healthy or troubled, and say which principles are being honored, which are being neglected and what to do about it. That skill matters for the Practitioner exam, where many questions describe a situation on a scenario project and ask which principle applies, but it matters far more on real projects.

This first lesson asks a simpler question: what is a principle, and why does PRINCE2 build itself on seven of them rather than on a set of rules or a fixed procedure?

Where principles sit in PRINCE2

PRINCE2 7, published in 2023 and renamed PRINCE2 Project Management in early 2026, is organized around five integrated elements. The principles are the foundation. The people element recognizes that projects are delivered by people and that leadership, communication and culture shape every outcome. The practices, formerly called themes, are the aspects of project management that must be addressed continually: business case, organizing, plans, quality, risk, issues and progress. The processes describe the journey from starting up to closing a project. The project context element reminds us that every project sits inside an organization, a sector and a set of constraints, and that the method must be tailored to fit.

The relationship between the elements is not symmetrical. You can tailor the practices heavily: a small project may combine its risk and issue registers into one log, write a two-page business case and hold stage boundaries as short meetings. You can tailor the processes: a simple project may combine starting up and initiating into a single short activity. But the principles are not tailored away. A project that ignores a principle is, by the method's own definition, not a PRINCE2 project, however many PRINCE2 templates it fills in.

What makes something a principle

The PRINCE2 manual describes its principles as having three characteristics. They are universal, self-validating and empowering. Each word repays attention.

• Universal means that every principle applies to every project, whatever its size, sector, culture, geography or delivery approach. A two-month office move and a ten-year transit line both need a reason to exist, both benefit from lessons, both need clear roles and both need decision points.
• Self-validating means the principles have been proven in practice over many years and many projects. They are not theories invented for the method; they are distilled from what worked and what failed on real projects since the 1970s.
• Empowering means that the principles give people confidence and the ability to shape and manage the project. A team member who understands manage by exception knows what they may decide alone. A board member who understands continued business justification knows they are allowed, and expected, to stop a project that no longer makes sense.

Principles differ from rules. A rule says exactly what to do: produce a highlight report every two weeks using this template. A principle says what must be true: the right level of management must be informed and must stay in control without being swamped by detail. A rule can be followed mechanically while its purpose is defeated, for example by sending a highlight report that hides a growing problem. A principle cannot be satisfied without achieving its purpose.

The seven principles at a glance

Here are the seven principles in the order the manual presents them. Each has its own lesson later in this course.

A good way to remember the set is to notice what each principle protects against. Continued business justification protects against projects that should never have started or should have stopped. Learn from experience protects against repeating old mistakes. Defined roles protect against confusion over who decides. Manage by stages protects against planning too far ahead and losing control. Manage by exception protects against micromanagement on one side and loss of control on the other. Focus on products protects against activity without outcomes and against scope creep. Tailoring protects against bureaucracy and against a method that does not fit.

Why a method needs principles at all

Early project methods were often criticized for being heavy and procedural. Teams produced documents because the method listed them, not because the documents helped. When PRINCE2 was revised in 2009, the authors made the principles explicit for the first time. The aim was to make clear what was essential and what was adaptable. A project manager facing a small project with a tight budget no longer needed to choose between doing all of PRINCE2 or none of it. They could ask which practices and products to scale down, as long as the principles still held.

Principles also provide a common language. When a board member says "this is outside tolerance, so it is an exception", everyone who knows PRINCE2 understands what has happened, who must decide and what information is needed. When a reviewer says "this project is not focusing on products", the team knows to look at whether product descriptions exist and whether acceptance criteria are clear. Shared principles make conversations shorter and decisions faster.

Finally, principles are what make PRINCE2 compatible with other ways of working. An agile delivery team can work in sprints with daily stand-ups and still sit inside a project that applies all seven principles. A public-sector project can follow its government's own gating process and still apply them. Because principles describe outcomes rather than steps, they can be satisfied in many different ways.

Principles apply to everyone

It is a common misunderstanding that the principles are the project manager's job. They are obligations on everyone involved. The executive applies continued business justification when deciding whether to authorize each stage. The senior user applies focus on products when confirming that the specified products will deliver the expected benefits. Team managers apply manage by exception when they escalate a work package that is forecast to exceed its tolerance. Team members apply learn from experience when they raise a lesson. Project assurance checks that all of this is happening.

How the exam treats principles

At Foundation level, questions usually ask you to identify a principle from a description, recognize its purpose or spot an option that is not a principle. At Practitioner level, questions describe events on a scenario project and ask which principle is being applied, which is being neglected or what action best honors a principle. The skill being tested is not recall of the list but recognition of the principle in action. Throughout this course, quizzes use original scenario-style items to build that skill.

Distractors often sound plausible. "Manage by milestones", "focus on activities", "ensure stakeholder satisfaction", "plan in detail before starting" and "minimize documentation" are not PRINCE2 principles, though each is close to something real. Observe that each distractor either describes a technique rather than an obligation or distorts a real principle. Focus on products is about outputs, not activities. Manage by stages is about decision points, not milestones. Tailoring is about fitting the method to the project, not about minimizing documents for their own sake.

A first look at a principles health check

Throughout the course you will practice assessing projects against the principles. A simple scoring scheme makes the assessment repeatable. For each principle, score the evidence from 0 to 3: 0 means no evidence, 1 means the principle is named but not practiced, 2 means it is practiced inconsistently and 3 means it is practiced consistently with evidence. The total out of 21 gives a rough health indicator, but the individual scores matter more. A single 0 means the project is not, strictly, a PRINCE2 project.

Lesson 12 develops this health check into a full capstone. For now, notice that the score is only as good as the evidence. A reviewer who scores from what people say rather than from documents, decisions and behavior will overrate most projects.