Overview
This domain covers the seven PRINCE2 principles: ensure continued business justification, learn from experience, define roles, responsibilities and relationships, manage by stages, manage by exception, focus on products, and tailor to suit the project. For each, you need to know the obligation it creates and the method features that put it into effect, such as tolerances for manage by exception or product descriptions for focus on products.
The principles are universal, self-validating and empowering. They apply to every project whatever its size or context, and a project that does not apply all seven is not a PRINCE2 project. That is what separates them from the practices and processes, which are adapted to the project. This domain therefore sits between the key concepts, which define the project, and the practices, which are the detailed mechanisms each principle relies on.
How it's tested
Principle questions check recognition and understanding. A stem describes a feature of the method or a short behaviour and asks which principle it supports, or asks which statement about a principle is correct. Some list several statements and ask which are true. The reasoning is mostly matching a mechanism to the principle that requires it.
-
Which principle is supported?
A method feature, such as setting tolerances or writing product descriptions, is described and you name the principle it puts into effect.
-
True statement about a principle
Several statements about one principle are offered and only one reflects the manual, for example about the minimum number of management stages.
-
Principle or not?
A list mixes principles with practices or general good practice, and you pick the genuine principle or the item that is not one.
A stem says the project board sets cost and time limits within which the project manager can act without referring back. Which principle does this support? Setting tolerances is the mechanism for manage by exception, because it lets each level manage within limits and escalate only forecast breaches. Manage by stages is the tempting distractor, but stages define decision points, not delegated limits.
Syllabus topics 7
Official syllabus topics from the PeopleCert outline, in outline order.
2.1 Ensure continued business justificationA justifiable reason to start the project that stays valid throughout and is documented and approved.
- What it means
- There must be a justifiable reason to start the project, that justification must remain valid for the whole project, and it is documented and approved in the business case.
- What to understand
- The business case is reviewed at key points, especially stage boundaries, and if the justification disappears the project should be changed or stopped. Justification can change over time, for example if expected benefits shrink, as long as it remains valid.
- How it shows up
- A stem asks which principle is applied when the board reviews the business case before authorizing the next stage, or what should happen if the project is no longer justified.
- Common confusion
- Candidates think justification is only checked at the start; the principle is about continued justification across the whole project.
2.2 Learn from experienceSeeking, recording and acting on lessons at the start, during and at the end of the project.
- What it means
- Project teams seek lessons from previous work when starting, record and act on lessons throughout the project, and pass lessons on at the end so later projects benefit.
- What to understand
- Learning is everyone's responsibility, not only the project manager's. The lessons log holds lessons to apply on this project and lessons reports pass them to the wider organization.
- How it shows up
- Expect a question on when lessons should be sought, with options limited to only the end of the project.
- Common confusion
- Treating lessons as a closing activity only; the principle covers all three points: start, during and end.
2.3 Define roles, responsibilities, and relationshipsA clear organization structure covering business, user and supplier interests, and how people work together.
- What it means
- A PRINCE2 project has defined and agreed roles and responsibilities within an organization structure that engages the business, user and supplier stakeholder interests, and pays attention to the relationships between people.
- What to understand
- The three primary interests are the business (is it value for money?), the user (will it meet needs and deliver benefits?) and the supplier (can it be delivered?). The 7th edition adds relationships to stress that roles work through people.
- How it shows up
- A stem asks which interest a stakeholder represents, or which principle requires all three interests to be represented in decision-making.
- Common confusion
- Candidates name only business and user interests and forget the supplier, or think the principle only concerns job titles rather than relationships.
2.4 Manage by stagesPlanning, monitoring and controlling the project one management stage at a time.
- What it means
- The project is divided into management stages, with the project board reviewing progress and deciding whether to continue at the end of each one. Detailed planning is done for the next stage, with a higher-level plan for the whole project.
- What to understand
- A PRINCE2 project has at least two management stages: the initiation stage and one or more further delivery stages. Shorter stages give more control points; longer stages reduce management overhead. Stages are decision points, not technical phases.
- How it shows up
- Expect a question on the minimum number of management stages or on why a detailed plan is produced only for the next stage.
- Common confusion
- Candidates equate management stages with technical stages or think one stage is enough for a small project.
2.5 Manage by exceptionDelegating authority within agreed tolerances and escalating only forecast breaches.
- What it means
- Each level of management sets tolerances for the level below on the performance aspects, and the lower level manages within them, escalating only if tolerances are forecast to be exceeded.
- What to understand
- Tolerances can be set on time, cost, quality, scope, benefits, risk and sustainability. The principle gives an efficient use of senior management time, because the board is not involved in decisions that stay within tolerance.
- How it shows up
- A stem describes setting limits on cost and time, or reporting only when limits are threatened, and asks which principle is applied.
- Common confusion
- Candidates think 'exception' means the board only hears about problems; the board still receives regular highlight reports and makes stage decisions.
2.6 Focus on productsDefining and agreeing products and their quality requirements before doing the work.
- What it means
- The project concentrates on the definition and delivery of products, especially their quality requirements, so expectations are clear and agreed before work starts.
- What to understand
- Product descriptions set out purpose, composition, quality criteria and similar details, and product-based planning starts from the products rather than the activities. This reduces scope creep, disputes over acceptance and user dissatisfaction.
- How it shows up
- Expect a question asking which principle is supported by writing product descriptions before creating activity schedules.
- Common confusion
- Candidates assume a focus on products means ignoring the work; activities are still planned, but they are derived from the products.
2.7 Tailor to suit the projectAdapting the method to the project's context, scale, complexity, capability and risk.
- What it means
- PRINCE2 is tailored to suit the project's environment, size, complexity, importance, team capability and risk, so the level of control fits the project.
- What to understand
- Tailoring adapts the practices and processes, and roles may be combined, but all seven principles must still be applied. The tailoring decisions are documented in the project initiation documentation (PID).
- How it shows up
- A stem says a small project is combining roles or simplifying reports and asks whether that is acceptable, or what may not be tailored.
- Common confusion
- Thinking tailoring allows a principle to be dropped; the principles are the part that is never tailored away.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Universal, self-validating, empowering
The principles apply to every project, have been proven in practice over many years, and give practitioners confidence to shape the method.
- Remember
- All seven must be applied for a project to be a PRINCE2 project.
- Tested as
- Questions test the characteristics of a principle or whether a project missing one can still be called PRINCE2.
- Trap
- Treating a principle as optional on small or low-risk projects.
-
Business case review points
Continued justification is confirmed at key decision points, notably each stage boundary and when an exception occurs.
- Remember
- If the project is no longer justified, the board should change direction or close it prematurely.
- Tested as
- Linked to manage by stages and the board's stage decisions.
- Trap
- Assuming the business case is approved once at the start and then left alone.
-
Lessons log and lessons report
The lessons log holds lessons for this project; a lessons report passes lessons to others in the organization.
- Remember
- Lessons are sought when starting, recorded during and passed on at the end.
- Tested as
- Appears in principle questions and again in the progress practice.
- Trap
- Thinking lessons are only captured in the closing process.
-
Business, user and supplier interests
The three primary stakeholder interests that the project management team structure must represent.
- Remember
- On the board: the project executive for business, senior users for user, senior suppliers for supplier.
- Tested as
- A stem names a concern, such as whether the product can be built, and asks which interest it belongs to.
- Trap
- Placing 'will the product be used and deliver benefits?' under business instead of user.
-
Minimum of two management stages
An initiation stage plus at least one further management stage.
- Remember
- Even a short project has an initiation stage separate from delivery.
- Tested as
- Frequently tested as a single fact in a true-statement question.
- Trap
- Choosing 'one stage is enough for a small project'.
-
Management stage vs. technical stage
Management stages are sequential decision points for the board; technical stages group specialist work and may overlap.
- Remember
- Management stages do not overlap; technical work can span them.
- Tested as
- Used to test what 'stage' means in manage by stages.
- Trap
- Assuming each design or build phase must be its own management stage.
-
Tolerance
The permissible deviation above and below a plan's target before the need to escalate to the next level.
- Remember
- Tolerances can be set on the seven performance aspects.
- Tested as
- The core mechanism of manage by exception.
- Trap
- Confusing tolerance with contingency budget or with a fixed target.
-
Product description
Defines a product's purpose, composition, derivation, quality criteria and related details.
- Remember
- Written before the product is developed so expectations are agreed.
- Tested as
- The main mechanism of focus on products.
- Trap
- Thinking product descriptions are written after delivery to document what was built.
-
What can and cannot be tailored
Practices, processes, roles, products and terminology can be adapted to context; the principles cannot.
- Remember
- Tailoring decisions are recorded in the PID.
- Tested as
- A stem proposes a tailoring decision and asks if it is acceptable.
- Trap
- Approving a 'tailoring' that drops business justification or stage control.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Manage by stages vs. manage by exception
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Manage by stages | Plan, monitor and control the project one management stage at a time | Creates board decision points at stage boundaries | Treating it as a way to delegate authority |
| Manage by exception | Delegate authority within tolerances and escalate only forecast breaches | Sets limits within which each level acts without referral | Thinking it removes regular progress reporting |
Principles vs. practices
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Principles | Seven universal obligations and good practices that define a PRINCE2 project | Always all applied; not tailored away | Assuming a principle can be omitted on a small project |
| Practices | Seven aspects of project management addressed throughout the project | Tailored to the context and implemented through processes | Calling business case a principle rather than the practice behind continued business justification |
Business vs. user vs. supplier interests
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Business | Concern with value for money and the business case | Represented by the project executive | Assigning benefits use to the business rather than the user |
| User | Concern with using the products and achieving benefits | Represented by senior users | Confusing the user with the customer organization as a whole |
| Supplier | Concern with providing the skills and resources to build the products | Represented by senior suppliers, internal or external | Assuming the supplier must be an external company |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Tailoring away a principle
- What candidates pick
- A statement that a simple project may skip manage by stages or business justification.
- Why it looks right
- Tailoring is presented as flexible, and small projects seem not to need formal control.
- Why it's wrong
- All seven principles must be applied; tailoring adapts how practices and processes are used, not whether principles apply.
Clue to watch for An option that removes a principle rather than simplifying a product or role is wrong.
-
One stage is enough
- What candidates pick
- An option saying a short project can be managed as a single management stage.
- Why it looks right
- A single stage sounds proportionate for a small project.
- Why it's wrong
- The minimum is two management stages: initiation, then at least one further stage.
Clue to watch for The words 'minimum' or 'at least' in the stem point to the two-stage rule.
-
Stages versus tolerances
- What candidates pick
- Manage by stages as the principle supported by setting cost and time limits.
- Why it looks right
- Stage tolerances are set for each stage, so the word stage appears in the stem.
- Why it's wrong
- Setting tolerances is the mechanism of manage by exception; manage by stages is about decision points.
Clue to watch for Look for limits, deviations or escalation; those signal exception.
-
Lessons only at the end
- What candidates pick
- An option saying lessons are captured when the project closes.
- Why it looks right
- End project reviews and lessons reports are prominent in many organizations.
- Why it's wrong
- Learn from experience applies at the start, throughout and at the end of the project.
Clue to watch for If one option mentions seeking lessons at the start, it is usually the complete answer.
-
Justification only at the start
- What candidates pick
- A statement that the business case is approved once at project authorization.
- Why it looks right
- Many organizations only approve funding once.
- Why it's wrong
- The principle is continued justification: the business case is reviewed and must remain valid throughout.
Clue to watch for The word 'continued' in the principle name is the clue.
-
Focus on products means no activity planning
- What candidates pick
- An option saying PRINCE2 plans products instead of activities.
- Why it looks right
- Product-based planning is emphasised so strongly that activities seem excluded.
- Why it's wrong
- Activities are still planned; they are derived from the products and their quality requirements.
Clue to watch for An option that excludes activities entirely is too absolute.
Answer framework
Use this sequence to match a described behaviour or mechanism to the correct principle.
- Identify the mechanism in the stem, such as a business case review, a tolerance, a product description, a lessons log entry or a role description, and ignore the surrounding story.
- Map that mechanism to the principle it implements, using the seven-principle list in order.
- Check edition wording: roles, responsibilities and relationships, and tailor to suit the project.
- Reject options that make a principle optional, that apply only at one point in time, or that confuse stages with tolerances.
- Confirm the remaining answer is consistent with all seven principles applying to every project, and that it names the principle the mechanism exists to serve rather than one it merely touches.
Practice question
Want more like this? The PRINCE2 7 Foundation practice test has questions for every domain.
Checklist
0 of 12
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Study this domain second, after key concepts, and allow two to three hours. Start by writing the seven principles in order and, beside each, the method feature that puts it into effect: business case reviews, lessons log, organization structure, management stages, tolerances, product descriptions and tailoring recorded in the PID. That pairing is what most questions test.
The high-priority facts are the two-stage minimum, the three stakeholder interests and who represents them, and the rule that tailoring never removes a principle. The commonly underestimated area is manage by exception: candidates know the phrase but cannot say which seven aspects carry tolerances or how escalation works between levels. Spend extra time there, because the same knowledge is tested again in the progress practice.
Afterwards, take a short practice set of principle questions and review every miss by asking which mechanism you mismatched. Then move on to the people domain; when you later study the practices, note which principle each one supports, which turns this domain into a review rather than a separate memory task.
FAQ
How many principle questions should I expect?
The learning outcome is weighted at 8%, about five of the 60 questions. That is an estimate; per-outcome counts are not published.
Can a principle be tailored out on a small project?
No. Tailoring adapts practices, processes, roles and products, but all seven principles must be applied for the project to be run as PRINCE2.
What is the minimum number of management stages?
Two: the initiation stage and at least one further management stage for delivery.
Does manage by exception mean the board only hears about problems?
No. The board still receives regular highlight reports and makes stage decisions; it is spared from approving decisions that stay within tolerance.
How are principles different from practices?
Principles are obligations that must always apply. Practices are aspects of project management, such as risk or quality, that are addressed throughout the project and tailored to it.
What changed in the 7th edition for principles?
The seven principles remain, with the roles principle now worded as define roles, responsibilities, and relationships to stress the people side of the organization.
How does this domain relate to the processes?
The processes put the principles into action, for example managing a stage boundary supports manage by stages and continued business justification.
Other Project Management certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- PRINCE2 7 Practitioner Same subject: Domain 1: PRINCE2 Principles in Context (10%)
- PMI Risk Management Professional Study guide
- PMI Scheduling Professional Study guide
- Project Management Professional Study guide
- CompTIA Project+ Study guide
- Portfolio Management Professional Study guide
- Program Management Professional Study guide
- Certified Associate in Project Management Study guide
- Agile Project Management Study guide
- PMI Agile Certified Practitioner Study guide
- Project Management Professional (PMBOK 7) Study guide
- Disciplined Agile Scrum Master Study guide
Test your Domain 2 knowledge
Check that you can name all seven principles and match each one to the mechanism that applies it, such as tolerances or product descriptions.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the PRINCE2 7 Foundation AI tutor Get any concept explained your way