PRINCE2 Practitioner: PRINCE2 Principles

Try 10 focused PRINCE2 Practitioner 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 Practitioner
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 Practitioner. 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

A project to replace an organization’s customer portal is in its first delivery stage. The Project Manager reports the following symptoms:

  • Project Board decisions are repeatedly delayed because the same questions and concerns are raised at each meeting.
  • The development team is doing significant rework; several defects are identical to issues seen on the last portal project.
  • Progress reporting is inconsistent across teams, so trends are not being spotted early.
  • Scope changes keep being proposed to “fix” problems that were already encountered before.

The organization has a lessons repository from previous projects, but the PID contains no reference to it and no Lessons Log has been created for this project.

In PRINCE2 terms, what is the MOST likely underlying cause of these symptoms?

  • A. Product descriptions and acceptance criteria are insufficiently defined
  • B. The project has unclear accountabilities for decision-making
  • C. Management controls and reporting frequency have not been tailored
  • D. The project is not applying the learn from experience principle

Best answer: D

What this tests: PRINCE2 Principles

Explanation: The key clue is that previous lessons exist but are not referenced, and the project has not set up a Lessons Log. That indicates the PRINCE2 principle of learning from experience is not being applied, so the team repeats known mistakes and fails to improve decision-making and reporting as the project progresses.

PRINCE2 expects teams to learn from experience by seeking relevant lessons at the start, capturing new lessons throughout, and applying them to improve how the project is managed and delivered. Here, identical defects from the previous portal project are recurring and scope changes are being used to re-solve old problems, while the PID omits how lessons will be used and no Lessons Log exists.

A practical application is:

  • Review prior lessons during starting up and initiation to shape plans, controls, and product definitions.
  • Maintain a Lessons Log during the stage, recording what happened, impact, and recommended actions.
  • Feed lessons into current work (e.g., update Product Descriptions, Work Packages, reporting approach) and into end stage/end project reports.

Late decisions and inconsistent reporting may be symptoms, but the root cause indicated by the clues is failing to capture and apply lessons.

Previous lessons are not being captured or used, so known problems recur and drive repeated rework and churn.


Question 2

Topic: PRINCE2 Principles

You are the Project Manager for a city e-permitting portal. You are at the end of initiation and must present the Project Plan and the next Stage Plan to the Project Board in 5 days. The Senior User says “a self-service portal” is needed, but acceptance is unclear; the regulator requires WCAG 2.2 accessibility and auditable transaction logs. The Senior Supplier warns delivery depends on integrating the city’s existing identity service. Stage time tolerance is ±1 week.

What is the BEST next action?

  • A. Ask the Team Manager to produce a detailed task list and estimates, then baseline the Stage Plan and seek approval
  • B. Create an activity-based schedule from the requirements and confirm acceptance criteria during stage execution to save time
  • C. Run a product-based planning workshop to define key products, draft Product Descriptions with quality criteria/acceptance methods, and map dependencies before finalizing the Stage Plan
  • D. Escalate to the Project Board for an exception decision because the identity-service dependency makes planning too uncertain

Best answer: C

What this tests: PRINCE2 Principles

Explanation: PRINCE2’s product focus means planning starts by defining the products to be delivered, their quality criteria, and how they will be accepted. Here, acceptance constraints (regulator needs) and a key dependency (identity integration) are unclear, so the best next step is to use product-based planning to make these explicit before baselining the next Stage Plan.

Product-based planning is used to build plans from outputs, not from activities. In this scenario the product acceptance expectations (WCAG 2.2 and audit logs) and a major technical dependency (identity service integration) must be made explicit to avoid baselining a Stage Plan on assumptions.

A practical next step is to convene the right stakeholders (especially Senior User and Senior Supplier) to:

  • Identify the required products (product breakdown)
  • Define each key product’s quality criteria and acceptance method (Product Descriptions)
  • Sequence products to expose dependencies (product flow)

Only then should the Stage Plan be completed and submitted for approval within governance and tolerance expectations.

Product-based planning clarifies required products, their quality criteria, and their dependencies so the Stage Plan is built on agreed outputs and acceptance.


Question 3

Topic: PRINCE2 Principles

A Project Manager is initiating a project to implement a new customer self-service portal. The Executive asks for an early view of what products will be delivered, their key quality expectations, and the main dependencies between them, before committing to detailed estimating and scheduling.

The Project Product Description has been agreed, but there is no shared understanding yet of the major products that make it up.

What is the most appropriate next step in PRINCE2 terms?

  • A. Apply product-based planning: create a Product Breakdown Structure and outline Product Descriptions with quality criteria
  • B. Create Work Packages for each specialist team to start delivery
  • C. Produce the Stage Plan first to confirm dates and resources
  • D. Update the Business Case to justify scope and benefits in more detail

