PRINCE2 Foundation: PRINCE2 Principles

Try 10 focused PRINCE2 Foundation questions on PRINCE2 Principles, with answers and explanations, then continue with PM Mastery.

On this page

Open the matching PM Mastery practice page for timed mocks, topic drills, progress tracking, explanations, and full practice.

Topic snapshot

FieldDetail
Exam routePRINCE2 Foundation
Topic areaPRINCE2 Principles
Blueprint weight8%
Page purposeFocused sample questions before returning to mixed practice

How to use this topic drill

Use this page to isolate PRINCE2 Principles for PRINCE2 Foundation. Work through the 10 questions first, then review the explanations and return to mixed practice in PM Mastery.

PassWhat to doWhat to record
First attemptAnswer without checking the explanation first.The fact, rule, calculation, or judgment point that controlled your answer.
ReviewRead the explanation even when you were correct.Why the best answer is stronger than the closest distractor.
RepairRepeat only missed or uncertain items after a short break.The pattern behind misses, not the answer letter.
TransferReturn to mixed practice once the topic feels stable.Whether the same skill holds up when the topic is no longer obvious.

Blueprint context: 8% of the practice outline. A focused topic score can overstate readiness if you recognize the pattern too quickly, so use it as repair work before timed mixed sets.

Sample questions

These questions are original PM Mastery practice items aligned to this topic area. They are designed for self-assessment and are not official exam questions.

Question 1

Topic: PRINCE2 Principles

During initiation of a digital service project, the project manager has created a high-level Product Breakdown Structure and drafted Product Descriptions for the main products, including quality criteria. The team now needs to understand which products must be created before others so that the Stage Plan can be built logically.

Which product-based planning output should be created next?

  • A. Product Flow Diagram
  • B. Stage Plan (activities and estimates)
  • C. Work Package
  • D. Risk Register

Best answer: A

What this tests: PRINCE2 Principles

Explanation: After identifying products and documenting their quality criteria, the next product-based planning step is to map the dependencies between products. The Product Flow Diagram provides this high-level view of product sequence so the work to create each product can be planned in the right order.

PRINCE2’s product-based planning supports the principle of focusing on products by planning from required outputs rather than starting with activities. Once the products are identified (Product Breakdown Structure) and defined (Product Descriptions, including quality criteria), you then need to understand how those products relate to each other.

The Product Flow Diagram is used to:

  • show the sequence in which products are created
  • identify dependencies (what must exist before a product can be produced)
  • provide the basis for deriving activities and building the Stage Plan

Planning activities or issuing work before understanding product dependencies risks an activity-led plan that is not driven by the required products.

A Product Flow Diagram shows the sequence and dependencies between products, which then informs the planning of activities.


Question 2

Topic: PRINCE2 Principles

A project to replace a finance system is being run using PRINCE2. The Project Board has approved the Project Plan at a summary level and set stage tolerances of .5 months and .2m.

At the end of the current management stage, a new reporting regulation is likely to affect solution design later in the project, but the impact is still uncertain. The current stage is forecast to finish within its tolerances.

What should the project manager do next to best balance business justification with time, cost, scope, quality, risk, and benefits while following PRINCE2 governance?

  • A. Produce an End Stage Report and a detailed Stage Plan for the next stage, update the Business Case and Project Plan as needed, and seek Project Board authorization to proceed
  • B. Continue into the next stage using the existing Project Plan, since the current stage is within tolerance and no escalation is required
  • C. Raise an Exception Report immediately so the Project Board can decide whether to stop the project due to the potential regulation change
  • D. Create a detailed plan for the remainder of the project now to reduce uncertainty before asking the Project Board for further funding

Best answer: A

What this tests: PRINCE2 Principles

Explanation: PRINCE2 manages by stages so the Project Board can make go/no-go decisions at defined points, based on continued business justification and updated information. The project manager plans in detail only for the next management stage, while keeping later stages at a higher level until their risks and requirements are clearer.

The principle of manage by stages means planning, monitoring, and control are organized around management stages, with the Project Board authorizing one stage at a time. This limits the Board’s exposure (time/cost/risk) by committing in increments, while still keeping an overall view through the Project Plan and Business Case.

