Try 10 focused PRINCE2 Practitioner questions on Project and PRINCE2 Key Concepts, with answers and explanations, then continue with PM Mastery.
| Field | Detail |
|---|---|
| Exam route | PRINCE2 Practitioner |
| Topic area | Project and PRINCE2 Key Concepts |
| Blueprint weight | 3% |
| Page purpose | Focused sample questions before returning to mixed practice |
Use this page to isolate Project and PRINCE2 Key Concepts for PRINCE2 Practitioner. Work through the 10 questions first, then review the explanations and return to mixed practice in PM Mastery.
| Pass | What to do | What to record |
|---|---|---|
| First attempt | Answer without checking the explanation first. | The fact, rule, calculation, or judgment point that controlled your answer. |
| Review | Read the explanation even when you were correct. | Why the best answer is stronger than the closest distractor. |
| Repair | Repeat only missed or uncertain items after a short break. | The pattern behind misses, not the answer letter. |
| Transfer | Return to mixed practice once the topic feels stable. | Whether the same skill holds up when the topic is no longer obvious. |
Blueprint context: 3% 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.
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.
Topic: Project and PRINCE2 Key Concepts
A bank’s Operations department produces a mandatory regulatory report every Friday using a well-defined, repeatable spreadsheet process.
A new regulation now requires the bank to implement an automated reporting solution by December 1, after which Operations will run the report every Friday using the new system.
Which TWO statements are correct about what should happen? (Select TWO.)
Correct answers: A, F
What this tests: Project and PRINCE2 Key Concepts
Explanation: The new automated reporting solution is a one-off change with a clear deadline and a defined end state, so it fits the definition of a project. The existing weekly report production is repetitive and stable, so it remains business-as-usual, while the project plans a controlled handover so Operations can run the new service after closure.
In PRINCE2, a project is a temporary organization created to deliver one or more defined products and then disband; it typically introduces change and uncertainty. Ongoing operations (business-as-usual) are repetitive, stable activities that keep the organization running.
Here, delivering the automated reporting capability by a fixed date is a change initiative with a defined end point, so it should be managed as a PRINCE2 project (with appropriate governance and justification). Producing the regulatory report every Friday is a repeatable operational process, so it should stay under operational management; the project should plan and execute a handover so that Operations can take ownership and run the new process/service after the project closes. The key takeaway is to manage the change as a project, and the steady-state running as BAU.
Implementing the new solution is a temporary change initiative with a defined end point and a unique output, so it should be managed as a project.
The repeatable weekly activity remains BAU, while the project should plan transition so Operations can own and run the new service.
Topic: Project and PRINCE2 Key Concepts
A PRINCE2 project is delivering a new HR self-service portal. During the final stage, the Senior User asks the Project Manager to “keep improving the portal every month based on staff feedback,” with no defined end date.
Current stage tolerances are +/-1 week and +/-$15,000. The requested work would create an ongoing stream of enhancements and support activity.
What should the Project Manager do to best protect business justification and value while staying within tolerances?
Best answer: C
What this tests: Project and PRINCE2 Key Concepts
Explanation: Ongoing monthly improvement with no end date is business-as-usual work, not a project. The best option is to keep the project focused on delivering agreed products (and any clearly defined, justified change within tolerances) and then hand over ongoing support and incremental improvements to operations. This protects the Business Case and avoids creating an uncontrolled, never-ending project.
A PRINCE2 project is a temporary organization created to deliver one or more products and enable change, after which the work should be closed and handed over. An open-ended request to “keep improving every month” is ongoing operational activity and should be managed as business-as-usual (or as a series of separately justified projects/releases).
In this situation, the Project Manager should:
The key takeaway is to avoid turning a project into indefinite operations, which undermines control and business justification.
It keeps the project temporary and controlled while transferring ongoing operational work to business-as-usual with clear handover.
Topic: Project and PRINCE2 Key Concepts
Halfway through a management stage, the Team Manager reports that a key product has failed quality review and must be reworked to meet agreed acceptance criteria. Forecast impact: +2 weeks and +$8,000 (all amounts USD). The Stage Plan tolerances are time \(\pm 1\) week and cost \(\pm\$15,000\); scope is fixed for this stage. The planned go-live date is the trigger for the first expected benefits.
What is the BEST next action for the Project Manager to maintain appropriate control of performance?
Best answer: C
What this tests: Project and PRINCE2 Key Concepts
Explanation: The rework is required to meet quality acceptance criteria, but it causes a forecast breach of the stage time tolerance. Under manage-by-exception, the Project Manager must escalate forecast breaches to the Project Board rather than re-baselining or trading scope unilaterally. An Exception Report preserves control across time, cost, quality, scope, and the impact on benefits.
PRINCE2 controls performance by setting tolerances for the performance aspects (time, cost, scope, quality, risk, benefits) and managing by exception. Here, quality is protected because the product must meet agreed acceptance criteria, but the resulting forecast is +2 weeks, which exceeds the stage time tolerance of \(\pm 1\) week.
The Project Manager should therefore:
Replanning within tolerance is delegated to the Project Manager; breaching tolerance requires governance decision-making to maintain control.
The forecast breaches stage time tolerance, so manage-by-exception requires escalation with an Exception Report (and proposed response).
Topic: Project and PRINCE2 Key Concepts
A project is delivering a new customer-relationship system. Two weeks into Stage 2, the Team Manager has drafted a “Solution Architecture Document” and asks the Project Manager to add it to the PID so the Project Board can approve it.
Constraints:
What is the BEST next action?
Best answer: D
What this tests: Project and PRINCE2 Key Concepts
Explanation: PRINCE2 focuses on defining and accepting products because clear product descriptions and acceptance criteria reduce ambiguity and rework, which is critical with tight tolerances. The architecture document is a specialist product that should be planned, quality-controlled, and accepted through product-based planning and Work Packages. Management products (like the PID) remain focused on directing and controlling the project, not documenting the technical solution.
This situation is about keeping the distinction between management products (used to direct, manage, and control) and specialist products (the deliverables used/operated by the business or created by specialists). A “Solution Architecture Document” is a specialist product: it describes the technical solution and supports building the system.
With tight cost tolerance and specific compliance acceptance needs, the Project Manager should reinforce product-based planning by ensuring:
This preserves PRINCE2 control without unnecessarily routing specialist deliverables through Project Board approval mechanisms intended for management products or exceptions.
PRINCE2 controls delivery by defining and accepting products, treating the architecture as a specialist product managed via Product Descriptions and Work Packages rather than elevating it into a management product.
Topic: Project and PRINCE2 Key Concepts
You are the Project Manager for a data-migration project. A supplier Team Manager asks to start work immediately, but you notice the Work Package is incomplete.
Exhibit: Work Package excerpt
Work Package: WP-07
Target product: Data migration runbook (v1)
Acceptance criteria: TBC
Quality method: Not defined
Handover: End of stage
Which is the BEST next action, consistent with PRINCE2’s distinction between management products and specialist products and its focus on products?
Best answer: B
What this tests: Project and PRINCE2 Key Concepts
Explanation: The data migration runbook is a specialist product, but the exhibit shows missing acceptance and quality information in the management product used to control its creation. In PRINCE2, agreeing product definitions and acceptance criteria up front enables product-based planning and objective acceptance, reducing rework and misunderstandings.
PRINCE2 distinguishes specialist products (the project’s deliverables, such as the “data migration runbook”) from management products (the documents/records used to plan, monitor, and control work). The exhibit shows the Work Package lacks acceptance criteria and a defined quality method, so the team cannot reliably build and verify the specialist product.
The appropriate action is to define the runbook via a Product Description (including quality criteria, quality method, and responsibilities) and then update/reissue the Work Package so the Team Manager can execute and report progress against clear product requirements. This reflects PRINCE2’s focus on products: control is based on agreed outputs and acceptance, not on activities alone.
Logging an issue may still be useful, but the immediate need is to complete the product definition before authorizing work.
The runbook is a specialist product, so PRINCE2 uses management products (Product Description/Work Package) to define acceptance and quality before work starts.
Topic: Project and PRINCE2 Key Concepts
You are the Project Manager for a fixed-price project to deliver an internal analytics portal. Context constraints:
A first iteration is ready to start, but the supplier asks how approvals and reporting will work without waiting for the monthly Project Board meeting.
What is the BEST next action to apply PRINCE2 appropriately to this context while keeping effective control?
Best answer: D
What this tests: Project and PRINCE2 Key Concepts
Explanation: The context needs delegation and frequent, lightweight control because delivery is iterative and the Project Board meets infrequently. Using Work Packages with clear tolerances and acceptance criteria (including sustainability) enables rapid iteration while maintaining formal authorization and acceptance under a fixed-price arrangement. Manage-by-exception is preserved because anything forecast to breach stage tolerances is escalated.
Project context drives how PRINCE2 is tailored, not whether it is used. Here, agile delivery needs short-cycle direction and feedback, the fixed-price supplier relationship needs clear acceptance criteria and auditable handovers, and the Project Board’s monthly availability means day-to-day authorization must be delegated within agreed limits.
The Project Manager should tailor controls by:
This keeps governance at the right level (stage/exception) while enabling fast delivery and measurable sustainability acceptance.
This tailors PRINCE2 controls to agile cadence (Work Packages and checkpoints) while preserving stage tolerances and manage-by-exception for governance.
Topic: Project and PRINCE2 Key Concepts
A government agency is delivering a new citizen-facing digital service. Delivery will be iterative (agile teams), but an external supplier is contracted on a fixed-price basis for a key component. The agency has mandated monthly governance reporting to a Project Board and has a sustainability objective to reduce operational energy use.
Which tailoring decision is NOT aligned with applying PRINCE2 to this project context?
Best answer: D
What this tests: Project and PRINCE2 Key Concepts
Explanation: PRINCE2 can be tailored to fit agile delivery and commercial contracting, but it should not be tailored away from essential governance and controls. Even with iterative development, PRINCE2 expects clear accountabilities (including a Project Board) and stage-based decision points to manage by exception. The context drives how controls are implemented, not whether they exist.
Project context affects how PRINCE2 is applied: agile delivery encourages lighter, timeboxed team-level controls, while fixed-price supplier arrangements increase the need for clear interfaces, acceptance criteria, and tolerances in Work Packages. Organizational governance (monthly reporting to a Project Board) influences reporting cadence and escalation routes, and sustainability objectives should be embedded in product acceptance and quality criteria.
Tailoring should preserve PRINCE2’s essential direction and control mechanisms:
Agile ceremonies can complement PRINCE2 controls, but they do not replace governance and manage-by-exception structures.
PRINCE2 still requires defined direction and management by exception; agile delivery does not replace the Project Board or stage-based control.
Topic: Project and PRINCE2 Key Concepts
A government agency is starting a 6-week digital proof-of-concept with one external supplier. The PM is told “use PRINCE2”, but the team is worried it will add heavy documentation and prevent iterative delivery.
Which statement best explains what PRINCE2 is and how it should be applied on this project?
Best answer: B
What this tests: Project and PRINCE2 Key Concepts
Explanation: PRINCE2 is a structured method for directing and managing projects through defined roles, management products, and controls. Its value is that it can be tailored so a small proof-of-concept keeps proportionate governance and clear accountabilities without forcing unnecessary bureaucracy.
PRINCE2 is a structured, adaptable project management method: it defines how to organize and govern a project (who makes which decisions, what information is needed, and when to escalate) using practices and processes. In this proof-of-concept, “using PRINCE2” does not mean adding maximum documentation; it means tailoring the method so controls and products are proportionate while preserving core governance (e.g., defined Project Board accountabilities and management-by-exception with tolerances).
Tailoring typically involves scaling:
PRINCE2 can coexist with iterative/Agile delivery because it governs the project environment rather than dictating the specialist build techniques.
PRINCE2 provides a defined governance structure and decision-making controls, and it is explicitly designed to be tailored to the project context.
Topic: Project and PRINCE2 Key Concepts
A project is delivering a new CRM system. During Stage 2, the Project Manager receives:
Select TWO statements that are correct about what should happen next.
Correct answers: A, E
What this tests: Project and PRINCE2 Key Concepts
Explanation: PRINCE2 controls performance by agreeing tolerances for time and cost in the Stage Plan and using manage-by-exception. A forecast to exceed any tolerance (here, time) requires escalation to the Project Board via an Exception Report. Scope is controlled through change control: capture the request as an issue, assess its impacts, and route it to the defined change authority for a decision.
PRINCE2 manages the six performance aspects by setting targets and tolerances in plans and then controlling progress through regular monitoring and escalation only when needed. In this scenario, Stage Plan time tolerance is +2 weeks, but the forecast is +3 weeks, so the Project Manager must escalate because a tolerance is forecast to be breached.
Scope is controlled by change control: an out-of-scope request is recorded (as an issue/change request), analysed for impact on time, cost, risk, quality, benefits, and the Business Case, and then submitted to the agreed change authority (often the Project Board or a delegated Change Authority). The key point is that tolerances drive escalation, and scope changes require formal assessment and approval before being incorporated into baselines.
A forecast breach of an agreed tolerance triggers escalation by exception to the Project Board.
Scope is controlled through change control by recording the request and assessing impact on the performance targets and Business Case.
Topic: Project and PRINCE2 Key Concepts
A project to roll out a new customer portal is showing these symptoms:
The Project Manager says the project has “one overall plan” and the Project Board will do a major review near the end.
In PRINCE2 terms, what is the most likely underlying cause of these problems?
Best answer: C
What this tests: Project and PRINCE2 Key Concepts
Explanation: PRINCE2 uses management stages to create planned decision points where the Project Board can review performance, confirm continued business justification, and authorize the next stage. If the project runs as one long stage with only an end review, governance decisions are delayed and changes are more likely to be handled informally. Stage boundaries also align reporting and planning to meaningful control points.
Managing by stages provides the Project Board with regular governance points (stage boundaries) to decide whether and how to continue. At each stage boundary, the Project Manager reports what has been achieved (End Stage Report), updates the Business Case and other controls as needed, and presents a plan for the next stage (Next Stage Plan) for approval. This enables timely direction, controlled acceptance of change, and reporting aligned to agreed stage objectives. In the scenario, treating the project as “one overall plan” with a single major review removes those decision points, so approvals happen after work starts, reporting lacks a control rhythm, and scope changes drift in informally.
The key takeaway is that stage boundaries support governance by forcing planned review-and-authorize decisions before committing to further work.
Without management stages and stage boundaries, the Project Board lacks planned control points to approve the next stage and reset direction before more work proceeds.
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.
Read the PRINCE2 Practitioner guide on PMExams.com, then return to PM Mastery for timed practice.