Best answer: A

What this tests: PRINCE2 Principles

Explanation: The project needs a product-focused definition of scope before it can be planned credibly. Product-based planning starts by identifying and structuring the products and capturing key quality criteria in Product Descriptions, which then enables mapping dependencies and building realistic plans. This directly supports the PRINCE2 principle of focus on products.

Product-based planning is used to clarify what will be delivered and the quality expectations, then to understand how products relate, before building time and cost estimates. With only the Project Product Description agreed, the next step is to define and analyze the products that make up the project’s outputs.

Practically, the Project Manager should:

  • Create a Product Breakdown Structure to identify and structure major products
  • Draft high-level Product Descriptions for key products, including quality criteria and quality methods
  • Use this as the basis to identify dependencies (typically via a Product Flow Diagram) and then develop the plan

Trying to schedule or authorize delivery work before this product definition increases the risk of rework and uncontrolled scope.

Defining and analyzing products (including quality criteria) provides the high-level product set needed to understand dependencies before detailed estimates and scheduling.


Question 4

Topic: PRINCE2 Principles

A project to implement a new customer self-service portal is halfway through stage 2. The Team Manager reports that integration testing revealed many defects caused by unclear interface specifications.

A similar project in the same organization finished last year and produced a lessons report recommending tighter definition and review of interface Product Descriptions early in each stage.

The Project Manager wants to apply the PRINCE2 principle of learning from experience immediately, without waiting for the end of the stage. What is the most appropriate next step?

  • A. Capture the lesson as an issue and update the Lessons Log, then brief teams and adjust stage controls accordingly
  • B. Raise an Exception Report and request the Project Board to mandate new interface standards
  • C. Wait until stage end and include the lesson only in the End Stage Report
  • D. Update the Business Case to reflect the cost of rework and record the lesson there

Best answer: A

What this tests: PRINCE2 Principles

Explanation: Learning from experience is applied throughout the project, not just at the end of stages. The Project Manager should record the lesson as soon as it is identified and ensure it is communicated and used to improve how products are specified and reviewed in the remainder of the stage and future stages. The Lessons Log is the management product used to capture and track lessons during the project.

The PRINCE2 principle ‘learn from experience’ means seeking, recording, and acting on lessons continuously. In this scenario, a known lesson (tighten interface Product Descriptions early) is directly relevant to the defects being found, so the Project Manager should capture the current learning immediately and ensure it is applied to prevent recurrence.

A practical next step is to:

  • Record the lesson in the Lessons Log (often triggered by an issue/defect pattern).
  • Communicate the lesson to the Team Manager(s) and relevant stakeholders.
  • Adjust how upcoming work is defined and controlled (for example, strengthen Product Description quality criteria, reviews, or acceptance methods in the current Stage Plan/Work Packages).

Waiting for end-of-stage delays benefit, and escalating as an exception is only justified if tolerances are forecast to be exceeded. The key takeaway is to log and apply lessons as soon as they are identified.

PRINCE2 expects lessons to be captured as they occur in the Lessons Log and applied during the project by adapting how work is defined and controlled.


Question 5

Topic: PRINCE2 Principles

You are asked to apply PRINCE2 on a 4‑week, low-risk internal project to automate a small reporting task for one department. The project has one supplier team and one business area, and the same person will fund and use the output. Corporate governance still requires clear decision-making and evidence of value for money.

Which approach best demonstrates the PRINCE2 principle of tailoring to suit the project, and correctly identifies what can be tailored?

  • A. Omit the Business Case because the work is small and the benefits are obvious to the department
  • B. Keep PRINCE2 principles, but scale controls/products and combine roles while retaining Project Board accountability
  • C. Avoid tolerances and exception management because they add unnecessary administration on short projects
  • D. Remove the Project Board and run the project solely under the Project Manager to reduce overhead

Best answer: B

What this tests: PRINCE2 Principles

Explanation: Tailoring means adapting how PRINCE2 is applied (e.g., roles, management products, and control frequency) to match the project’s scale, risk, and governance context. In this scenario, the method should be made lightweight, but it must still preserve direction/accountability and continued business justification required by governance.

The PRINCE2 tailoring principle is about applying the method in a way that is proportionate to the project’s context while still adhering to PRINCE2’s principles. For a short, low-risk internal project, it is appropriate to simplify documentation, reduce formality, and combine roles where one person legitimately covers multiple stakeholder interests.