Here, the current stage is forecast to stay within tolerance, so exception escalation is not justified. The correct governance action is to use the stage boundary to:

  • Report stage performance (End Stage Report)
  • Refresh forecasts and continued justification (updated Business Case/Project Plan)
  • Present a detailed Stage Plan for the next stage for authorization

The key takeaway is that stage boundaries provide controlled decision points without forcing premature detailed planning for uncertain later work.

This uses the stage boundary to review viability and risk, gain approval for the next commitment, and keep detailed planning focused on the next management stage.


Question 3

Topic: PRINCE2 Principles

A small internal project is being run using PRINCE2, but it has been tailored (combined roles, simplified controls, and fewer management products). The corporate PMO asks for evidence of how PRINCE2 has been tailored to suit the project and what will be used for governance and control.

Which management product should the project manager provide as the best evidence?

  • A. Checkpoint Report
  • B. End Stage Report
  • C. Highlight Report
  • D. Project Initiation Documentation (PID)

Best answer: D

What this tests: PRINCE2 Principles

Explanation: The PRINCE2 principle ‘tailor to suit the project’ requires the method to be adapted to the project’s context without losing control. The clearest evidence is the set of initiation documentation that defines what is being used and how governance, roles, controls, and management products have been adapted. This is documented and baselined in the PID.

‘Tailor to suit the project’ means PRINCE2 is not applied as a rigid template; it is adapted to the project’s scale, risk, complexity, and delivery approach while maintaining effective governance and control. The place to evidence these tailoring decisions is the Project Initiation Documentation (PID), which establishes the project’s baseline and includes the defined project controls and management approaches (e.g., how progress will be monitored and reported, roles/responsibilities, and which management products will be produced and at what level of detail). Highlight, Checkpoint, and End Stage reports primarily validate progress and performance during delivery, not the upfront tailoring decisions about how PRINCE2 will be applied.

The PID captures and communicates how the method is applied and tailored, including roles, controls, and management approaches/products for the project.


Question 4

Topic: PRINCE2 Principles

A project is halfway through delivery of a new customer portal. Market changes have reduced the expected benefits, but the Project Board still wants the team to “finish what we started”. The project has also repeated a defect pattern that was documented as a lesson in a previous stage.

Which action is NOT aligned with PRINCE2 principles of continued business justification and learning from experience?

  • A. Review earlier lessons at stage boundaries and brief them to the delivery teams
  • B. Update the Business Case and ask the Project Board to decide whether to continue
  • C. Record and act on the repeated defect as a new lesson for this stage
  • D. Keep the Business Case unchanged to avoid delaying delivery

Best answer: D

What this tests: PRINCE2 Principles

Explanation: PRINCE2 requires continued business justification, meaning the Business Case is actively maintained and used to decide whether the project should proceed. When circumstances change, the Business Case should be updated and the Project Board should make an informed decision on continuation. Learning from experience also requires lessons to be sought, recorded, and applied to prevent repeat problems.

The principle of continued business justification means the project must remain desirable, viable, and achievable, supported by a Business Case that is kept under review. When expected benefits change, the Business Case should be updated and used by the Project Board to decide whether to continue, change direction, or stop.

The learning from experience principle means lessons are identified, recorded, and acted upon throughout the project, not only at the end. If a known defect pattern repeats, the team should use prior lessons and capture what is newly learned so it is applied immediately and carried forward.

Avoiding updates to the Business Case to “save time” breaks governance by removing the basis for continued justification.

PRINCE2 requires the Business Case to be kept under review so continuation is based on current justification.


Question 5

Topic: PRINCE2 Principles

During initiation, the project manager starts creating the Stage Plan by listing activities and estimating effort. They decide to defer producing a Product Breakdown Structure and Product Descriptions (including quality criteria) until the delivery teams “work it out as they build.”

What is the most likely near-term impact on stage progress?

  • A. Stage tolerances will automatically be reduced by project assurance.
  • B. Benefits realization will fail at the post-project benefits review.
  • C. The Business Case must be rewritten before the stage can be authorized.
  • D. Work packages will have unclear acceptance criteria, causing rework and delays.

Best answer: D

What this tests: PRINCE2 Principles

