Try 10 focused PRINCE2 Agile Practitioner questions on PRINCE2 Agile Practices, Roles, with answers and explanations, then continue with PM Mastery.
| Field | Detail |
|---|---|
| Exam route | PRINCE2 Agile Practitioner |
| Topic area | PRINCE2 Agile Practices, Roles |
| Blueprint weight | 44% |
| Page purpose | Focused sample questions before returning to mixed practice |
Use this page to isolate PRINCE2 Agile Practices, Roles for PRINCE2 Agile Practitioner. Work through the 10 questions first, then review the explanations and return to mixed practice in PM Mastery.
| Pass | What to do | What to record |
|---|---|---|
| First attempt | Answer without checking the explanation first. | The fact, rule, calculation, or judgment point that controlled your answer. |
| Review | Read the explanation even when you were correct. | Why the best answer is stronger than the closest distractor. |
| Repair | Repeat only missed or uncertain items after a short break. | The pattern behind misses, not the answer letter. |
| Transfer | Return to mixed practice once the topic feels stable. | Whether the same skill holds up when the topic is no longer obvious. |
Blueprint context: 44% of the practice outline. A focused topic score can overstate readiness if you recognize the pattern too quickly, so use it as repair work before timed mixed sets.
These questions are original PM Mastery practice items aligned to this topic area. They are designed for self-assessment and are not official exam questions.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
A PRINCE2 Agile project is using one agile delivery team to build a claims portal. During the current timebox, an external supplier confirms that a security component will be delivered 3 weeks late, and several Must have stories may now miss the planned release. The organization wants quick local decisions, but the project board requires visibility of anything that could threaten stage tolerance. Which adaptation of issue handling is most appropriate?
Best answer: D
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: The supplier delay has already happened, so it is an issue, not a risk. The best tailoring is to let the agile team handle small local adjustments while using PRINCE2 Agile issue controls for a material item that could affect tolerance.
In PRINCE2 Agile, issue handling should be tailored so that routine day-to-day delivery changes can be handled quickly, while significant matters still receive project-level control. In this scenario, the supplier delay is a real event affecting Must have delivery, so it should be treated as an issue and recorded appropriately.
A proportionate adaptation is to define clear thresholds: minor defects or story swaps can stay within team-level management, but a significant external dependency issue belongs in the issue register. If impact analysis shows that stage tolerance may be exceeded, the project manager should escalate using an issue report. This preserves agile responsiveness without weakening governance.
The key point is to separate local agile adjustment from formal project issue control, not to replace one with the other.
This keeps routine delivery decisions agile while giving project-level visibility and escalation for a significant issue that has already occurred.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
A medium-sized PRINCE2 Agile project is delivering an employee portal. User feedback is changing many lower-priority stories, but the target benefits, overall budget, and planned go-live window are still stable. The Project Executive wants the business case to remain valid without creating unnecessary reapproval overhead. Which TWO actions are most appropriate? Select TWO.
Correct answers: C, D
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: PRINCE2 Agile keeps the business case as a live control, but it does not require heavy governance for every backlog change. The proportionate response is to manage value and justification at project level while allowing detailed scope to evolve and reviewing viability at stage-level control points.
In PRINCE2 Agile, continued business justification must be maintained, but agility usually comes from allowing detailed scope to change as learning emerges. In this scenario, the overall benefits, budget, and go-live window are still stable, so the business case should stay focused on value, benefits, costs, risks, and outcomes rather than on fixed story detail. Detailed changes belong in the product backlog. The proportionate control is to revisit the business case at stage boundaries using evidence from delivered increments, stakeholder feedback, and any updated benefit assumptions. That preserves governance for the Project Executive and project board without creating unnecessary approval cycles for normal agile reprioritization.
The right balance is flexible detailed scope with controlled ongoing justification.
This preserves project-level justification while allowing agile scope detail to change at backlog level.
This gives proportionate governance from real evidence without reacting to every small reprioritization.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
On a PRINCE2 Agile project, the project board asks whether the current stage remains under control. The project manager has received only this team dashboard from the delivery team.
Team dashboard excerpt
Timebox: 5 of 6
Stories done: 21/28
Must Haves done: 10/10
Open blockers: 1
Defects awaiting fix: 2
Release forecast: All Must Haves on track
Which interpretation BEST reflects how a PRINCE2 practice should be applied here?
Best answer: D
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: The exhibit shows team-level delivery data, which is useful but not enough on its own for a project board decision. In PRINCE2 Agile, the Progress practice provides proportionate control by turning team information into project-level evidence such as tolerances, risks, and forecast status.
A team dashboard supports agile delivery by showing short-cycle progress, blockers, and forecast at team level. However, the project board needs project-level evidence to judge whether the stage is still within control. In PRINCE2 Agile, that is the role of the Progress practice: it uses agile delivery data as input, then adds the governance information needed for decision support, such as tolerance status, major risks or issues, and stage or release forecast.
This is proportionate control because the team keeps lightweight, useful metrics, while the project layer adds only the extra evidence needed for governance. Completing all Must Haves is positive, but it does not by itself confirm overall stage control. Likewise, open defects do not automatically justify exception escalation unless tolerances are forecast to be exceeded.
The key distinction is team visibility versus project-level decision evidence.
It adds the project-level evidence needed for board decisions without overloading the agile team with extra control.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
A PRINCE2 Agile project is delivering a new citizen self-service portal through three agile teams. Stakeholders frequently disagree on which features should enter the next release, and the project board wants one person accountable for overall product priorities. The project manager proposes appointing only three Product Owners, one for each team, and asking them to rotate the project-wide prioritization decisions. Which evaluation is MOST fit for purpose?
Best answer: B
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: This approach is not fit for purpose because the scenario needs one clear project-level authority for product direction across three teams. In PRINCE2 Agile, that is the Chief Product Owner, while each Product Owner works with an individual team on detailed priorities and acceptance.
In PRINCE2 Agile, the Chief Product Owner and Product Owner operate at different levels. The scenario describes multiple teams, competing stakeholder demands, and an explicit need for one person accountable for overall product priorities. That is a project-level coordination and value decision, so it fits the Chief Product Owner role. Product Owners are still useful, but their purpose is to work closely with their own teams on detailed backlog clarification, sequencing within the agreed direction, and acceptance of completed items. Asking several Product Owners to rotate project-wide prioritization weakens authority and accountability because no single role owns the cross-team trade-offs. The closest distractor is relying on the Project Executive, but business justification and governance do not replace the Chief Product Owner’s product-direction role.
A Chief Product Owner provides single project-level accountability for cross-team product direction, while Product Owners focus on team-level backlog detail and acceptance.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
A PRINCE2 Agile project uses a live team dashboard updated daily by the delivery team. It shows progress against the current work package, blocked items, defects, and a forecast for finishing the timebox. The project manager wants to use it instead of separate checkpoint reports, and the Project Executive asks to use the same dashboard instead of highlight reports. Additional information: it does not show stage tolerance, business case status, or overall project risk. Which boundary of responsibility is MOST appropriate?
Best answer: D
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: A team dashboard can be a fit-for-purpose substitute for separate checkpoint reporting when it gives the project manager agreed delivery-level evidence. It does not remove the project manager’s responsibility to provide project-level progress information to the project board.
In PRINCE2 Agile, progress information should match its control level and audience. A team dashboard is a delivery-level artifact, so it can provide appropriate checkpoint-level evidence if it shows agreed work package progress, impediments, quality-related information, and short-term forecast data. That makes it suitable for the project manager’s day-to-day control.
However, the project board needs project-level governance evidence, not raw team data alone. Because this dashboard does not show stage tolerance, business case status, or overall project risk, it is not sufficient as a replacement for highlight reporting to the board. The project manager must still interpret and escalate progress at the project level. The key distinction is between team visibility for control and project reporting for governance.
This keeps team-level progress evidence for checkpoint purposes while preserving the project manager’s accountability for project-level governance reporting.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
A PRINCE2 Agile project is delivering a regulated customer portal using two agile teams working in 2-week timeboxes. Team-level agile maturity is good, but the project board is new to agile and wants confidence that significant problems will not be hidden. Most delivery blockers are resolved within a day, but some issues could affect supplier commitments, compliance, or stage tolerance. Which tailoring of the issues practice is MOST appropriate?
Best answer: B
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: The best tailoring is the option that stays lightweight for day-to-day agile delivery but still keeps formal control for significant issues. In PRINCE2 Agile, tailoring should be proportionate, not remove issue visibility, escalation, or governance.
Effective tailoring of the issues practice means matching the level of control to the impact of the issue. In this scenario, the teams are mature enough to resolve short-lived blockers quickly, so forcing full formal handling for every small problem would be excessive. However, the project board is new to agile and the project is regulated, so issues that could affect compliance, supplier commitments, approvals, or stage tolerance still need clear recording and escalation.
This is more fit for purpose than either removing issue control or making every small blocker a board-level matter.
This keeps issue handling fast at team level while preserving project-level control and escalation for significant issues.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
A PRINCE2 Agile project is delivering a new claims portal using two agile teams. During the first stage, functional managers keep giving developers urgent work directly, the teams are using inconsistent working agreements, and a senior stakeholder asks the agile coach to decide what should be built next. Which TWO actions are appropriate for the agile coach? Select TWO
Correct answers: A, D
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: The agile coach should strengthen agile capability and help remove systemic barriers, not take over accountable delivery or governance decisions. In this scenario, the appropriate contributions are coaching people on agile ways of working and escalating the recurring management interference through the project manager.
In PRINCE2 Agile, the agile coach is an enabling role. The coach helps improve agile maturity, encourages the right behaviors, and supports effective agile working across the project environment. Here, managers are bypassing team boundaries and creating a recurring organizational impediment, while the teams also need help becoming more consistent in how they work.
The key distinction is that the agile coach supports capability and transparency, but does not own product prioritization or governance authority.
This fits the agile coach role because it builds agile capability and consistent behaviors without taking over delivery accountability.
Repeated organizational interference is a systemic impediment, so the agile coach should surface it and escalate it through the proper project authority.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
A customer portal project will run a 16-week stage using two experienced agile teams and three planned releases. The first release date is fixed by regulation, and the Chief Product Owner expects lower-priority features to move between releases using MoSCoW. The project board wants enough information to authorize the stage, but not sprint-level detail. How should the project manager tailor the stage plan and release map?
Best answer: C
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: A stage plan should remain a stage-level control product, while the release map adds agile visibility across planned releases. This gives the project board enough information to authorize the stage, while detailed stories stay flexible in backlogs and team plans.
In the Plans practice, the stage plan provides the PRINCE2 control view and the release map provides the agile delivery view. For stage authorization, the project board needs stage-level information such as objectives, major products, release milestones, dependencies, and tolerances. The release map then shows how prioritized backlog items are expected to land across releases, supporting forecasting and discussion of delivery risk without locking down detailed scope. Detailed user stories and sprint tasks belong in the product backlog and team plans, where the Chief Product Owner and teams can refine them as learning emerges. Using only the release map would weaken governance evidence, while baselining stories or freezing the full backlog would over-tailor and reduce agile responsiveness.
This preserves stage-level governance for authorization while the release map supports agile release forecasting and keeps detailed scope flexible.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
During Initiating a project, a PRINCE2 Agile project plans to use two-week timeboxes with an external supplier. The Agilometer shows high flexibility on scope, but low customer availability and weak collaboration between business users and the supplier. The project executive asks the project manager what should be done next with these results. What is the best response?
Best answer: B
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: The Agilometer is used to reveal agile suitability and risk exposure, not to approve or reject agile working by itself. Here, low customer availability and weak collaboration should be captured in project-level risk information and used to tailor practical responses.
In PRINCE2 Agile, the Agilometer helps the project manager assess how suitable agile working is in the project context and where risk exposure exists. In this scenario, low customer availability and weak collaboration increase the risk of slow decisions, poor feedback, and delivery friction, so the findings should feed the Risk practice. That means recording the exposure in the risk register, updating the risk management approach, and agreeing proportionate responses such as stronger Product Owner or Chief Product Owner availability, planned collaboration points, or extra facilitation.
The Agilometer supports risk-informed tailoring; it is not a pass/fail gate or a progress dashboard.
The Agilometer should inform the risk register and risk management approach so identified exposure can drive proportionate responses.
Topic: PRINCE2 Agile Practices, Roles, and Their Application
During Stage 3 of a PRINCE2 Agile project, the project manager reviews the following risk note before planning the next timebox.
Exhibit: Risk register excerpt
ID: R-21
Cause: Legacy supplier has not finalized data-migration rules
Risk event: Stories built now may need rework later
Effect: Release 1 reporting features could lose up to 2 weeks
Exposure: Medium
Tolerance forecast: Stage tolerance not forecast to be exceeded
Agile context: Team can build a simple prototype next timebox; supplier joins weekly reviews
Which response is the MOST appropriate?
Best answer: D
What this tests: PRINCE2 Agile Practices, Roles, and Their Application
Explanation: A timeboxed prototype is a proportionate risk reduction response because it creates fast learning before more stories are built. Updating the risk register preserves PRINCE2 control, and no exception escalation is needed because stage tolerance is not forecast to be exceeded.
In PRINCE2 Agile, the response should match both the exposure and the control level. Here, the migration problem is still a risk, not an issue, because rework may happen but has not happened yet. The exposure is medium and stage tolerance is still safe, so the project manager should use normal stage control rather than escalate. A short prototype in the next timebox fits agile delivery because it tests assumptions early, reduces uncertainty quickly, and uses supplier feedback at the weekly review. Recording the response and follow-up in the risk register keeps the action visible and governed. Immediate escalation is reserved for forecast tolerance breach, while stopping work or waiting for failure would increase uncertainty and reduce delivery flow.
This reduces uncertainty quickly through agile learning while keeping PRINCE2 control proportionate because the risk remains within stage tolerance.
Use the PRINCE2 Agile Practitioner Practice Test page for the full PM Mastery route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.
Read the PRINCE2 Agile Practitioner guide on PMExams.com, then return to PM Mastery for timed practice.