What can be tailored includes the level of detail in management products, the frequency and formality of controls (reports, meetings), role assignments (combining roles while keeping accountabilities clear), and how the processes are applied (e.g., fewer stage boundaries if justified). What should not be tailored away are the principles themselves, such as having clear direction/accountability and maintaining continued business justification (often evidenced through a Business Case), especially when governance requires it.

Tailoring adjusts roles, controls, and management products to fit size/risk, but does not remove the need for accountable direction and continued justification.


Question 6

Topic: PRINCE2 Principles

A project is delivering a new CRM platform for a retail company. At the end of the stage, the Senior User asks for evidence that the key stage output “Pilot-ready CRM configuration” is properly defined so it can be objectively accepted. They want to see what the product includes, the measurable quality criteria it must meet, and the prerequisite products/information it depends on.

Which management product provides the best evidence for this validation?

  • A. Product Description for “Pilot-ready CRM configuration”
  • B. Product Breakdown Structure for the stage
  • C. Quality Register for the current stage
  • D. Stage Plan for the current stage

Best answer: A

What this tests: PRINCE2 Principles

Explanation: A Product Description is the PRINCE2 product-based planning artifact that makes acceptance objective by defining the product’s purpose/composition and measurable quality criteria. It also captures key dependencies through the derivation and any required input products/information. This is the most direct evidence for acceptance readiness of a specific product.

Product-based planning validates acceptance readiness by ensuring each product is defined in a way that allows objective verification. The management product designed for this is the Product Description: it documents what the product is (composition), how quality will be assessed (quality criteria and quality method), and what it depends on (derivation/inputs). In the scenario, the Senior User needs evidence that “Pilot-ready CRM configuration” can be accepted against clear criteria and that prerequisites are known, so the Product Description is the best validation artifact. Planning and reporting products may reference products and activities, but they do not provide the definitive, testable definition needed for acceptance.

A Product Description defines composition, quality criteria/methods, and derivation (inputs), enabling objective acceptance and showing dependencies.


Question 7

Topic: PRINCE2 Principles

A project is replacing a retailer’s customer portal. The Business Case depends on enabling online returns and payments before the peak season.

During the current stage, the Team Manager reports that the Product Description for the “Payments module” is vague and its acceptance criteria are mostly subjective (e.g., “easy to use”). The supplier suggests starting build immediately and “refining later” to protect the stage end date. Current stage tolerances allow up to 2 weeks schedule slip and $40,000 extra cost without escalation.

What should the Project Manager do NEXT to best protect business justification and value while balancing performance within tolerances?

  • A. Add detailed features requested by users to maximize future benefits
  • B. Clarify the Product Description and measurable acceptance criteria, then re-plan
  • C. Reduce testing to keep the date and accept higher defect risk
  • D. Authorize build now and treat acceptance as a final user sign-off

Best answer: B

What this tests: PRINCE2 Principles

Explanation: Focusing on products means defining the product’s purpose, composition, and quality expectations up front so delivery effort is spent on the right outcomes. Making acceptance criteria measurable enables objective acceptance and protects benefits realization. Using the available time/cost tolerances to clarify and re-plan maintains control while avoiding costly rework and disputes later.

The PRINCE2 principle of focus on products is about agreeing and controlling what products are needed and what “done” means, before significant delivery effort is committed. In this scenario, a vague Product Description and subjective acceptance criteria create a high risk of building the wrong thing, rework, and delayed or disputed acceptance—directly threatening the Business Case.

The Project Manager should use the permitted stage tolerances to:

  • Facilitate clarification with the Senior User and supplier
  • Update the Product Description with objective, testable acceptance criteria
  • Re-plan the remaining work/packages accordingly

This protects business value by ensuring delivery aligns to required outcomes and quality expectations while staying within agreed tolerances and keeping control of acceptance.

Product focus requires agreeing what will be built and how it will be accepted before committing effort, using tolerances to re-plan without losing value.


Question 8

Topic: PRINCE2 Principles

A Project Manager is halfway through Stage 2 of a customer-portal project. The Stage Plan sets a time tolerance of ±5 working days. A Checkpoint Report from the Team Manager shows a forecast slippage of 12 working days due to an unexpected integration defect. No change request has been raised yet.

Which plan should the Project Manager prepare next to support PRINCE2 manage-by-exception?

  • A. Exception Plan
  • B. Stage Plan (update the current one)
  • C. Stage Plan (for the next stage)
  • D. Project Plan (revise and rebaseline)

Best answer: A

What this tests: PRINCE2 Principles

Explanation: The forecast delay exceeds the stage time tolerance, so the situation must be escalated as an exception. In PRINCE2, the Project Board needs an Exception Plan to evaluate options and approve a replacement plan for the remainder of the stage (or a new stage) before work continues under revised tolerances.