Explanation: Product-based planning defines what must be delivered (products), the quality criteria for acceptance, and the dependencies between products before detailed scheduling. If these are deferred, teams start work without clear acceptance criteria and sequencing, so clarification and rework happen immediately. That typically shows up as short-term stage delays rather than an instant governance stop or a distant benefits problem.

Product-based planning supports the PRINCE2 principle of focusing on products by identifying and defining products before detailed activity planning. At a high level this is done by:

  • Creating a Product Breakdown Structure (what products are needed)
  • Writing Product Descriptions (including quality criteria and quality methods)
  • Mapping dependencies with a Product Flow Diagram (in what order products are created)

If these are deferred, the Stage Plan and work packages are built on assumptions. The near-term consequence is that teams cannot reliably agree acceptance criteria, responsibilities, and sequencing, so work gets redone or paused for clarification, slowing stage progress and increasing the chance of forecast breaches later.

Deferring product definitions and quality criteria makes work packages hard to agree and accept, leading to early rework and schedule slippage within the stage.


Question 6

Topic: PRINCE2 Principles

A project has had the same type of issue occur in each delivery work package during the current stage.

According to the PRINCE2 principle of learning from experience, how should this influence planning for the next stage?

  • A. Wait until project closure to document it in the Lessons Report
  • B. Treat it as operational business-as-usual because the issue is recurring
  • C. Escalate the recurring issue to the Project Board as an exception, even if tolerances are not forecast to be exceeded
  • D. Capture the lesson and adjust the next Stage Plan and controls to prevent recurrence

Best answer: D

What this tests: PRINCE2 Principles

Explanation: PRINCE2’s learning from experience principle expects the project to actively seek, record, and act on lessons throughout the project. A recurring issue is a clear trigger to change the approach before the next stage starts. Therefore, the next Stage Plan (and associated controls/working approach) should be updated to reduce the chance of the issue happening again.

The PRINCE2 principle “learn from experience” means lessons are identified, documented, and applied continuously, including when planning each new stage. If the same issue keeps occurring, the project should use that evidence to improve how the next stage will be managed and delivered (for example, changing techniques, tightening acceptance criteria, updating work instructions, strengthening quality checks, or adjusting controls and responsibilities). This is proactive learning: not just recording what happened, but changing the next stage’s approach to prevent repeat problems.

The key takeaway is that recurring issues should drive concrete updates to the next Stage Plan and how the work will be controlled, rather than being deferred or automatically escalated.

The learning principle requires using lessons to improve the approach for the next stage, not just recording them.


Question 7

Topic: PRINCE2 Principles

Halfway through a delivery project, a regulatory change reduces the expected benefits and increases operating costs for the product. The project manager decides to continue because “the project was approved in the PID” and does not update the Business Case or ask the project board to re-confirm viability.

Which PRINCE2 principle should be applied to correct this behavior?

  • A. Learn from experience
  • B. Manage by exception
  • C. Continued business justification
  • D. Manage by stages

Best answer: C

What this tests: PRINCE2 Principles

Explanation: This situation shows the project continuing on the basis of past approval rather than current viability. The corrective PRINCE2 behavior is to keep the Business Case under review and seek direction when changes affect whether the project is still worthwhile. That directly applies the continued business justification principle.

The principle of continued business justification means there must be a justifiable reason to start and continue the project, and that justification is recorded and maintained in the Business Case. When external changes affect expected benefits, costs, or risks, the project manager should ensure the Business Case is updated and bring the impact to the project board so it can decide whether to continue, change direction, or stop.

Continuing solely because the PID was approved treats justification as a one-time approval, which conflicts with PRINCE2’s requirement to re-check ongoing viability throughout the project lifecycle.

PRINCE2 requires the Business Case to remain valid and to escalate for a decision when viability changes.


Question 8

Topic: PRINCE2 Principles

A PMO advises a project manager to run a small, low-risk internal upgrade with a simple PID, informal reports, and one delivery stage. For a large, high-risk customer project, it advises detailed management products, more frequent controls, and multiple stages.

Which PRINCE2 principle is being applied?

  • A. Manage by exception
  • B. Manage by stages
  • C. Focus on products
  • D. Tailor to suit the project

Best answer: D

What this tests: PRINCE2 Principles

