Try 10 focused PRINCE2 Agile Practitioner questions on PRINCE2 Agile Processes, with answers and explanations, then continue with PM Mastery.
| Field | Detail |
|---|---|
| Exam route | PRINCE2 Agile Practitioner |
| Topic area | PRINCE2 Agile Processes |
| Blueprint weight | 30% |
| Page purpose | Focused sample questions before returning to mixed practice |
Use this page to isolate PRINCE2 Agile Processes for PRINCE2 Agile 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: 30% 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: PRINCE2 Agile Processes and Their Application
A customer portal project has delivered its final agreed increment, and a few low-priority enhancements will continue after closure under product management. To tailor closure, the project manager proposes using only the team’s retrospective notes and team dashboard as closure evidence, asks the Product Owner to declare the project closed after deployment, and plans to inform the project board afterwards. Which governance boundary has been mishandled?
Best answer: D
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: This is weak tailoring because agile artifacts can inform project closure, but they do not move closure authority away from governance. The project manager should prepare project-level closure evidence, and the project board decides whether the project can close.
In an agile context, project closure can use lightweight evidence from retrospectives, release results, and dashboards, but that evidence still has to support a project-level closure decision. The project manager prepares the closure recommendation and project-level information, typically including an end project report, acceptance status, handover arrangements, lessons, and any follow-on actions for residual backlog items. The project board then authorizes closure.
Product Owner input is useful for confirming delivered value and continuity of backlog items after the project, but it does not transfer closure authority. Project assurance checks whether closure information and controls are adequate; it does not approve closure. The weak tailoring here is delegating a governance decision to a delivery-side role and treating team-level evidence as if it were sufficient on its own.
Even when agile evidence is used, formal project closure remains a project board decision, with the project manager only recommending it.
Topic: PRINCE2 Agile Processes and Their Application
During Managing product delivery, an agile team is working on an authorized work package for a customer-portal increment.
Project information:
Work package acceptance: 4 Must user stories completed to Definition of Done
Reporting: weekly checkpoint report to the project manager
Current status: 1 Must story entered the timebox without acceptance criteria and is now blocked
Proposal from the Product Owner: swap in a ready Could story from the product backlog and keep the same timebox end date; do not inform the project manager
Which evaluation is the most fit for purpose?
Best answer: C
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: The proposal is not fit for purpose because the authorized work package requires four Must stories, and replacing one with a Could changes the agreed delivery outcome. In Managing product delivery, the Product Owner can help order and clarify backlog items, but the project manager retains control over the work package.
In Managing product delivery, agile teams can self-manage how they deliver, but they do not silently change the outcome agreed in an authorized work package. Here, the blocked story lacks acceptance criteria, so it is a readiness and product-quality problem that should be clarified first. More importantly, the work package acceptance states that four Must stories are required to Definition of Done. Swapping in a Could story keeps activity moving, but it no longer matches the authorized delivery target.
A good response preserves agile flexibility while keeping PRINCE2 Agile control at the right level.
Because the work package requires four Must stories, silently substituting a Could story bypasses project manager control over the authorized delivery outcome.
Topic: PRINCE2 Agile Processes and Their Application
A PRINCE2 Agile project is delivering in two-week timeboxes within an approved stage. The Project Board wants the team to keep adapting priorities quickly, but it must retain authority over project-level decisions. Additional information: forecasts remain within stage tolerances and the business case is still valid. Which TWO governance actions should the Project Board take? Select TWO.
Correct answers: B, C
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: In Directing a project, the Project Board should enable agility through delegated authority and management by exception. That means setting clear stage tolerances for day-to-day decisions and intervening only when forecasts show a likely breach or loss of business justification.
The key governance principle here is to keep project-level authority with the Project Board while avoiding unnecessary interruption to agile delivery. In an agile context, the board should authorize the stage and define clear tolerances so the project manager and appropriate product roles can make routine priority and delivery decisions quickly. This supports responsive backlog management without forcing the board into timebox-level control.
The board then preserves its authority by requiring escalation only when a forecast shows that stage tolerances may be exceeded or the business case may no longer remain valid. That is management by exception. It allows teams to continue delivering at speed while ensuring that exception decisions and major governance decisions stay at the correct level.
The main mistake is either micromanaging every delivery adjustment or delegating exception authority away from the board.
This preserves Project Board authority at the stage level while delegating routine agile decisions within agreed limits.
This applies management by exception so agile delivery can continue unless project-level intervention is actually needed.
Topic: PRINCE2 Agile Processes and Their Application
During a stage, the project manager reviews checkpoint reports and team dashboards from two agile delivery teams. A Must-have integration story has failed testing, and the teams forecast the stage will finish 8 working days late even after swapping out all available Should-have and Could-have items in their work packages. Additional information: the stage time tolerance is -7 days? No, the stage time tolerance is -7 days is wrong. Additional information: the stage time tolerance is -7 days? This is inconsistent.
Best answer: A
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: The team evidence shows that stage time tolerance is forecast to be exceeded, so this is no longer routine progress monitoring. In Controlling a Stage, the project manager should escalate with an exception report to the project board.
In PRINCE2 Agile, team dashboards and checkpoint reports provide delivery evidence to the project manager during a stage. The key fact here is that the forecast is 8 working days late against a stage time tolerance of -7 days? This is wrong and inconsistent.
A forecast breach of stage tolerance must be escalated by the project manager through an exception report.
Topic: PRINCE2 Agile Processes and Their Application
A project manager is controlling a stage with three 2-week timeboxes. After the first timebox review, one Must-have user story was not accepted, but the Product Owner says two Should-have stories can be deferred with no significant loss of value. The stage time tolerance is one week, and the project board wants clear evidence that the stage remains under control without adding extra meetings. Which action should the project manager take?
Best answer: D
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: Stage control needs evidence that links agile delivery results to PRINCE2 tolerances. Using the timebox review outcome with the updated release map and team dashboard gives the project manager enough collaborative evidence to reforecast the stage and decide whether corrective action or escalation is needed.
In Controlling a Stage, the project manager needs timely evidence to compare actual progress and forecast performance against stage tolerances. In an agile context, the best evidence comes from collaborative delivery events and current artifacts, not from adding separate reporting overhead. The timebox review confirms what has been accepted, the release map shows the impact on planned delivery, and the team dashboard adds current progress and impediment information. Together, these support a revised stage forecast and a proportionate control decision.
Stand-up detail is too granular for the project board, and retrospective output is mainly for improvement rather than stage-status evidence.
This combines agile workshop output and current artifacts to assess the stage forecast properly against tolerance.
Topic: PRINCE2 Agile Processes and Their Application
During Initiating a Project for a new self-service portal, the project manager presents this summary:
Backlog: 5 epics listed; no priorities, no release map, and no user stories for stage 1
Quality: Definition of Ready and Definition of Done agreed; key product descriptions include acceptance criteria
Risk: Agilometer shows low collaboration with an external supplier; risk register records this concern but no owner or response
Governance: project management team structure names the Project Executive, Chief Product Owner, senior supplier, project manager, and project assurance, with escalation routes
Which TWO statements show that initiation is insufficient? Select TWO
Correct answers: C, D
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: Initiation needs enough evidence to support controlled agile delivery. Here, the backlog is too thin to plan stage 1, and a significant supplier risk is visible but not yet managed. The quality and governance clues show adequate evidence, not gaps.
In PRINCE2 Agile, initiating a project does not mean detailing the whole product backlog, but it does mean having enough backlog evidence to support the project approach and the first stage. A set of unprioritized epics with no release map and no stage 1 user stories gives too little basis for sequencing, forecasting, and agreeing near-term delivery.
The risk clue is also weak. The Agilometer has surfaced low collaboration with an external supplier, but the risk register has no owner and no response, so the uncertainty is known but not yet actively managed. By contrast, the quality evidence is sound because product descriptions can be used alongside a Definition of Ready and Definition of Done. Governance evidence is also present because role definitions and escalation routes should be clear during initiation, not delayed until delivery begins.
The key test is whether initiation provides enough evidence for controlled, agile delivery.
Without prioritization or stage-level breakdown, initiation lacks enough backlog evidence to support planning and control of the first stage.
A recorded risk without ownership or a response shows incomplete risk evidence during initiation.
Topic: PRINCE2 Agile Processes and Their Application
A project manager is tailoring Managing Product Delivery for one mature agile team working in three two-week timeboxes on a small internal service enhancement. The team wants to rely only on its digital board and a final stage demo, because weekly written reports feel wasteful. The project manager still needs enough evidence to accept completed delivery and give weekly governance updates. Which adaptation is most appropriate?
Best answer: B
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: The best adaptation is to keep lightweight agile visibility but add the minimum PRINCE2 Agile controls for Managing Product Delivery. One authorized work package, regular checkpoint reporting, and recorded Product Owner acceptance at reviews give the project manager enough evidence to monitor progress and accept completed delivery without over-governing a mature team.
In Managing Product Delivery, the project manager needs evidence that work has been authorized, progress is being reported at the right level, and completed delivery meets agreed acceptance criteria. For a mature single team, it is proportionate to use one work package covering the planned timeboxes rather than add heavy control for each user story. The digital board is still useful for day-to-day visibility, but it does not on its own provide explicit acceptance evidence or structured project-level reporting. Adding short checkpoint reports gives the project manager regular progress information, while Product Owner acceptance at each review against agreed criteria or Definition of Done provides traceable delivery evidence. That combination preserves agile working and still lets the project manager accept the completed work package with confidence.
This keeps agile visibility while adding the minimum control needed: authorized work, traceable acceptance evidence, and regular reporting to the project manager.
Topic: PRINCE2 Agile Processes and Their Application
A PRINCE2 Agile project is replacing a claims portal. Stage 2 used two agile teams and finished within stage tolerance. The next stage will include customer migration and an external identity-service supplier, so risk exposure is higher. At the stage boundary, the project manager wants the project board to authorize the next stage using only team dashboards, a release burn chart, and the updated product backlog, arguing that anything more would be unagile. Select TWO statements that are correct.
Correct answers: A, D
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: At a stage boundary, agile delivery data can inform the decision, but the project board still needs controlled project-level evidence to authorize the next stage. In this scenario, dashboards and backlog detail alone are not enough, while a concise end stage report and next stage plan provide proportionate control.
Managing a stage boundary is about giving the project board enough reliable evidence to decide whether to continue, adjust, or stop before the next stage starts. In an agile context, team dashboards, burn charts, and backlog information are useful inputs, but they do not by themselves provide full project-level control.
Here, the next stage has higher risk because it includes migration and an external supplier. That makes a purely delivery-focused evidence set unfit for purpose. A lightweight but formal end stage report and next stage plan are proportionate because they can draw on agile information while still covering stage performance, forecast for the next stage, unresolved risks and issues, and continued value or business justification.
Agile information should support the stage-boundary decision, not replace it.
Stage-boundary authorization needs project-level evidence, not only team progress information.
These controlled products give the project board proportionate evidence for the next-stage decision.
Topic: PRINCE2 Agile Processes and Their Application
The project manager wants to recommend closure of an agile billing project after the final release. The project board asked whether the end project report contains complete closure evidence.
Exhibit: End project report excerpt
Acceptance: Final release accepted against project acceptance criteria.
Benefits: Benefit owners, measures, and review dates confirmed
for months 3 and 9 after closure.
Lessons: Lessons report completed and sent to project support.
Transition: Service desk training and support runbook update
are scheduled for next week, after project closure.
Which judgment is the best one?
Best answer: D
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: The missing evidence is in transition to operations. PRINCE2 Agile can close a project before all benefits are realized, but it should not recommend closure while live support arrangements are still outstanding.
In Closing a project, the project manager needs evidence that the product has been accepted, lessons have been captured, post-project benefits review is arranged, and transition to operations is ready. The exhibit already shows acceptance against agreed criteria, a completed lessons report, and confirmed benefit owners, measures, and review dates. The weak point is the transition note: service desk training and the support runbook update are still scheduled for after closure. That means operational readiness has not yet been completed or evidenced.
The key takeaway is that finishing agile delivery work is not the same as completing project closure; operational handover must also be ready.
Transition evidence is incomplete because key support activities are planned for after closure, so operations are not yet ready.
Topic: PRINCE2 Agile Processes and Their Application
An agile project has reached the end of a management stage. The project manager has current project and team dashboards and the latest release review results available. The project executive asks which single evidence package is most fit for purpose for the project board to decide whether to authorize the next stage. Which option provides the most direct support for that decision?
Best answer: C
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: For a stage boundary decision, the project board needs project-level evidence that summarizes the completed stage and shows whether proceeding is still justified. The end stage report, supported by the updated business case and next stage plan, is the most direct fit for that authorization decision.
In PRINCE2 Agile, managing a stage boundary is about giving the project board a sound basis to authorize the next stage, not just showing that agile delivery activity is healthy. The most fit-for-purpose evidence package is the end stage report together with the updated business case and next stage plan. These provide a formal view of stage performance, status against tolerances, outstanding risks and issues, continued business justification, and what is proposed for the next stage. A project dashboard is useful for ongoing governance, but it is not the primary stage-boundary basis for authorization. Release review results and team metrics are valuable inputs from agile delivery, yet they remain partial views. Stage approval needs formal project-level evidence, not only product feedback or team performance data.
This gives the project board formal stage performance evidence and the basis to authorize the next stage.
Use the PRINCE2 Agile 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 Agile Practitioner guide on PMExams.com, then return to PM Mastery for timed practice.