Try 50 free PRINCE2 Agile Practitioner questions across the exam domains, with answers and explanations, then continue in PM Mastery.
This free full-length PRINCE2 Agile Practitioner practice exam includes 50 original PM Mastery questions across the exam domains.
The questions are original PM Mastery practice questions aligned to the exam outline. They are not official exam questions and are not copied from any exam sponsor.
Count note: this page uses a 50-question full-length practice format for PRINCE2 Agile Practitioner Version 2 review. Always confirm current book rules, language availability, and delivery rules directly with PeopleCert.
Set a 150-minute timer and treat the set as an applied PRINCE2 Agile scenario diagnostic. Track misses by scenario evidence, governance/agility balance, role decision, process tailoring, or product-delivery trade-off.
Use this page as a PRINCE2 Agile Practitioner scenario diagnostic, not as the only measure of readiness. The most useful result is the pattern behind your misses.
| Result pattern | What it usually means | Next step |
|---|---|---|
| Strong score and misses are scattered | Your applied tailoring judgment may be stable. Review explanations and protect timing. | |
| Many governance misses | Revisit tolerances, business justification, roles, controls, and escalation. | |
| Many agile-practice misses | Drill timeboxing, transparency, feedback, collaboration, and prioritization in context. | |
| Many scenario-tailoring misses | Practice choosing what to tailor, what to preserve, and what evidence supports the action. | |
| You rely too much on open-book lookup | Use the book to confirm, not to replace scenario judgment. |
| Field | Record |
|---|---|
| Overall score | ___ / 50 questions |
| Timing result | Finished early / on time / rushed late |
| Highest-miss area | governance / agile practices / tailoring / wider context |
| Most expensive mistake type | weak scenario evidence / too rigid / too loose / poor prioritization / other: ___ |
For concept review before or after this set, use the PRINCE2 Agile Practitioner guide on PMExams.com.
This static page is useful for one diagnostic pass. PM Mastery is better for repeated practice because it gives you varied timed attempts, focused practitioner drills, explanations, and progress history instead of one page you can memorize.
| Checkpoint | Approximate time budget | What to do |
|---|---|---|
| Questions 1-15 | 45 minutes | Read the scenario facts before choosing the method response. |
| Questions 16-35 | 105 minutes cumulative | Watch for governance-versus-agility trade-off traps. |
| Questions 36-50 | 150 minutes cumulative | Finish with enough time to review marked tailoring decisions. |
If you retake this free diagnostic, treat the second attempt as a reasoning check rather than a fresh score. Give more weight to varied timed attempts in PM Mastery than to repeating one static page.
| Item | Detail |
|---|---|
| Issuer | PeopleCert |
| Exam route | PRINCE2 Agile Practitioner |
| Official exam name | PRINCE2 Agile Practitioner (Version 2) |
| Full-length set on this page | 50 questions |
| Exam time | 150 minutes |
| Topic areas represented | 4 |
| Topic | Approximate official weight | Questions used |
|---|---|---|
| Agile Mindset, People, and Change Management | 20% | 10 |
| PRINCE2 Agile Practices, Roles, and Their Application | 44% | 22 |
| PRINCE2 Agile Processes and Their Application | 30% | 15 |
| PRINCE2 Agile in the Wider Context | 6% | 3 |
Topic: PRINCE2 Agile Processes and Their Application
An agile project has tailored Controlling a stage so teams can reorder user stories within each work package without project manager approval. Mid-stage, a team forecasts that a regulatory Must Have will miss the stage end date, so stage time tolerance will be exceeded unless the stage is extended. The Product Owner suggests managing this within the team and informing the project manager at the next stage boundary. Which boundary of responsibility is MOST aligned with PRINCE2 Agile?
Best answer: C
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: This tailoring is fit for purpose only if team autonomy stops at the work-package boundary. Once the forecast affects stage tolerance, PRINCE2 Agile control must apply through the project manager, with escalation to the project board if an exception is forecast. That preserves agility without weakening governance.
PRINCE2 Agile supports tailoring that gives agile teams freedom over day-to-day delivery decisions, such as reordering stories inside a work package. However, that flexibility does not remove project-level control. In this scenario, the problem is no longer just local backlog management because the forecast affects the agreed stage time tolerance. That moves the matter from team self-management into project control.
Waiting until the next stage boundary would be ineffective because it delays action on a governance-level forecast breach.
Work-package autonomy can remain agile, but a forecast stage-tolerance breach is a project-level exception owned through the project manager and project board.
Topic: PRINCE2 Agile Processes and Their Application
A project has delivered its final agreed release through two agile teams. The product will continue to evolve after the project, so the Product Owner will keep a product backlog for future enhancements. To tailor closing, the project manager proposes using outputs from the final sprint review and retrospective instead of a separate closing workshop, and asking the Product Owner to approve project closure. Which responsibility boundary is MOST appropriate?
Best answer: C
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: This tailoring is only effective if agile evidence is reused without removing PRINCE2 Agile closure control. The project manager can use sprint review and retrospective outputs, but must still create project-level closure evidence and seek Project Board authorization.
In an agile context, tailoring closing should remove duplication, not remove governance. Reusing the final sprint review and retrospective is sensible because they provide current evidence about delivered value, acceptance feedback, lessons, and remaining follow-on work. However, those team-level workshops do not replace the project manager’s responsibility to assemble project-level closure information, including the end project report, and to recommend closure.
The authority to close the project stays with the Project Board. Product-side roles may confirm product status and own the ongoing product backlog after the project, but that does not give them project closure authority. The key boundary is between agile delivery evidence, which can be reused, and project governance accountability, which must still be preserved.
Agile workshop outputs can inform closure, but project closure remains a project-level governance decision authorized by the Project Board.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
A project is using two agile delivery teams. During initiation, the project manager circulates the following draft role note, but the Project Executive says it does not clearly separate governance, delivery, and escalation.
Exhibit:
Draft role note
- Chief Product Owner: answers daily story questions from both teams
- Product Owners: escalate delivery blockers directly to the Project Board
- Team coaches: send progress updates to the Project Executive
- Project manager: manages stages and exception reports
Which revision would BEST clarify the project management team structure for this agile context?
Best answer: B
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: The best structure separates project-level governance from team-level delivery. In PRINCE2 Agile, the Chief Product Owner provides overall product direction across teams, Product Owners work at team level, and escalation normally goes through the project manager, with the Project Board involved if tolerances are threatened.
The Organization practice should make reporting lines, decision rights, and escalation paths explicit. In this scenario, the draft blurs project and team responsibilities by placing the Chief Product Owner in daily team detail, sending blockers straight to the Project Board, and bypassing the project manager for progress flow.
A clearer PRINCE2 Agile structure is:
This keeps agile delivery responsive while preserving governance. The closest distractors sound agile, but they weaken role clarity by giving delivery roles project-level authority or turning assurance into line management.
This preserves project-level governance, keeps delivery decisions close to each team, and uses the correct escalation path through the project manager.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
A city council project is replacing paper permit applications with a digital service using two agile teams and a cloud supplier. Reduced paper use and lower hosting energy are part of the approved value justification, and sustainability results must be reported externally at each stage boundary. During initiation, the project manager only added a few sustainability-related items to the product backlog; there is no sustainability management approach and no project-level owner or measure. Which TWO statements are correct? Select TWO.
Correct answers: B, C
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: The current approach is not sufficient because sustainability is part of the project’s approved value justification and must be reported at stage boundaries. PRINCE2 Agile therefore needs proportionate project-level control, while agile teams can still support delivery by embedding sustainability checks in relevant backlog items.
When sustainability contributes to why the project is justified, it belongs in the Business Case practice, not only in team delivery records. In this scenario, sustainability outcomes must be reported externally at each stage boundary, so the project needs clear ownership, measures, and governance evidence at project level. A sustainability management approach is a proportionate way to define how this will be managed and reported, with the business case reflecting its contribution to value.
Agile delivery can still support this by adding sustainability-related acceptance criteria or similar checks to relevant backlog items. That helps day-to-day delivery decisions, but it does not replace project-level control. The key distinction is between useful team-level delivery detail and the project-level evidence needed to support ongoing business justification and stage control.
Sustainability affects the approved value justification, so it needs explicit project-level control through the business case and a supporting sustainability management approach.
Team-level backlog criteria can support sustainable delivery, but stage-boundary reporting still needs project-level measures and ownership.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
A PRINCE2 Agile project is delivering a customer self-service portal through short timeboxes. Midway through the current stage, a new regulation makes one planned feature optional, cutting most of the forecast savings from the next release. The teams can still deliver on time, product quality is meeting the Definition of Done, and no tolerances are forecast to be exceeded. The project board asks the project manager for the best basis to decide whether the project should continue unchanged. Which practice is most relevant to use next?
Best answer: B
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: The main decision is about continued business justification, not delivery control. Because the regulation has reduced expected benefits, the business case practice is the right place to reassess whether the project still offers enough value to continue unchanged.
The decisive need here is continued business justification. The regulation change has reduced the benefits that supported the project, so the project manager should use the business case practice to reassess expected value and advise the project board on whether the project should continue unchanged.
In PRINCE2 Agile, the most relevant practice is the one whose purpose best matches the decision need. The teams are still delivering on time, meeting quality criteria, and staying within tolerance, so plans, quality, and progress are not the main concern. A change has occurred, but simply recording it as an issue does not answer the board’s real question: is the project still worth doing? The business case practice provides the basis for that decision, after which any replanning or issue actions can follow.
This practice is most relevant because the key decision is whether reduced benefits still justify continuing the project.
Topic: PRINCE2 Agile Processes and Their Application
A project manager is preparing to authorize a work package to an agile delivery team for the current stage. The team wants freedom to reorder tasks as it learns from user feedback, but the project board still expects clear product acceptance and reliable stage reporting. Which TWO actions best balance team autonomy with PRINCE2 Agile governance? Select TWO.
Correct answers: B, C
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: The best balance is to define what must be achieved and how progress will be reported, then let the team decide how to do the work. In Managing Product Delivery, PRINCE2 Agile keeps control through clear acceptance conditions and agreed reporting, not through day-to-day micromanagement.
In an agile context, Managing Product Delivery should protect team autonomy while preserving project control. The work package sets the boundaries for delivery, including what products are needed and how acceptance will be judged. Using acceptance criteria and a Definition of Done gives clear quality and acceptance expectations without telling the team how to organize its tasks.
Reporting should also stay proportionate. Checkpoint reports, supported by team dashboard information, give the project manager reliable visibility of progress, impediments, and forecast completion while leaving the team free to adapt its detailed work. Requiring approval for internal story reordering pushes project-level control into team-level decisions, and delaying acceptance until stage end removes early feedback and increases the risk of discovering problems too late.
The key is to control outcomes and visibility, not the team’s daily delivery choices.
This keeps acceptance explicit while allowing the team to self-manage how the work is completed.
This provides regular progress evidence to the project manager without daily direction of the team.
Topic: Agile Mindset, People, and Change Management
A PRINCE2 Agile project is in Stage 2 of a customer portal release. A supplier API delay means three planned Must-have stories cannot be completed in the current timebox. The Product Owner suggests moving them to the next stage.
Project note:
Stage 2 tolerances
- Time: 0 weeks
- Cost: +\$20,000
- Scope: minimum 17 Must-have stories
Current forecast
- Time: no change
- Cost: +\$8,000
- Scope: 15 Must-have stories
Delegated authority
- The Product Owner may reprioritize within the stage
if stage tolerances remain within limits
What should the project manager do now?
Best answer: B
What this tests: Agile Mindset, People, and Change Management
Explanation: Manage by exception allows agile reprioritization only within agreed tolerances. Here the forecast drops below the stage’s minimum Must-have scope, so the project manager must escalate rather than rely on delegated authority.
Manage by exception delegates routine decisions to the lowest appropriate level, but only while agreed tolerances are forecast to be met. In an agile project, the Product Owner can usually reprioritize backlog items and use MoSCoW to protect value, yet that flexibility still sits inside project and stage controls.
In the exhibit, time and cost remain within tolerance, but scope does not. The stage requires at least 17 Must-have stories and the new forecast is 15, so a stage-level tolerance is forecast to be exceeded. That makes this an exception, not a normal team-level trade-off. The project manager should therefore escalate to the Project Board with an exception report.
Agile flexibility applies within tolerance; a forecast breach triggers escalation.
The forecast breaches stage scope tolerance, so delegated authority no longer applies and the project manager must escalate by exception.
Topic: PRINCE2 Agile Processes and Their Application
A PRINCE2 Agile project is partway through Stage 2, using fixed two-week timeboxes and a fixed market launch date. A supplier delay means the planned release will miss the stage end date by 12 days unless several Should-have stories are moved to a later release. The project manager has already submitted an exception report and an exception plan, and the Chief Product Owner confirms the revised release map still supports the business case. What should the project board do next?
Best answer: B
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: The key fact is that stage tolerance is forecast to be exceeded, so the project manager has correctly escalated. In Directing a Project, the project board should authorize the exception plan when the revised approach still protects value and the business case.
This is a Directing a Project decision because the issue has moved beyond normal agile replanning. In PRINCE2 Agile, backlog reprioritization and moving lower-priority stories are valid ways to protect a fixed date, but only while the project remains within agreed tolerances. Here, the stage end date is forecast to be exceeded, so the project manager must escalate with an exception report and exception plan.
Because the revised release map still supports the business case, the board should authorize the exception plan and allow delivery to continue against the revised baseline. Waiting for the stage boundary delays a required governance decision, and asking delivery roles to absorb the problem without authorization would bypass exception control. The closest distractor is simple backlog reprioritization, but that is not enough once a tolerance breach is forecast.
A forecast breach of stage tolerance requires project board authorization of an exception plan, even when agile reprioritization preserves value.
Topic: PRINCE2 Agile Processes and Their Application
A project manager has tailored stage control for a PRINCE2 Agile stage by relying only on the supplier team’s product backlog. No work package descriptions are being issued because “the backlog already tells the team what to do.” Mid-stage, the supplier team completes several stories, but the Chief Product Owner says a key interface product was never explicitly authorized for this stage. The project board wants better control without adding heavy documentation. What is the best next step?
Best answer: A
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: The weak tailoring is the removal of the work package description, not the use of agile backlog items. In PRINCE2 Agile, backlog detail can support delivery, but the project manager still needs a clear, lightweight authorization mechanism for stage work, especially where interfaces and supplier work are involved.
In Controlling a Stage, the project manager must maintain clear authorization and control over what work is being done in the stage. A product backlog helps the team manage delivery detail, but it does not automatically replace the need for a work package description. In this scenario, the dispute about whether an interface product was authorized shows that scope, interfaces, and expectations were not clearly agreed at the right control level.
A good PRINCE2 Agile response is to use a light work package description that points to the relevant backlog items rather than creating separate heavy documentation. That preserves agile flow while reintroducing the missing control. The problem is not that agile artifacts are being used; it is that a project-level stage control was removed completely.
This restores a PRINCE2 Agile stage control that was removed, while keeping delivery lightweight by linking authorization and controls to existing backlog detail.
Topic: PRINCE2 Agile in the Wider Context
A PRINCE2 Agile project has launched a self-service claims portal. After project closure, a permanent product management team will continue fortnightly enhancements. The organization has moderate agile maturity and reliable live-service analytics, but current reporting mainly shows stories completed, defects fixed, and throughput. The project board wants a proportionate adaptation to closure evidence that shows whether project outcomes are supporting continuing product value and benefits. Which adaptation is MOST appropriate?
Best answer: B
What this tests: PRINCE2 Agile in the Wider Context
Explanation: The best adaptation is to use live product measures that continue after handover, not just team delivery activity. OKR trends and early benefit measures show whether the released portal is creating value and let product management continue tracking that value after the project closes.
In PRINCE2 Agile, agile product management beyond the project means closure evidence should connect what the project delivered to the value the product continues to create. A proportionate adaptation is to include live-service OKR trends and early benefit measures in project closure evidence, with ongoing ownership passed to product management. That keeps PRINCE2 control while recognizing that product value continues after the project ends.
Team throughput, story counts, and defect totals show delivery performance, not whether outcomes are improving customer or business results. Product backlog priority shows expected value, not realized or continuing value. Keeping the project open until all long-term benefits appear is not proportionate; continued value tracking can carry on after project closure.
This gives project-level evidence that released outputs are creating continuing product value and allows tracking to continue after closure.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
A project manager is preparing an end stage report for a pilot release. The project board wants evidence that the products planned for release are at the required quality status before authorizing the next stage.
Exhibit: Product register excerpt
| Product | Product status | Quality status |
|---|---|---|
| Online claim form | Completed | Approved |
| Assessor dashboard | Completed | Usability review action open |
| Pilot release package | Ready for release | Security approval pending |
How should the project manager use this information?
Best answer: A
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: The product register is the right source for a project-level view of each product’s current status and quality state. In the exhibit, one product has an open review action and another still lacks approval, so the release should not yet be treated as fully ready.
In PRINCE2 Agile, the product register supports the quality practice by showing what products exist and where each stands in its lifecycle. That makes it useful when the project manager needs control evidence for a release, stage boundary, or acceptance decision. Here, the register shows that completed work is not the same as acceptable status: the assessor dashboard still has an open usability action, and the release package still needs security approval. The right use is to highlight those gaps and support product status control until the outstanding quality items are closed or an explicit decision is made. The product register is for product readiness and status visibility, not for backlog prioritization, detailed defect logging, or productivity reporting.
The product register gives project-level visibility of product status and quality state, so it supports a readiness decision by highlighting open actions and pending approval.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
A project is using agile teams to deliver a customer self-service portal. The project manager needs a next stage plan for project board authorization, covering a 3-month stage and two planned releases. The Chief Product Owner says the product backlog is detailed only for the next two timeboxes; later items are high level and likely to change. What is the best next step?
Best answer: B
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: In the Plans practice, epic user stories are useful for longer-horizon stage and release planning when detail is still emerging. User stories should then be used for near-term work so the project has planning evidence without fixing uncertain scope too early.
Epic user stories and user stories support different planning horizons. Here, the project manager needs enough information for stage authorization, but the later part of the 3-month stage is still uncertain. Using epic user stories for that later scope supports the stage plan and release thinking without forcing premature detail.
For the next two timeboxes, the work is close enough to delivery to be refined into user stories so it can be prioritized, estimated, and delivered by the agile teams. This is a fit-for-purpose use of planning artifacts in PRINCE2 Agile: keep project-level control and visibility, while allowing detailed definition to emerge at the right time. The tempting alternative is to detail everything now, but that creates waste and reduces agility when later scope is likely to change.
This gives enough stage-level planning visibility while keeping detailed user stories close to delivery, which is the fit-for-purpose use of epics and stories in the Plans practice.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
A project is using two agile delivery teams and a specialist supplier to build a regulated customer portal. At initiation, the Agilometer showed weak business availability and low agile familiarity in the supplier organization. The project manager now proposes removing the project risk review from stage controls and relying on team impediment boards, adding an item to the risk register only if a problem has already affected a release date.
Which evaluation is the most appropriate?
Best answer: D
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: This approach is not fit for purpose because it removes project-level risk control even though the Agilometer has already shown important uncertainty around collaboration and supplier agility. In PRINCE2 Agile, team boards can inform risk management, but they do not replace the project risk management approach or risk register.
PRINCE2 Agile uses the Agilometer to understand agile suitability and risk exposure in context, then tailor controls accordingly. In this scenario, weak business availability and low supplier agile familiarity are early warning signs that project-level risk visibility is needed, not reduced. The project manager should keep project risk review within stage control, use the risk management approach to define how risks are identified and escalated, and record relevant uncertainties in the risk register while they are still uncertain.
Team impediment boards are useful operational inputs, but they mainly provide team-level visibility. Waiting until a release date has already been affected means the uncertainty has turned into an issue before formal project-level management begins. The closest trap is the agile-sounding idea that local team management alone is enough, but that would weaken governance and delay response.
This is best because Agilometer evidence informs project-level risk tailoring, and uncertain events should be managed as risks before they become issues.
Topic: PRINCE2 Agile Processes and Their Application
During Stage 2 of a PRINCE2 Agile project, two agile teams work in two-week timeboxes. The project manager has tailored control by using a team dashboard and a fortnightly review workshop instead of written checkpoint reports. Additional information: the latest dashboard shows that, even after swapping lower-value stories within the agreed work package, the stage may exceed its time tolerance. Which governance and delivery boundary best fits this situation?
Best answer: B
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: This tailoring is fit for purpose only if the dashboard and review workshop still give the project manager enough checkpoint information to control the stage. Teams can adjust delivery within the work package, but stage tolerance decisions and exception escalation remain project-level responsibilities.
In Controlling a stage, PRINCE2 Agile allows the project manager to tailor how progress information is collected. A team dashboard and a review workshop can replace written checkpoint reports if they provide equivalent checkpoint information. However, changing the artifact or workshop does not change decision rights. The agile team and Product Owner can collaborate on reprioritization within the agreed work package, but the project manager remains accountable for judging the impact on stage tolerances. If a breach is forecast, the project manager escalates by exception to the project board. This keeps agile flexibility at delivery level while preserving PRINCE2 stage control.
Tailoring can change how checkpoint information is gathered, but the project manager still owns stage-level control and exception escalation.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
Project information: A PRINCE2 Agile project has two self-managing delivery teams and a specialist supplier. Both teams use a digital dashboard for local impediments. A data-migration defect has already affected both teams and now needs a supplier contract decision. The organization wants light-touch governance, but the project board expects clear evidence when an issue needs project-level action. Which adaptation of the Issues practice is most appropriate?
Best answer: C
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: The defect is no longer just a team-level impediment because it affects two teams and needs a supplier decision. The best tailoring keeps lightweight team visibility for local issues, but uses the issue register and, when needed, an issue report for project-level control.
In PRINCE2 Agile, a team dashboard is useful for short-cycle visibility of local impediments, but it is not enough on its own when an issue has broader project impact. Here, the problem has already occurred, affects multiple teams, and needs a supplier contract decision, so it has moved beyond normal team self-management.
A proportionate adaptation is to:
This keeps governance light without removing required control. Waiting until a tolerance breach is confirmed is too late, while reporting every blocker to the project board is unnecessarily heavy.
This preserves team autonomy for local impediments while providing the proper project-level issue artifacts for a cross-team issue needing formal action.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
A PRINCE2 Agile project is using an external supplier for a regulatory reporting component. The go-live date is fixed, releases are monthly, and the internal Product Owner can reprioritize user stories as feedback emerges. The supplier is new to agile delivery, and the project board wants clear commercial governance without losing flexibility. Which adaptation of the commercial management approach is most appropriate?
Best answer: C
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: The commercial management approach should support agile delivery without removing PRINCE2 control. In this scenario, the best adaptation is to align commercial terms to incremental releases, permit controlled reprioritization, and keep clear acceptance and escalation responsibilities at the right governance level.
In PRINCE2 Agile, the commercial management approach sits within the Organization practice and should be tailored so supplier arrangements work with agile delivery. Here, the project has a fixed date, monthly releases, evolving backlog priorities, and a supplier that is new to agile. That means the approach should support release-based working and controlled flexibility, while still making responsibilities, acceptance points, and escalation paths explicit.
The key is to be agile in delivery, not informal in governance; the closest distractors either remove control or make reprioritization too slow.
This adapts commercial control to incremental delivery while preserving governance, acceptance, and escalation responsibilities.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
A digital licensing project has three agile teams and uses a project canvas to summarize expected benefits, costs, key assumptions, and major risks while detailed scope evolves. A regulatory change reduces forecast uptake, so the Chief Product Owner reorders epics to maximize value. The project manager asks who owns the decision on whether the project is still justified, using the updated project canvas as input. Which responsibility boundary best fits?
Best answer: C
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: The project canvas supports project-level value and justification decisions, not delivery-team prioritization decisions. In PRINCE2 Agile, the project executive owns continued business justification, while the Chief Product Owner helps optimize product value within that governance boundary.
The key distinction is between product value prioritization and project justification. Reordering epics is an appropriate response by the Chief Product Owner when value assumptions change, but it does not transfer ownership of the decision about whether the project should continue. The updated project canvas provides current evidence on benefits, costs, assumptions, and risks so the project executive can judge whether the project still has a valid justification.
The project manager should make sure that evidence is updated and visible, but the project manager does not own the go/no-go judgment. The senior supplier can advise on feasibility or cost impact, but supplier input is only part of the justification picture. The closest distractor is the Chief Product Owner, because that role owns product value choices across teams, not the project-level business justification decision.
Continued business justification is a project-level accountability of the project executive, and the project canvas supports that decision with current value evidence.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
Project information: A PRINCE2 Agile project uses one delivery team with two external suppliers under separate outcome-based contracts. In the first release, the Product Owner swapped two similar-sized user stories, but one supplier later raised an extra charge because nobody had defined who could approve backlog substitutions or when a commercial change must be escalated. The project manager wants to prevent repeat disputes without slowing timeboxes. What is the best next step?
Best answer: A
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: The weakness is unclear commercial authority in a multi-supplier setting, not agile reprioritization itself. The best response is to tailor the commercial management approach and related roles so teams can swap work within agreed limits, while contract-affecting changes still follow controlled escalation.
In PRINCE2 Agile, supplier or commercial complexity is handled through proportionate tailoring of the Organization practice. Here, the problem is that backlog substitution happened without clear commercial decision rights, so the project needs better role clarity and governance boundaries rather than less agility.
Updating the commercial management approach and related role descriptions is the best next step because it can define:
This keeps timeboxes responsive while preserving PRINCE2 Agile control. Options that give unilateral authority to a delivery role, freeze the backlog in detail, or rely only on reporting data do not fix the real weakness: unclear commercial governance.
This is proportionate because it clarifies commercial authority and escalation while preserving agile reprioritization within agreed limits.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
A PRINCE2 Agile project is using three agile teams to deliver a new customer portal. Each team has its own Product Owner, but stakeholders are giving conflicting priorities and the project manager wants one clear business voice across the project. Which TWO statements correctly describe the use of the Chief Product Owner and Product Owner roles in this situation? Select TWO.
Correct answers: C, D
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: A Chief Product Owner is useful when several Product Owners or teams need one coherent business direction. Product Owners then keep their team-level focus on detailed backlog decisions and day-to-day clarification within that overall direction.
In PRINCE2 Agile, the key distinction is control level and purpose. A Chief Product Owner provides a single, project-level business view when priorities must be aligned across multiple teams, product areas, or Product Owners. That role helps reconcile competing demands and keeps value and scope decisions consistent across the project.
A Product Owner works much closer to the delivery team. The Product Owner refines detailed backlog items, answers day-to-day questions, and supports acceptance of completed work for that team or product area. This preserves agile responsiveness while keeping project-level prioritization coherent.
Cross-team priority decisions should not be delegated independently to separate Product Owners, and the Chief Product Owner should not absorb all detailed team-facing work.
Correct because the Chief Product Owner provides one project-level business direction when multiple Product Owners need aligned priorities.
Correct because a Product Owner supports day-to-day team decisions on detailed requirements within the agreed overall priorities.
Topic: Agile Mindset, People, and Change Management
A PRINCE2 Agile project is delivering a new customer portal through three agile teams. Each team already has a Product Owner, the teams are agile-mature, and the project board still requires clear project-level accountability for priorities, reporting, and tolerance management. To reduce overhead, roles will be tailored. Which adaptation is MOST appropriate?
Best answer: A
What this tests: Agile Mindset, People, and Change Management
Explanation: A multi-team agile project often needs a Chief Product Owner to coordinate business priorities across team Product Owners. This keeps day-to-day delivery decisions with the teams while the project manager remains accountable for project-level control, reporting, and tolerance management.
This is an application of the PRINCE2 principle of defined roles, responsibilities, and relationships in an agile context. The project is complex enough to need coordination across several Product Owners, but it still needs clear separation between governance and delivery accountability. A Chief Product Owner provides project-level alignment on value and priorities across teams, while the project manager remains the key link to the project board for progress, reporting, and control.
Mature agile teams can self-manage delivery, but that does not remove project-level accountability. Tailoring should simplify where sensible, not blur responsibilities. Direct reporting from delivery roles to the project board, or moving business-priority ownership to the senior supplier, weakens the governance structure instead of adapting it proportionately.
The key takeaway is to add coordination where complexity requires it without collapsing governance and delivery roles.
This preserves project governance through the project manager while giving the project a single business-facing role to coordinate priorities across multiple Product Owners.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
During Initiating a project, the project board is asked to authorize the first delivery stage for a self-service portal project. The project manager proposes using only the project canvas and a prototype team dashboard as value and justification evidence.
Project information:
Project canvas shows:
- target users and problem statement
- desired outcome: reduce call-centre demand
- three Must Have epics
- estimated annual saving: \$180,000
Current evidence does not show:
- whole-life cost
- benefit measures or benefit owners
- major risks or dis-benefits
The prototype team dashboard shows stable throughput and low defects.
Which evaluation is MOST fit for purpose?
Best answer: D
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: A project canvas is useful as a concise, visual summary of value, but it is not enough here for stage authorization. The board still lacks key justification evidence on whole-life cost, measurable benefits and ownership, and significant risks or dis-benefits, while the team dashboard only shows delivery performance.
In PRINCE2 Agile, the project canvas can be a strong early business case support artifact because it summarizes the problem, value idea, and key scope in a simple visual form. However, it is only fit for purpose if it gives enough evidence for the decision being made. In this scenario, the intended purpose is project board authorization of a delivery stage, so the board needs more than a value summary and positive prototype metrics.
The missing items are critical business justification evidence:
The prototype team dashboard helps show delivery health, but it does not replace project-level business case evidence. A product backlog also does not replace the project canvas or business justification; it supports prioritized delivery. The key point is that a useful agile artifact is not automatically sufficient for a governance decision.
Stage authorization needs sufficient business justification, and the canvas plus team metrics do not cover the missing cost, benefit ownership, and risk evidence.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
During Controlling a Stage, a project manager is about to authorize a work package for an agile team to build a reporting module. The Product Owner has prioritized the related user stories in the product backlog, but the Chief Product Owner and the operations lead disagree about required response time and audit-trail behaviour. The team coach suggests clarifying this later during the timebox. What should the project manager do next to best support quality expectations?
Best answer: A
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: When a defined product has disputed acceptance expectations, the product description is the best PRINCE2 Agile artifact to resolve them. It sets product-level quality criteria, methods, and responsibilities before work starts, and the product backlog can then reflect those expectations in the delivery items.
In PRINCE2 Agile, the product description is used when a specific product needs clear, agreed quality expectations before delivery begins. In this scenario, the reporting module is a defined product, and the disagreement is about what acceptable quality means, especially response time and audit-trail behaviour. The project manager should therefore create or update the product description before authorizing the work package.
The backlog supports delivery and prioritization, but it should not be the only place where unresolved product-level quality expectations are held.
A product description is the right PRINCE2 Agile artifact for agreeing product-level quality expectations before authorizing delivery.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
A PRINCE2 Agile project is delivering a regulated customer portal through three agile teams, two from external suppliers and one internal. Business representatives are giving conflicting priorities, and each team’s Product Owner is optimizing for local team goals. The project board wants faster value-based decisions without weakening accountability for the release date. Which adaptation of the Organization practice is MOST appropriate?
Best answer: D
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: When several agile teams receive conflicting business priorities, PRINCE2 Agile Organization guidance supports a project-level Chief Product Owner to align value decisions across teams while Product Owners stay close to delivery. Recording this in the project management team structure and role descriptions improves collaboration without weakening governance.
The key Organization practice decision here is how to tailor the role structure so collaboration improves without losing control. The problem is conflicting business priorities across multiple teams and suppliers, not a lack of delivery activity. In PRINCE2 Agile, a Chief Product Owner provides a single project-level business view and aligns priorities across teams, while each Product Owner continues to support detailed day-to-day team decisions. Updating the project management team structure and role descriptions makes those decision boundaries explicit, which is especially important on a regulated release. Giving prioritization to the project manager, escalating routine conflicts to the project board, or substituting the senior supplier for customer-side prioritization would all blur role boundaries. The best adaptation keeps business-led prioritization clear and supports agile collaboration at the right levels.
This provides one project-level business voice across teams while keeping team-level collaboration close to delivery and clearly defining authority.
Topic: Agile Mindset, People, and Change Management
A PRINCE2 Agile project has an authorized stage containing three 2-week timeboxes and one planned release. During the second timebox, the Product Owner wants to replace two Should Have stories with one higher-value Should Have story of similar size. All Must Have stories remain protected, and the stage end date and cost tolerance are unchanged. Which governance and delivery boundary best fits this situation?
Best answer: D
What this tests: Agile Mindset, People, and Change Management
Explanation: Manage by stages means the project board controls the project at stage boundaries, not by approving every timebox-level adjustment. Here, the change stays within agreed tolerances and protects the stage Must Have scope, so stage control remains with the project manager while backlog reprioritization stays with the Product Owner and team.
The key principle is that agile delivery happens within PRINCE2 stage control, not instead of it. An authorized stage can contain several timeboxes or a release, and the project board should not be drawn into routine reprioritization when the agreed boundaries remain intact. In this scenario, the change affects only Should Have content, keeps the release goal viable, and does not threaten the stage end date or cost tolerance.
So the project manager remains accountable for controlling the stage against tolerances, while the Product Owner and team can adjust detailed delivery content to optimize value. Escalation to the project board would be needed only if the change forecast a stage-level exception or weakened continued business justification. The closest distractor is the project board option, but that would create unnecessary micro-governance inside an already authorized stage.
This keeps project-level control at the stage boundary while allowing agile reprioritization within the authorized stage unless an exception is forecast.
Topic: PRINCE2 Agile in the Wider Context
A PRINCE2 Agile project has released the first operating version of a claims platform. All agreed project products have met acceptance criteria, support staff are trained, service support is active, and a permanent product team will continue monthly enhancements through continuous deployment. Most benefits will be measured during the next year, and several desirable backlog items remain. Which governance boundary best fits this situation?
Best answer: B
What this tests: PRINCE2 Agile in the Wider Context
Explanation: Project closure ends the temporary project in a controlled way once agreed products are accepted and operational handover is ready. It is not delayed until every future enhancement is delivered or until all benefits are realized. Here, the project manager should recommend closure and the project board should authorize it.
In PRINCE2 Agile, project closure and continuous development operate at different control levels. The project exists to deliver the agreed project products and hand them over in a controlled way. Once acceptance criteria are met, support arrangements are in place, and the organization is ready to operate the product, the project manager can prepare closure information and the project board decides whether to close.
Continuous development and operations then continue under ongoing product and service governance, where new backlog items are prioritized and deployed as part of business-as-usual evolution. Benefits may continue to emerge and be reviewed after closure, so waiting for the backlog to be empty or for a long live-stability period would blur the boundary between temporary project governance and ongoing product management.
Closure is authorized at project level once agreed products are accepted and transition is ready, while ongoing enhancements and benefits continue beyond the project.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
An organization with limited agile experience is running a 10-month PRINCE2 Agile project to deliver a new service portal. Three delivery teams will work in parallel, including one external supplier team.
Project information:
Draft project management team structure
- Project manager will also act as Chief Product Owner
- One Product Owner will serve all teams
- Project assurance will not be appointed
- Agile coach support will be requested only if delivery problems emerge
Which evaluation is most accurate?
Best answer: D
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: The organization approach is under-controlled for the scenario. A multi-team project with an external supplier and low agile maturity needs clear responsibilities, project assurance, and proactive agile support rather than merged or missing roles.
In PRINCE2 Agile, tailoring the organization practice should be proportionate, but it must still provide clear accountability and sufficient control. Here, project scale is increased by parallel teams and supplier involvement, while agile maturity is low. That combination usually needs more role clarity and support, not less.
Combining the project manager and Chief Product Owner blurs project control and product-prioritization responsibilities. Omitting project assurance removes an important governance check. Delaying agile coach support until problems appear is reactive, even though the organization already knows its agile maturity is limited. A shared Product Owner may or may not be workable depending on capacity, but it is not the main weakness in this structure.
The key point is that proportionate tailoring should simplify roles without removing necessary governance or capability support.
This structure removes needed control and support in a multi-team, low-maturity context by blurring responsibilities and delaying agile capability support.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
A project is delivering a self-service insurance claims portal. The business case states the main expected benefit is a 20% reduction in claims-centre calls within three months. The first increment has been released to one pilot region, and the project executive must decide at the end of the stage whether wider rollout should proceed. Which evidence should the project manager present first?
Best answer: C
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: In PRINCE2 Agile, benefit validation needs outcome evidence, not just delivery evidence. A pilot benefits review with real usage and service results most directly shows whether the increment is supporting the benefit stated in the business case.
The key test in the business case practice is whether an increment is contributing to the outcomes that justify the project. In this scenario, the expected benefit is a reduction in claims-centre calls, so the strongest evidence is measured operational performance from the pilot compared with a baseline. That is benefit evidence because it shows actual change in business results, not just activity or completion.
All of these can increase confidence, but they do not directly validate whether the expected benefit is being achieved. The closest distractor is the quality evidence, because the increment must be fit for purpose, but quality alone does not prove business value.
It directly compares live operational outcomes with the expected benefits, so it is the strongest evidence that the increment is creating value.
Topic: PRINCE2 Agile Processes and Their Application
An e-commerce project is using two-week timeboxes and has a fixed date for a new tax rule. To “work more agile”, the Project Executive proposes three changes to Directing a project:
Which action is the BEST tailoring decision?
Best answer: C
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: Directing a project can be tailored for agile delivery, but not by removing project board decision rights or relying only on team-level information. The best approach keeps stage and exception authority with the project board, uses lightweight project-level evidence, and lets the Chief Product Owner optimize value only within agreed tolerances.
In an agile context, Directing a project should become lighter and faster, not weaker. Sprint reviews and team dashboard burn charts are useful delivery evidence, but they are team-level inputs. The project board still needs project-level evidence and must retain decision rights for stage authorization and exception handling under management by exception. The Chief Product Owner can help maximize value through prioritization, but cannot take over project board authority for forecast tolerance breaches.
The heavier-control alternative is also unsuitable because it pushes the project board into routine backlog decisions that should stay closer to delivery.
This keeps project board authority and project-level evidence while tailoring the mechanics to stay lightweight and agile.
Topic: Agile Mindset, People, and Change Management
An agile project will deliver a customer service app in two releases, each built through four 2-week timeboxes. The project board has approved funding only through the first release because benefit evidence and supplier performance must be reviewed before committing to the second. To reduce governance overhead, the project manager proposes one delivery stage covering both releases, relying on timebox reviews, a team dashboard, and backlog reprioritization for control. Which evaluation is the MOST appropriate?
Best answer: A
What this tests: Agile Mindset, People, and Change Management
Explanation: The proposal is not fit for purpose. Timeboxes, dashboards, and backlog changes support agile delivery within a stage, but they do not replace a formal stage boundary when the project board must review viability before authorizing more investment.
In PRINCE2 Agile, a stage is a management control unit, while timeboxes and releases are delivery units. They should work together, not replace each other. Here, the board has deliberately limited funding to the first release until it can review benefits evidence and supplier performance. That makes the end of release 1 a clear stage boundary.
Using one long delivery stage would weaken manage by stages because the board would lose an explicit authorization point before release 2. The better tailoring is to keep the iterative timeboxes inside a stage and place the next stage boundary at the release-based decision point.
Treating every timebox as a stage would add unnecessary governance overhead and confuse delivery cadence with project control.
Manage by stages requires board authorization at meaningful control points, and the first release is one because continued funding depends on its review.
Topic: Agile Mindset, People, and Change Management
An agile project is delivering an employee expenses app in 2-week timeboxes. In the last two retrospectives, the team reported that stories were starting before finance representatives were available to answer questions, causing rework and two Must-have stories to slip. The project manager is about to authorize the next work package, and stage tolerances are still within limits. What is the best next step?
Best answer: B
What this tests: Agile Mindset, People, and Change Management
Explanation: The learn from experience principle means lessons should be used during the project, not saved only for closure. Here, the retrospectives reveal a repeatable cause of delay, so the next work package should reflect that learning before the next timebox starts.
In PRINCE2 Agile, learning from experience is continuous. Retrospectives provide evidence about how delivery is working, and the project manager should use that evidence to improve the next decision when change can be made within tolerance. In this scenario, the real problem is not estimation; it is that stories are entering development before the right business input is available. The best response is to capture the lesson and change readiness criteria for upcoming work so the team does not repeat the same waste.
Escalating or delaying action would weaken agile responsiveness and miss the point of continuous learning.
This applies learn from experience by capturing the lesson and immediately changing how future work is prepared within existing tolerances.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
A PRINCE2 Agile project is using two self-managing teams to deliver a customer portal. A third-party supplier provides a security component, and the specialist resource is scarce; any delay would threaten stage tolerance. Fortnightly demos and a project dashboard are already in place. Which adaptation of the senior supplier role is most appropriate?
Best answer: D
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: The senior supplier should be tailored to enable agile delivery, not to run the teams. In this scenario, the role needs to stay engaged enough to assure supplier capability and technical viability, using existing visibility and raising supplier constraints when tolerance is at risk.
In PRINCE2 Agile, the senior supplier represents those who will design, develop, and supply the solution. In an agile context, that role should support fast technical and supplier-side decisions, confirm that the necessary capability is available, and help address dependencies or constraints without taking over team-level work. Here, the scarce specialist resource and third-party component create a supplier-side risk that could affect stage tolerance, so the senior supplier should stay engaged through the existing demos and project dashboard and act when supplier constraints threaten control limits. Requiring daily approvals would micromanage the teams, while handing responsibility to the Chief Product Owner or waiting until the end of the stage would remove needed supplier accountability.
This keeps the senior supplier focused on supplier capability and technical assurance while preserving team autonomy and project-level control.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
A PRINCE2 Agile project uses two agile delivery teams and a supplier. To “stay agile”, the project manager proposes removing the issue register and asking teams to track defects, change requests, and blockers only on their team boards, with review at the end of the stage if anything remains open. Additional information: a supplier interface change has already blocked work and may affect current stage tolerance. What is the best next step?
Best answer: D
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: The tailoring is only effective if it keeps agile teams lightweight without removing needed project control. Team boards can handle day-to-day issues, but the project still needs issue visibility and escalation for matters affecting tolerances, suppliers, or governance decisions.
In PRINCE2 Agile, tailoring the issues practice should be proportionate, not absent. Agile teams can manage many local blockers, defects, and small changes through their normal workflow, but issues that have already occurred and may affect stage tolerance, require cross-team or supplier action, or need project-level decisions still need formal visibility.
A lightweight project issue register with clear escalation triggers preserves both agility and control. It avoids unnecessary administration for minor team matters while ensuring significant issues are assessed and acted on early enough. Waiting until the end of the stage is not fit for purpose when a live supplier issue may already affect tolerance. Using the risk register would also be incorrect because this is an issue, not an uncertainty. Escalating every blocker to the project board would be excessive and slow the teams down.
This is proportionate tailoring: routine team issues stay local, while project-level issues remain visible and can be escalated before tolerances are threatened.
Topic: PRINCE2 Agile Processes and Their Application
During a delivery stage for a mobile payment project, one agile team works in 2-week timeboxes and the go-live date is fixed by regulation. To reduce overhead, the project manager has replaced checkpoint reports with read-only access to the team dashboard, agreed that the Product Owner can approve any forecast breach of stage tolerance by swapping stories, and plans to brief the project board only at the end of the stage. A weekly impediment workshop with the Product Owner and team coach is still planned. What is the BEST action?
Best answer: B
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: The tailoring has gone too far. Agile stage control can be lighter and more visual, but it still needs project-level evidence during the stage and must keep tolerance decisions in the correct PRINCE2 Agile governance path. Keeping the workshop while restoring lightweight reporting and exception escalation is the best balance.
Controlling a stage in an agile context should be tailored to support fast delivery, not to remove necessary control. The weekly impediment workshop and team dashboard are useful agile mechanisms, but they do not replace the project manager’s need for checkpoint information and ongoing project-level reporting. The project board should receive progress visibility during the stage, not only at the end. Also, a Product Owner may help reorder backlog items within agreed limits, but cannot authorize a forecast breach of stage tolerance; that remains part of exception management.
The closest distractor adds more oversight, but it does so at the wrong level by pulling the project board into team self-management.
This preserves agile delivery visibility while restoring project-level evidence and the correct decision rights for tolerance management.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
A project manager is controlling a stage for a customer portal project delivered by two agile teams. Mid-stage, a supplier API delay means the next release is forecast to finish 3 weeks late; the stage time tolerance is 1 week, and removing any Must Have stories requires project board approval. Team dashboards and checkpoint information already confirm the trend. Which action should the project manager take next?
Best answer: D
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: When delegated tolerance is forecast to be exceeded, the project manager should escalate using an exception report. In this scenario, the delay is beyond stage tolerance and any change to Must Have scope needs project board authorization, so a decision-ready exception report is needed.
In PRINCE2 Agile, an exception report is used in the Progress practice when a delegated tolerance is forecast to be exceeded. The key point is not just to show that delivery is slipping, but to give the project board enough project-level evidence to decide what to do next. Here, team dashboards and checkpoint information help confirm the trend, but they do not replace formal escalation.
The exception report should support decision-making by covering:
That preserves agile responsiveness while keeping governance intact. A routine status update or team-level replanning would not be enough once the agreed tolerance is expected to be exceeded.
An exception report is the correct progress artifact because it escalates a forecast tolerance breach with decision-ready options for the project board.
Topic: Agile Mindset, People, and Change Management
Project information: A financial services organization has an approved agile transformation plan that phases adoption through role clarification, leadership coaching, governance changes, and then wider use of backlog and timebox techniques. A new compliance-reporting project is under pressure to “look agile quickly”, so one team wants daily stand-ups and a Kanban board while keeping line managers assigning tasks, monthly approval gates, and no named Product Owner. What is the best next step?
Best answer: B
What this tests: Agile Mindset, People, and Change Management
Explanation: The best next step is to use the agile transformation plan to guide how the project adopts agile working. The scenario shows local practices being added without the supporting role, leadership, and governance changes needed for sustainable adoption.
An agile transformation plan is used to coordinate how agile capability is introduced across the wider system, not just inside one delivery team. Here, stand-ups and a Kanban board are being proposed while task allocation, approval paths, and product ownership remain unchanged. That is a classic example of isolated local practice changes rather than managed adoption.
This keeps the project moving, but avoids the trap of doing agile practices without the organizational conditions needed for being agile.
An agile transformation plan should sequence the wider changes that make agile practices effective, so the project should align adoption to that plan rather than add isolated rituals.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
A public-service portal project is entering Stage 2. Additional information: Stage 2 contains two planned releases; Release 1 must deliver all Must Have compliance features by September 30, and Release 2 adds Should Haves if stage tolerance allows. The project manager proposes a stage plan showing only team timeboxes and capacity, arguing that the product backlog makes a release map unnecessary. The project board needs stage-level evidence to review forecast delivery.
Which evaluation is the most appropriate?
Best answer: A
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: The proposal is weak because the board needs more than team cadence data. In PRINCE2 Agile, a release map can support a stage plan by showing when planned releases and prioritized scope are expected, giving the project-level view needed for stage control.
A stage plan is still a PRINCE2 Agile control product, even when delivery is agile. When the decision need is stage-level forecast and release confidence, the plan should be supported by a release map that shows the planned releases within the stage and the expected prioritized scope in each one. Here, the key question is whether all Must Have compliance features can be delivered in Release 1 by September 30. Team timeboxes and capacity help with delivery planning, but they do not by themselves show the release-level outcome the project board needs.
The closest wrong idea is treating the release map as a substitute for the stage plan, when it should support it.
A stage plan needs release-level forecasting for project control, so a release map should support it by showing when prioritized scope is expected in each release.
Topic: PRINCE2 Agile Processes and Their Application
During Managing product delivery, the project manager receives this update from an agile team and wants to use it as evidence that the work package is under control before preparing the next highlight report.
Exhibit: Team dashboard excerpt
Timebox 3
Stories accepted: 11
Current velocity: 23 points
Open defects: 2
Blocked stories: 1
Team note: Progress is tracked at story level only.
No forecast yet for completion of the agreed work package products
against the required acceptance criteria and delivery date.
Which clue most clearly shows that this evidence is insufficient for project control?
Best answer: C
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: The decisive clue is the gap between team activity data and project control needs. The dashboard shows useful delivery measures, but it does not forecast whether the agreed work package products will meet their required criteria and date, so the project manager lacks enough evidence for reliable control.
In PRINCE2 Agile, a team dashboard is valuable for short-cycle delivery visibility, but project control requires a clear link from team evidence to the agreed work package outcomes. Here, accepted stories, velocity, blockers, and defects help the team manage its work. The key weakness is the note that progress is tracked only at story level and does not yet forecast whether the agreed work package products will meet the required acceptance criteria and delivery date.
Without that link, the project manager cannot confidently judge whether the work package remains under control or report reliable status upward. A blocked story or a small number of open defects may need attention, but they do not by themselves prove that the evidence is inadequate. The real issue is the missing forecast against the committed work package outcomes.
Story counts and velocity are team data; project control also needs evidence that the agreed work package products remain achievable.
Topic: PRINCE2 Agile in the Wider Context
A PRINCE2 Agile project board agrees to trial AI support.
Exhibit: Improvement note
Need: Faster weekly project-level reporting
Current inputs: team dashboards and checkpoint reports
Constraint: role accountability and approvals must remain unchanged
Which proposed use of AI is MOST appropriate?
Best answer: D
What this tests: PRINCE2 Agile in the Wider Context
Explanation: AI is most appropriate here as decision support for a PRINCE2 Agile element, not as a replacement for role accountability. Drafting the project dashboard speeds reporting, while the project manager still reviews and issues it.
In PRINCE2 Agile, AI can usefully support elements such as reporting, summarization, trend analysis, and preparation of management information. The key condition in the exhibit is that accountability and approvals must stay with the named roles. Drafting a project dashboard from team dashboards and checkpoint reports fits that need because AI is assisting with information assembly, while the project manager remains responsible for interpreting, approving, and issuing the project-level view.
The other proposals cross the line from support into delegated authority:
So the best use is AI-assisted preparation of a PRINCE2 Agile artifact, not AI decision-making.
This uses AI to support a PRINCE2 Agile artifact while leaving review and accountability with the project manager.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
A PRINCE2 Agile project has two agile teams delivering a customer portal. During a timebox review, Team A’s Product Owner proposes moving a high-value identity feature to the next release to protect the current timebox. Additional information: delaying this feature would postpone a benefit used in the business case and may exceed stage tolerance. The Project Executive asks the Product Owner to confirm the new release content immediately. What should the project manager do?
Best answer: B
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: The proposed change is no longer just a team-level backlog decision because it affects forecast benefits and may exceed stage tolerance. In PRINCE2 Agile, that moves the decision above the agile delivery role and into project-level governance.
This scenario tests the boundary between agile delivery roles and project governance roles. A Product Owner can prioritize team work within agreed constraints, but the moment a change affects release-level value, the business case, or stage tolerance, it becomes a project-level matter. The Chief Product Owner is the right role to assess value and priority across the project, while the project board retains control of decisions that affect business justification or tolerances. The project manager should therefore route the decision through the Chief Product Owner and escalate if governance limits are threatened.
The key distinction is control level: delivery roles manage day-to-day backlog detail, while governance roles protect overall value, direction, and decision authority. The tempting mistake is to treat backlog ownership as authority for any scope change, even when the impact has moved beyond the team.
This uses the Chief Product Owner for project-level value decisions and keeps any business case or tolerance change under project board control.
Topic: Agile Mindset, People, and Change Management
A PRINCE2 Agile project is delivering a customer portal. The delivery team works in 2-week timeboxes and aims for a release every 6 weeks. After the first release, the Project Executive asks whether management stages should be removed and replaced by release reviews to “stay agile”. Which TWO responses apply the PRINCE2 principle of manage by stages correctly? Select TWO.
Correct answers: C, D
What this tests: Agile Mindset, People, and Change Management
Explanation: In PRINCE2 Agile, iterative delivery and manage by stages work together. Timeboxes and releases create frequent feedback, but management stages remain the project-level control points for review, authorization, and forward planning.
Manage by stages means controlling the project through a series of management stages, each ending with a formal decision point. In an agile project, that control sits above the delivery rhythm of timeboxes and releases. Agile delivery provides rapid learning and frequent increments, but it does not remove the need for stage-level governance.
The key distinction is that releases inform project control, but they do not replace stage authorization.
Management stages provide project-level control, while timeboxes remain team-level delivery cycles within a stage.
A stage boundary uses evidence from recent iterations or releases to confirm continued business justification and plan ahead.
Topic: PRINCE2 Agile Processes and Their Application
A Project Board is directing a stage that is being delivered in two-week timeboxes. The board has approved fixed time and cost tolerances for the stage, and only the Must-have outcomes are mandatory; Should-have and Could-have stories may be traded. The Chief Product Owner expects frequent reprioritization during the stage, but board members will only meet weekly. Which governance action is MOST fit for purpose?
Best answer: A
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: The best approach is to preserve management by exception while enabling agile delivery to continue. The Project Board should delegate day-to-day scope trade-offs within agreed tolerances and retain authority for stage-level decisions and exceptions.
In Directing a project, the Project Board should keep control of authorization, tolerances, and exception decisions, but it should not become a bottleneck for routine backlog movement inside agreed limits. Here, time and cost tolerances are already fixed, and only Must-have outcomes are mandatory, so lower-priority scope can be adjusted during the stage without needing repeated board approval. A fit-for-purpose response is to define that delegated authority clearly now, allow the project manager and Chief Product Owner to manage within it, and maintain project-level visibility through normal reporting. If the reprioritization threatens the Must-have outcomes or stage tolerances, the project manager escalates by exception. This preserves board authority without stopping agile delivery.
It keeps day-to-day prioritization within delegated authority while stage tolerances and exception decisions remain with the Project Board.
Topic: PRINCE2 Agile Processes and Their Application
A delivery team is finishing an authorized work package within a stage. On the fixed end date of the timebox, the project manager receives this checkpoint excerpt.
Exhibit:
WP-7 checkpoint excerpt
Priority in work package: 5 Must, 2 Should, 1 Could stories
Completed to Definition of Done: 5 Must, 1 Should
Not completed: 1 Should, 1 Could
Acceptance minimum: all Must stories complete
Quality: completed stories accepted by Product Owner
Tolerance: end date fixed; scope may vary using MoSCoW
Forecast: no work package or stage tolerance breach
Which action should the project manager take next in the Managing product delivery process?
Best answer: B
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: In PRINCE2 Agile, Managing product delivery should preserve both control and agility. Here, the minimum agreed scope has been completed, the delivered stories meet the Definition of Done, and no tolerance breach is forecast, so the right action is to take delivery and handle unfinished lower-priority stories through normal replanning.
The key judgment is whether the work package has met its agreed delivery conditions. The exhibit shows that all Must stories are complete, the completed work meets the Definition of Done, the Product Owner has accepted those stories, and both work package and stage tolerances remain intact. In an agile context, fixed time and flexible scope mean lower-priority items can be moved out without treating the situation as a failure.
The project manager should therefore:
Extending the timebox or escalating would be disproportionate because the agreed minimum scope has been delivered and tolerances are not under threat.
All Must stories are done, quality is confirmed, and tolerances are intact, so the work package can be delivered while lower-priority scope is reconsidered later.
Topic: Agile Mindset, People, and Change Management
A PRINCE2 Agile project is delivering a citizen portal through two agile teams. The launch date is fixed by regulation. Mid-stage, a supplier delay reduces capacity, so several Should-have features may need to move out of the next release, but all Must-haves can still be delivered and stage tolerances are not forecast to be exceeded. The affected features sit in different team product backlogs.
Which responsibility boundary best fits this situation?
Best answer: B
What this tests: Agile Mindset, People, and Change Management
Explanation: When time is fixed, agile scope performance is usually protected by deferring lower-priority items, but the prioritization decision should stay with the role that owns business value. Because this change crosses two teams yet remains within tolerances, the Chief Product Owner should make the project-level choice and the Product Owners should reflect it in their backlogs.
Scope performance in agile delivery is often managed by flexing lower-priority scope while protecting a fixed time target. Here, the important boundary is between project-level value decisions and team-level delivery decisions. Because the reprioritization affects release content across two teams, the project-level choice should be made through the project backlog by the Chief Product Owner. Product Owners then translate that decision into their own product backlogs for delivery.
The project manager still maintains PRINCE2 governance by monitoring stage performance and would escalate only if tolerances were forecast to be exceeded. The Project Executive does not need to approve routine reprioritization when business justification and tolerances remain intact. Letting the project manager or delivery teams own the value trade-off would blur the boundary between governance, product ownership, and delivery.
Cross-team scope trade-offs that change release content belong to the Chief Product Owner, while Product Owners apply that decision in their team backlogs.
Topic: PRINCE2 Agile Processes and Their Application
A PRINCE2 Agile project is at the end of Stage 2. The project board has already received the updated business case and draft Stage 3 plan. Before deciding whether to authorize Stage 3, it asks for the strongest project-level evidence of how Stage 2 actually performed. Which evidence should the project manager provide?
Best answer: A
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: At a stage boundary, the project board needs project-level evidence to decide whether to authorize the next stage. The end stage report is designed for that decision because it summarizes actual stage performance and control information, rather than only team-level delivery signals.
In PRINCE2 Agile, approving the next stage is a governance decision made at the stage boundary. Even in an agile delivery environment, the board needs a project-level view of how the current stage performed, especially against tolerances, and whether continued investment remains justified. The end stage report is the main evidence product for that purpose because it consolidates performance information from the stage into a form suitable for board review.
Team dashboards, sprint reviews, and retrospectives are all useful, but they mainly support day-to-day delivery control, stakeholder feedback, or team improvement. They can inform the project manager’s assessment, yet they do not replace the formal stage-boundary evidence needed for authorization. The closest distractor is the team dashboard, because it contains useful metrics, but it is still not the board’s primary approval evidence.
An end stage report is the stage-boundary product that gives the project board project-level evidence on stage performance for the next-stage decision.
Topic: PRINCE2 Agile Processes and Their Application
A project delivering a new claims service uses 2-week timeboxes within 10-week stages. To tailor Directing a project for agile delivery, the project board has agreed to:
Which evaluation is the most accurate?
Best answer: C
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: This tailoring goes too far. In an agile context, the project board can use timebox reviews, dashboards, and workshops as inputs, but it still needs project-level evidence and explicit stage authorization decisions. Removing those controls weakens management by stages rather than tailoring it.
Directing a project can be tailored for agile delivery, but the tailoring must preserve project board control. Agile artifacts such as a team dashboard and outputs from timebox reviews improve transparency, and a release planning workshop can help the board understand priorities and delivery options. However, these are inputs to direction, not replacements for project-level governance evidence or decision rights.
The closest distractor is relying on exception reporting alone, but that leaves the board without normal stage control.
It correctly identifies that agile visibility supports project board decisions, but does not remove the need for project-level reports and stage authorization.
Topic: Agile Mindset, People, and Change Management
A PRINCE2 Agile project uses two delivery teams. At the end of the first stage, team retrospectives and project reporting show repeated rework because stories entered timeboxes with unclear acceptance criteria. The teams are agile-mature, but the organization is new to PRINCE2 Agile and the project board wants visible evidence that lessons are being applied without adding heavy governance. Which adaptation is most appropriate for the next stage?
Best answer: B
What this tests: Agile Mindset, People, and Change Management
Explanation: The best adaptation turns retrospective feedback into a concrete change for the next stage. Adding a shared readiness check and recording the lesson applies learn from experience continuously while still giving the project board visible, proportionate evidence.
In PRINCE2 Agile, learn from experience is not just about capturing lessons; it is about using them to improve the next decision. Agile teams generate frequent feedback through retrospectives, reviews, and short delivery cycles, so useful lessons should be applied quickly when a clear pattern appears.
Here, the pattern is repeated rework caused by stories entering timeboxes before they were ready. A proportionate response is to adapt the next stage by adding a shared readiness check, such as a Definition of Ready step, and recording that change in the lessons log. This preserves agility because the teams keep working in short cycles, and it preserves PRINCE2 control because the project board can see that learning has led to action.
Waiting, escalating detailed story decisions to the board, or relying only on informal team memory would weaken either responsiveness or governance visibility.
This applies the lesson immediately in the next stage and keeps proportionate evidence for the project board.
Topic: PRINCE2 Agile Processes and Their Application
Project information: During Controlling a Stage, the project manager receives this checkpoint summary from an agile team:
Timeboxes left in stage: 2
Must Have stories complete: 3 of 8
Blocked item: supplier API unavailable now
Forecast: stage end date will slip by 3 weeks
Stage time tolerance: 0 weeks
Which responsibility boundary best fits this situation?
Best answer: D
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: The key clue is the forecast three-week delay against zero stage time tolerance. When team-level information shows a likely tolerance breach, it becomes a project manager control matter in Controlling a Stage, with exception escalation if recovery is unlikely.
In PRINCE2 Agile, agile teams self-manage detailed delivery, but the project manager remains accountable for stage control. Team-level evidence such as a checkpoint summary should trigger project manager action when it shows an actual issue or a forecast that threatens agreed stage tolerances. Here, the supplier API problem has already occurred, and the team now forecasts a three-week delay while stage time tolerance is zero. That moves the situation beyond local replanning. The project manager must assess the impact on the stage, decide whether recovery is possible within tolerance, and, if not, raise an exception to the project board. Team replanning can still help, but it does not replace project-level control once a tolerance breach is forecast.
The checkpoint summary forecasts a breach of stage time tolerance, so it requires project manager control and possible exception escalation.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
A project to launch a digital claims service uses two external suppliers on different contract types. Agile teams work in 2-week timeboxes, but backlog reprioritization and acceptance questions are repeatedly escalated directly to the Project Executive because commercial routes and supplier responsibilities were not defined clearly. The Project Manager wants a proportionate tailoring change that fixes this weakness without slowing delivery. What is the best action?
Best answer: A
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: The best response is to tailor the Organization practice by adding a commercial management approach and clearer role boundaries. That fixes the supplier-routing weakness while keeping day-to-day agility and preserving project-level commercial control.
In PRINCE2 Agile, supplier or commercial complexity is handled by adding enough organizational clarity, not by removing control or stopping change. Here, the weakness is unclear decision routes between agile delivery and project-level commercial governance. A proportionate fix is to define a commercial management approach and update role descriptions so routine supplier matters flow through the Project Manager and Senior Supplier, while backlog prioritization remains agile within agreed tolerances.
The tempting alternatives either give commercial authority to the wrong role, overload the Project Board, or reduce agility by freezing change.
This clarifies commercial decision paths and authority boundaries while preserving agile reprioritization and normal exception control.
Topic: Agile Mindset, People, and Change Management
A PRINCE2 Agile project delivers a usable increment every 2 weeks. The project executive asks the project manager how to respond to the quality performance trend below without weakening agile delivery or project control.
Exhibit: Quality performance note
Timebox length: Fixed at 2 weeks
Definition of Done: regression tests pass; no critical defects open
Carry-forward defects: 2, then 3, then 4 over last 3 timeboxes
All carry-forward defects are minor
Stage tolerance: target date fixed; lower-priority scope may be varied
Which action best balances quality performance with agile delivery and PRINCE2 governance needs?
Best answer: C
What this tests: Agile Mindset, People, and Change Management
Explanation: The exhibit shows an agreed quality threshold already exists: regression tests must pass and no critical defects can remain open. Because only minor defects are being carried forward and lower-priority scope can vary, the balanced response is to keep the timebox stable, adjust scope, and escalate only if tolerances are forecast to be exceeded.
Quality performance in iterative delivery means keeping each increment fit for purpose without destroying delivery cadence. In this case, the quality target is already defined through the Definition of Done, and the trend shows only minor defects, not failure of the agreed acceptance level. The best response is therefore to preserve the fixed timebox, use prioritization to free capacity for defect fixing, and treat the trend as warning information for project control.
The key point is to balance fit-for-purpose quality with agile flow, rather than chasing perfect scope completion or adding unnecessary governance.
This protects the agreed quality bar while preserving fixed-timebox delivery and using PRINCE2 escalation only at the correct control level.
Topic: PRINCE2 Agile Processes and Their Application
An agile project is ending Stage 2, and the project board must decide whether to authorize Stage 3. The project manager plans to present only combined team dashboards because they are the most current view of work. Additional information: a release review workshop has shown working products, the Chief Product Owner confirmed delivered Must Have stories still support current priorities, and residual risks remain within stage tolerance. Which improvement is most fit for purpose?
Best answer: D
What this tests: PRINCE2 Agile Processes and Their Application
Explanation: The project board needs evidence that matches the purpose of Directing a project: making key decisions with overall project control. The end stage report and project dashboard provide that governance view, while the release review output adds collaborative evidence of delivered value and current priorities.
In Directing a project, the project board needs evidence at the project level when deciding whether to authorize the next stage. Team dashboards are useful inputs, but they mainly show delivery progress and flow within teams. They do not, on their own, give enough governance evidence about overall stage performance, remaining viability, and readiness to proceed.
The end stage report summarizes how the stage performed and whether the project remains controlled. The project dashboard gives a concise project-level view of progress, risks, and exceptions. Output from the release review workshop adds collaborative evidence that working products were demonstrated and that priorities still support business value. Because tolerances remain within bounds, this combined evidence is fit for purpose for a timely board decision. The key point is to support the board with project-level evidence, not only team-level activity data.
These give the board project-level governance evidence plus collaborative confirmation of delivered value and current priorities.
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 for concept review, then return here for PM Mastery practice.