This is a manage-by-exception decision driven by tolerance. When a Stage Plan forecast shows that the stage will exceed its agreed tolerance (here, 12 days slippage vs ±5 days), the Project Manager must escalate to the Project Board and provide a plan-based response for decision-making.

An Exception Plan is produced to replace the current Stage Plan (or, if needed, replace the remaining project-level plan elements) and to show the revised approach, costs, timescales, and risks for completing the work. A Stage Plan is used for day-to-day control within tolerance (current stage) or for planning the next stage at a stage boundary, while the Project Plan remains the overall baseline and is updated after decisions, not used as the immediate exception-response plan.

Key takeaway: exceeding tolerance triggers an exception and requires an Exception Plan for approval.

Because the stage forecast is outside agreed tolerance, an Exception Plan is needed for the Project Board to decide how to proceed.


Question 9

Topic: PRINCE2 Principles

During stage delivery, a Team Manager reports a forecast 2-week delay on a critical product due to a supplier issue. The Project Manager must decide whether to manage it within the stage or escalate as an exception, and who to inform. However, the Stage Plan excerpt available does not show any agreed tolerances or delegated authority limits.

What should the Project Manager obtain/verify FIRST before deciding the escalation action and audience?

  • A. A detailed root-cause analysis from the supplier
  • B. An updated benefits forecast from the Senior User
  • C. Reconfirmed product acceptance criteria from the users
  • D. The agreed stage and project tolerances (and escalation route) for time

Best answer: D

What this tests: PRINCE2 Principles

Explanation: Escalation in PRINCE2 is driven by manage-by-exception: action depends on whether forecasts exceed agreed tolerances at the relevant level (work package, stage, or project). If the forecast is outside the Project Manager’s delegated tolerances, an exception is raised to the next level of management. Therefore the first clarification is the agreed tolerances and the defined escalation route.

In PRINCE2, “forecast outside tolerance” is only meaningful when you know (1) what tolerances have been agreed for the level you are controlling and (2) who holds authority when those limits are forecast to be exceeded. The Project Manager manages within delegated stage tolerances; when an exception is forecast (e.g., time/cost/quality/scope/benefits/risk outside tolerance), the Project Manager escalates to the Project Board using an Exception Report and follows the agreed escalation route.

Before deciding whether to absorb the 2-week delay within the stage or escalate, the Project Manager should:

  • Confirm the agreed stage (and relevant project) tolerances for time.
  • Confirm the escalation route/authority limits (who must be informed if exceeded).

Only then can the Project Manager judge whether this is a local corrective action or an exception needing Project Board attention.

Without confirmed tolerances and escalation routes, the Project Manager cannot determine whether this forecast is an exception requiring escalation to the Project Board.


Question 10

Topic: PRINCE2 Principles

A Project Manager is running a 10-week internal CRM configuration project. They copied the documentation and governance approach from a previous large programme: full PID pack, multiple boards/committees, and long Highlight Reports. In practice, decisions are made late because the right people are not available at meetings, teams redo work after belated clarifications, reporting is seen as “noise”, and scope changes are agreed informally and then implemented without consistent impact assessment.

In PRINCE2 terms, what is the MOST likely underlying cause?

  • A. Highlight Reports are not being distributed frequently enough
  • B. The team is underperforming and missing deadlines
  • C. Product descriptions are missing acceptance criteria
  • D. PRINCE2 was not tailored to the project context

Best answer: D

What this tests: PRINCE2 Principles

Explanation: The symptoms point to a PRINCE2 implementation that is “copied and pasted” rather than adapted. When governance, decision routes, controls, and management products are not tailored to the project’s scale and availability of decision-makers, reporting becomes ineffective, decisions lag, and uncontrolled scope and rework increase.

The principle “tailor to suit the project” means PRINCE2 should be adapted so it remains fit-for-purpose while still providing appropriate governance and control. Here, a 10-week project is being run with programme-level documentation and forums, creating delay and poor engagement, while informal scope agreements bypass consistent control.

Tailoring can include adjusting:

  • Roles and decision authority (e.g., how the Project Board engages, what is delegated)
  • Management products (content, level of detail, format, digital tooling)
  • Controls and their frequency (reports, checkpoints, stage boundaries, tolerances)
  • Process/application approach (how activities are performed to match delivery method)

The key takeaway is to adapt PRINCE2’s products and controls to match risk, scale, and governance realities, not to run “maximum” PRINCE2 by default.

Applying an over-heavy, misaligned governance and product set indicates failure to tailor PRINCE2 to suit the project.

Continue with full practice

Use the PRINCE2 Practitioner 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 Practitioner guide on PMExams.com, then return to PM Mastery for timed practice.

Revised on Thursday, May 14, 2026