Explanation: The decisions described change the amount of documentation, formality, and control based on the project’s level of risk and complexity. This is exactly what the PRINCE2 principle of tailoring requires: apply PRINCE2 in a way that is appropriate for the specific project environment. The contrast between light-touch and more rigorous controls indicates tailoring rather than a specific planning or reporting technique.

The PRINCE2 principle “Tailor to suit the project” means PRINCE2 is not applied as a fixed, one-size-fits-all set of products and controls. Instead, the project manager and project board decide how much governance, documentation, and formality are needed based on factors such as risk, complexity, scale, and contractual needs.

In the stem, the small/low-risk project uses lighter controls (simple PID, informal reporting, fewer stages), while the large/high-risk project uses stronger governance (more detailed management products, tighter control cadence, more stages). That is tailoring the method to the project, rather than changing what PRINCE2 is trying to achieve.

Other principles may still be used, but they do not primarily explain the deliberate difference in rigor between the two projects.

PRINCE2 is being adapted so the method and controls are appropriate to the project’s size, risk, and context.


Question 9

Topic: PRINCE2 Principles

A project is delivering a new customer portal. The current management stage is ending this week and the next stage will commit most of the budget.

Performance is within agreed tolerances, but the project manager needs approval to start the next stage.

Which action best reflects the PRINCE2 principle of managing by stages?

  • A. Ask the team manager to approve the next stage because performance is within tolerance
  • B. Raise an Exception Report because the stage is ending and approval is required
  • C. Submit an End Stage Report and next Stage Plan to the project board for authorization to proceed
  • D. Send a Checkpoint Report to the project board to obtain approval to start the next stage

Best answer: C

What this tests: PRINCE2 Principles

Explanation: Managing by stages means planning, delegating, monitoring, and controlling the project one management stage at a time. At each stage boundary, the project board reviews the end-of-stage information and decides whether to authorize the next Stage Plan. This creates clear decision points and limits commitment of resources to one stage at a time.

The PRINCE2 principle of manage by stages organizes planning and control around management stages so the project board can make periodic decisions to continue, change direction, or stop. A stage boundary is a formal control point: the project manager reports how the stage went (including updated forecasts) and requests authorization to proceed with the next stage.

Typical stage-boundary control is:

  • Produce the End Stage Report (and updated plans/Business Case as needed)
  • Produce the next Stage Plan
  • Project board reviews and authorizes the next stage before significant commitment

This is different from escalation by exception, which is only needed when forecasts exceed tolerances.

Managing by stages uses stage boundaries as decision points where the project board authorizes the next Stage Plan before work starts.


Question 10

Topic: PRINCE2 Principles

Midway through a management stage, the project manager forecasts the stage will exceed its approved cost tolerance (forecast is +10% against an agreed tolerance of ±5%).

Which management product should be used to escalate this forecast to the appropriate level of management for a decision?

  • A. End Stage Report to the Project Board
  • B. Exception Report to the Project Board
  • C. Checkpoint Report to the Project Manager
  • D. Highlight Report to the Project Board

Best answer: B

What this tests: PRINCE2 Principles

Explanation: When a forecast shows a management stage will exceed its agreed tolerance, this becomes an exception situation. PRINCE2 requires escalation to the next level of management so that a decision can be made on how to proceed. The management product designed for this escalation from the project manager is an Exception Report to the Project Board.

PRINCE2 manages by exception using tolerances. If the project manager forecasts that stage (or project) tolerances will be exceeded, the project manager must not wait for routine reporting; they should escalate the situation to the Project Board for a decision.

The correct management product for this escalation is an Exception Report, which summarizes the exception situation, its impact, and options, enabling the Project Board to decide whether to request an Exception Plan, adjust tolerances, or take other action. Routine progress reports (like Highlight or Checkpoint Reports) are for normal control within tolerances, not for escalating an expected breach.

An Exception Report is used by the project manager to escalate a forecast breach of tolerance to the Project Board for direction.

Continue with full practice

Use the PRINCE2 Foundation Practice Test page for the full PM Mastery route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.

Open the matching PM Mastery practice page for timed mocks, topic drills, progress tracking, explanations, and full practice.

Free review resource

Read the PRINCE2 Foundation guide on PMExams.com, then return to PM Mastery for timed practice.

Revised on Thursday, May 14, 2026