Prepare for PRINCE2 Agile Practitioner (Version 2) with free sample questions, a 50-question full-length diagnostic, topic drills, timed mock exams, tailoring, agile suitability, prioritization, tolerance, and scenario-based governance decisions, and detailed explanations in PM Mastery.
Start a practice session for PRINCE2 Agile Practitioner (Version 2) below, or open the full app in a new tab. For the best experience, open the full app in a new tab and navigate with swipes/gestures or the mouse wheel—just like on your phone or tablet.
Open Full App in a New TabA small set of questions is available for free preview. Subscribers can unlock full access by signing in with the same app-family account they use on web and mobile.
Use on iPhone or Android too: PM Mastery on the App Store or PM Mastery on Google Play using the same PM Mastery account you use on web. The same PM Mastery subscription works across web and mobile.
Free diagnostic: Try the 50-question PRINCE2 Agile Practitioner full-length practice exam before subscribing. Use it to identify misses around tailoring, agile suitability, prioritization, tolerances, and scenario-based governance decisions.
PRINCE2 Agile Practitioner (Version 2) is the applied PeopleCert route for learners who already know the basics and now need scenario-driven PRINCE2 Agile judgment. Use this page to confirm whether the practitioner layer fits your role before moving into full PM Mastery practice.
PeopleCert’s current public page lists this assessment as PRINCE2 Agile Practitioner (Version 2), and its public naming update maps PRINCE2 Agile to PRINCE2 Agile Version 2. If you searched for the older PRINCE2 Agile Practitioner version 1 route: This route has been replaced or renamed. Use this page to choose the current equivalent.
Official source check: Last checked May 5, 2026 against PeopleCert's PRINCE2 Agile Practitioner Version 2 product page.
PeopleCert lists PRINCE2 Agile Practitioner Version 2 as a 50-question, 150-minute, open-book multiple-choice exam with a 60% passing score. Confirm current book rules, language availability, booking, and delivery details directly with PeopleCert before scheduling.
PRINCE2 Agile Practitioner questions usually reward the option that tailors governance intelligently without losing control, value focus, or delivery adaptability. Weak answers tend to become either rigid method enforcement or uncontrolled agility.
| Scenario signal | First check | Strong answer usually… | Weak answer usually… |
|---|---|---|---|
| The project needs agility but has governance constraints | Tailoring boundary | Adapts agile practices while preserving PRINCE2 principles, roles, tolerances, and decision rights | Removes controls or imposes rigid controls unchanged |
| Scope pressure appears inside a fixed timebox | Prioritization and tolerance | Uses prioritization and escalation rules to protect value and control | Commits to all scope or ignores tolerance impact |
| Team maturity is uneven | Agile suitability and support | Chooses practices appropriate to capability, risk, and stakeholder access | Forces advanced agile practices without readiness |
| Delivery feedback changes assumptions | Business justification and product focus | Updates plans, backlog, quality expectations, or Business Case evidence as needed | Treats feedback as disruption to the original plan |
| Stakeholders want confidence without detail | Transparency | Uses agile information and PRINCE2 reporting to make progress and risk visible | Replaces evidence with reassurance |
| Area | What the exam tests | What PM Mastery practice should force | Common trap |
|---|---|---|---|
| Tailoring | Whether PRINCE2 Agile is adapted to the case facts | Choose the smallest effective governance-plus-agile response | Applying one method recipe everywhere |
| Governance | Whether controls, roles, tolerances, and justification remain active | Preserve authority and escalation while allowing adaptation | Confusing agile flexibility with no control |
| Agile delivery | Whether practices improve feedback, collaboration, and delivery flow | Select practices that fit maturity and risk | Choosing agile terminology without scenario fit |
| Scenario judgment | Whether you can use the case facts before the answer choices | Identify constraint, role, tolerance, and delivery context | Choosing the most fashionable agile answer |
If you want concept-first reading before heavier simulator work, use the companion PRINCE2 Agile Practitioner Version 2 Study Guide on PMExams.com. Then return here for timed mocks, topic drills, explanations, and the full PM Mastery practice route.
Use these child pages when you want focused PM Mastery practice before returning to mixed sets and timed mocks.
Try these 24 public sample questions for PRINCE2 Agile Practitioner V2. They are original PM Mastery practice items aligned to applied PRINCE2 Agile governance, tailoring, collaboration, and delivery scenarios. They are not PeopleCert exam questions and are not copied from any exam sponsor.
Topic: Agile mindset, people, project management, and organizational change management
A PRINCE2 Agile project has three delivery teams and several shared specialists. During recent timeboxes, line managers have moved people between teams, required approval for day-to-day task choices, and discouraged teams from discussing failed experiments in reviews. The project manager wants help changing these organization-wide behaviours while keeping team empowerment and accountability intact.
Which responsibility boundary BEST fits this situation?
Best answer: B
Explanation: The problem is organization-wide micromanagement, not a backlog or reporting issue. In PRINCE2 Agile, the agile coach helps leaders and managers adopt behaviours that support empowerment and learning, while the teams remain accountable for day-to-day delivery within agreed boundaries.
An agile coach supports agile working beyond a single team by helping managers and leaders change behaviours that block collaboration, openness, and empowerment. In this scenario, line managers are interrupting timeboxes, taking over daily choices, and reducing learning by hiding failed experiments. That is an organizational leadership problem, so the boundary should be: the agile coach works with managers to improve the environment, while the teams retain responsibility for how they deliver.
The weaker options shift delivery control to the wrong role and undermine agile team behaviour.
This targets the organizational impediment at the right level while leaving day-to-day delivery ownership with the teams.
Topic: Agile mindset, people, project management, and organizational change management
A customer-service transformation project is using two agile delivery teams. To “be fully agile”, the project manager proposes dropping stage authorizations, highlight reports, and tolerance reviews, relying only on team dashboards and backlog updates. Additional information: the project board still needs visibility of benefits, risks, and forecast exceptions for a fixed launch date. Which evaluation is MOST fit for purpose?
Best answer: A
Explanation: The proposal is weak because it treats PRINCE2 Agile as a substitute for PRINCE2 Project Management control. In PRINCE2 Agile, agile delivery information increases responsiveness, but project-level governance such as stage control, tolerances, and reporting must still be retained and tailored proportionately.
PRINCE2 Agile blends agile ways of working with the governance and control of PRINCE2 Project Management. In this scenario, team dashboards and backlog updates provide useful short-cycle delivery evidence, but they are team-level information. The project board still needs project-level visibility of benefits, risks, tolerances, and forecast exceptions for the fixed launch date. That means stage authorization, highlight reporting, and exception management remain necessary, even if they are made lighter and more responsive.
A fit-for-purpose approach is to:
More team detail does not create project-level control.
PRINCE2 Agile tailors PRINCE2 Project Management controls around agile delivery, so team dashboards inform governance rather than replacing stage control and reporting.
Topic: PRINCE2 Agile practices, roles, and their application
On a PRINCE2 Agile project, the project manager asks project support to keep the issue register and project dashboard up to date and collect checkpoint information from the agile team. The same arrangement says that, if a timebox forecast shows the planned release scope will not be met, project support should move lower-value user stories to a later release without consulting the Product Owner and should alert the project board directly if stage time tolerance may be exceeded.
Which evaluation is the most fit for purpose?
Best answer: A
Explanation: Project support is valuable in an agile context when it improves visibility and reduces administrative overhead for the project manager. However, changing release priorities is a Product Owner decision, and a possible breach of stage tolerance should be raised through the project manager rather than bypassing that role.
In PRINCE2 Agile, project support helps the project manager by providing administrative and information support that keeps governance lightweight and visible. Updating the issue register, maintaining the project dashboard, and collecting checkpoint information from the team are appropriate contributions because they support project-level control without interfering with team autonomy. The arrangement becomes unfit when project support is asked to make decisions outside its role. Moving user stories to a later release changes value and priority, so that decision belongs to the Product Owner. Likewise, a forecast breach of stage tolerance is handled through the project manager, who decides whether escalation to the project board is required. Support is appropriate; taking over authority is not.
Project support can aid visibility and administration, but reprioritizing release scope and bypassing the project manager on tolerance escalation exceed that role’s authority.
Topic: PRINCE2 Agile practices, roles, and their application
A PRINCE2 Agile project is in its first delivery stage. The Agilometer shows low agile maturity among business stakeholders, and one delivery team still waits for the project manager to make routine timebox decisions instead of self-managing. The project executive has approved coaching support. What is the best next step?
Best answer: D
Explanation: The scenario has two different needs: wider agile maturity across stakeholders and a local team performance problem. In PRINCE2 Agile, an agile coach supports broader agile adoption and behaviour change, while a team coach helps a delivery team improve self-management and day-to-day ways of working.
The key distinction is scope and purpose. An agile coach works at a broader level, helping the project manager, leaders, and stakeholders improve agile understanding, collaboration, and fit-for-purpose ways of working across the project environment. A team coach works close to a delivery team to strengthen self-management, facilitation, team dynamics, and the effective use of agile practices during delivery. Neither role replaces project governance authority or product decision accountability. In this scenario, low stakeholder agility needs broader coaching, while the team’s dependence on the project manager needs team-level coaching. Increasing management control would reduce agility, and using a product role as the coach would confuse ownership of value with coaching responsibility.
This matches the agile coach’s broader change role and the team coach’s focus on improving a specific team’s self-management and delivery practices.
Topic: PRINCE2 Agile processes and their application
During Initiating a Project, the project manager has agreed a release cadence, a common Definition of Done, and that the Chief Product Owner will prioritize the product backlog. The project will use two mature internal agile teams and one external supplier team to deliver a regulated integration. Additional information: the initiation documentation does not yet define how cross-team dependencies, impediments threatening stage tolerance, or team dashboard data will be handled at project level. Which adaptation is the MOST appropriate before authorizing controlled delivery?
Best answer: B
Explanation: Initiation has covered some key agile basics, but not enough project-level working agreements for controlled delivery in this context. With multiple teams, a supplier, and a regulated component, lightweight agreements for dependency handling, escalation, and reporting are needed before stage authorization.
In an agile context, Initiating a Project should establish enough working agreements to enable delivery while preserving control. Here, some important foundations already exist: release cadence, a common Definition of Done, and clear backlog prioritization by the Chief Product Owner. However, the missing elements are project-level interfaces needed for PRINCE2 Agile control across several teams and a supplier.
A proportionate response is to add lightweight agreements for:
This is sufficient without becoming heavy. Leaving these points undefined weakens control, while prescribing detailed team behavior or requiring board approval of user stories would over-tailor governance. The key is to define the minimum project-level agreements that allow agile teams to work flexibly within controlled boundaries.
These missing agreements are needed for project-level control, but they can be added lightly without taking away team autonomy.
Topic: PRINCE2 Agile practices, roles, and their application
A PRINCE2 Agile project has one self-managing delivery team using 2-week timeboxes. Mid-stage, an external supplier says an API used only by two Should-have stories will arrive 1 week late. The Product Owner proposes removing those stories from the current release to keep the fixed release date, and the project dashboard still shows the stage within time and cost tolerances. What should the project manager do next?
Best answer: D
Explanation: The project manager should help the Product Owner and team adapt within agreed tolerances while keeping project-level control visible. Because only Should-have scope is affected and the stage remains within time and cost tolerance, the delay should be managed as an issue and monitored rather than escalated.
In PRINCE2 Agile, the project manager enables agile delivery without taking over product decisions from the Product Owner or self-management from the team. Here, the fixed release date can still be protected by flexing lower-priority scope, and the stage is still forecast to remain within time and cost tolerances. The right response is to support the reprioritization, make sure the supplier delay is captured and visible at project level, and continue monitoring whether an exception is emerging.
Immediate escalation is the closest distractor, but it is premature when tolerances remain intact.
This supports adaptive delivery within tolerance while keeping backlog decisions with the Product Owner and reserving escalation for a forecast exception.
Topic: Agile mindset, people, project management, and organizational change management
On a PRINCE2 Agile project, a newly formed supplier team uses timeboxes, user stories, and daily stand-ups correctly. However, senior stakeholders publicly criticize any unfinished work, so developers hide impediments and wait for the project manager to assign tasks. Weekly highlight reports to the project board must continue because supplier dependency risk is high. Using the Agile Onion, which adaptation is MOST appropriate?
Best answer: B
Explanation: This is primarily a mindset problem, not a missing technique or process. The team already has agile practices in place, but public criticism is stopping transparency and self-management, so the proportionate response is coaching and safer behaviours while keeping required project-level reporting.
The Agile Onion helps diagnose whether the visible problem sits in outer layers such as techniques and processes, or in deeper layers such as behaviours and mindset. Here, the team is already using core agile ways of working: timeboxes, user stories, and stand-ups. The real problem is that people do not feel safe to expose issues, which shows a mindset problem that is driving poor behaviours.
A proportionate adaptation is to improve psychological safety through agile coaching and better stakeholder interactions, while preserving PRINCE2 Agile control. Weekly highlight reports are still needed because the project board requires project-level visibility over supplier dependency risk. Changing tools or removing reporting would not address the root cause.
The key takeaway is to fix the deepest layer causing the problem, not just the visible symptoms.
The techniques and processes are already present, so the root cause is an unsafe mindset that needs coaching without removing required governance.
Topic: PRINCE2 Agile in the wider context
A project board is reviewing whether to close a project that has delivered the first release of a new customer portal.
Exhibit: Closure pack excerpt
Current release: MVP ready for launch
Product roadmap: 3 further increments planned after project closure
Benefits note: 70% of forecast benefits depends on those later increments
Governance note: no decision recorded on who will prioritize and fund the backlog after closure
Which interpretation is MOST appropriate?
Best answer: D
Explanation: The key clue is that most forecast benefits depend on increments planned after project closure, yet no one is assigned to own backlog prioritization and funding. That creates a gap between project governance and ongoing product management expectations.
In PRINCE2 Agile, a project may deliver an initial release while product evolution continues beyond the project. The decisive clue here is not simply that an MVP is ready or that a roadmap exists; it is that 70% of the benefits depend on post-project increments and the closure pack does not define who will own backlog prioritization and funding afterward. That means project-level governance must connect with product management expectations before closure, so ongoing value decisions have clear accountability and support. The board does not need to keep the project open for all future increments, but it does need confidence that post-project product management arrangements are in place. Otherwise, the business case remains exposed after closure.
Most benefits sit beyond the project, so closure should not proceed without a defined post-project product management and funding arrangement.
Topic: PRINCE2 Agile processes and their application
A PRINCE2 Agile project uses two agile delivery teams. During Managing a stage boundary, rising integration defects mean the project manager must recommend whether the next stage should be authorized and whether any Must Have scope should move to a later release. The project board needs evidence on tolerance, risk, and release impact. The agile coach suggests using the next retrospective to make that decision. Which adaptation is most appropriate?
Best answer: D
Explanation: A retrospective is mainly a team-delivery workshop. In this scenario it should inform the project manager, but the next-stage authorization decision needs project-level evidence for the project board. The best tailoring is to keep the retrospective at team level and feed its outputs into the stage-boundary decision.
In PRINCE2 Agile, agile workshops can provide valuable input, but they do not replace the process decision point or change who has authority to decide. A retrospective helps the teams inspect causes, agree improvements, and suggest recovery actions. Here, the live decision is whether to authorize the next stage and how defects affect tolerances, risks, and Must Have delivery, which is a project-level governance matter within Managing a stage boundary.
The appropriate tailoring is to keep the retrospective focused on team learning and recovery actions, then convert its outputs into project-level evidence for the project manager’s recommendation. That evidence may include updated risk exposure, tolerance forecasts, and release impact. Using the retrospective itself as the decision forum would blur authority, while replacing it would remove a useful team-delivery mechanism.
This preserves the retrospective as a team workshop while using its findings as input to the project-level decision that belongs in Managing a stage boundary.
Topic: PRINCE2 Agile processes and their application
A project using two agile teams is finishing Stage 2. To save time, the project manager proposes skipping the stage boundary review: the Project Board will just look at the release demo and team dashboard in a chat channel, and Stage 3 will start immediately if nobody objects. No End Stage Report or Stage Plan for Stage 3 will be prepared because project tolerances are still forecast to be met.
What is the best next step?
Best answer: B
Explanation: The key clue is that a new stage will begin without the normal stage boundary control. In PRINCE2 Agile, tailoring may streamline how information is presented, but it must not remove the Project Board decision and products needed to authorize the next management stage.
This scenario signals an inappropriate tailoring decision because a necessary PRINCE2 control is being removed at the exact point where it is required. The warning sign is not the use of agile evidence; demos and dashboards are useful. The problem is the proposal to start the next stage without an End Stage Report, a Stage Plan for the next stage, and explicit Project Board authorization.
In PRINCE2 Agile, team-level information can feed project control, but it does not replace project-level governance. A release demo shows delivered capability, and a team dashboard shows short-cycle progress, but neither substitutes for the formal decision to continue into a new management stage. The right response is to keep the agile evidence and use it within the stage boundary process before Stage 3 starts. Treating ongoing visibility as enough would weaken control.
A new management stage still needs formal Project Board authorization, and agile delivery evidence should support that control rather than replace it.
Topic: Agile mindset, people, project management, and organizational change management
A local authority is running a 9-month project to launch an online permit service. At the same time, an operational service team is handling weekly permit-rule changes and frequent user complaints on the current service. The sponsor proposes one common approach for both environments: agree all requirements upfront, avoid user reviews until the full solution is ready, and batch operational improvements into quarterly releases to “protect efficiency”. Which evaluation is MOST appropriate?
Best answer: B
Explanation: The approach is not fit for purpose because it removes the feedback loops needed when needs and priorities are changing. In both the project and the operational service, shorter increments would support learning, responsiveness, and earlier value delivery.
Agile is needed when uncertainty, evolving needs, or changing priorities make delayed feedback risky. Here, weekly rule changes and frequent complaints show that both the temporary project and the ongoing operational service need to inspect, learn, and adapt regularly. Locking requirements upfront, delaying user reviews, and batching improvements into large releases may feel efficient, but they reduce responsiveness and increase the chance of delivering the wrong outcomes. An agile mindset would favor shorter feedback cycles, earlier validation, and incremental value delivery while still keeping appropriate control. That matters in projects and non-project environments alike when users, regulations, or priorities can shift quickly. Predictability is useful, but not when it is achieved by ignoring real feedback.
Frequent rule changes and user complaints show that both the project and operational environment need responsiveness, feedback, learning, and earlier value delivery.
Topic: Agile mindset, people, project management, and organizational change management
A PRINCE2 Agile project is starting a 12-week stage to deliver an online licensing service. The proposed delivery team has analysts from one supplier, developers from another, and a tester available only one day a week from operations. The Product Owner and project manager are both sending priority requests to developers, and a recent pilot showed slow hand-offs and low trust between functions. What is the best action for the project manager now?
Best answer: A
Explanation: The scenario shows weak team composition, thin capability, and unclear priority ownership. Building a stable cross-functional team with dedicated testing and one clear source of delivery priorities is the best way to improve collaboration and flow without weakening PRINCE2 Agile control.
When building an agile team, the key considerations are capability, collaboration, role clarity, and team composition. Here, work is split across functions and suppliers, testing is not sufficiently embedded, and the team receives competing priority instructions. A stable cross-functional team reduces hand-offs, improves shared ownership, and makes it easier to complete work end-to-end. Adding dedicated testing closes a clear capability gap. Clarifying that delivery priorities come through the Product Owner removes confusion, while the project manager still retains project-level planning, reporting, and control.
More reporting or tighter external direction may increase visibility, but they do not fix the underlying team design problem. The best response is to improve the team structure and working relationships, not to add extra coordination layers.
This best improves capability, collaboration, and role clarity while keeping the project manager focused on project-level control rather than daily direction.
Topic: PRINCE2 Agile processes and their application
A project manager is tailoring Managing product delivery for an experienced agile team working in two-week timeboxes. The team wants freedom to change how stories are implemented during a work package, but the project board still needs clear product acceptance and weekly progress reporting. Which adaptation is most appropriate?
Best answer: C
Explanation: Managing product delivery should be tailored by defining the required products, acceptance, and reporting boundaries without controlling day-to-day delivery choices. An outcome-based work package supported by checkpoint reporting preserves PRINCE2 Agile governance while allowing the team to learn and adapt within the timebox.
In PRINCE2 Agile, the work package is the main control for agreeing what is to be delivered, how acceptance will be judged, and what reporting the project manager needs. Tailoring should protect team autonomy over how stories and tasks are completed, while still keeping project-level visibility and value protection.
Here, the balanced adaptation is to define the outcomes and acceptance criteria up front and keep a regular checkpoint reporting cadence, using team-level dashboard information as evidence. That gives the project manager reliable progress information without turning self-management into task supervision. It also prevents acceptance from becoming vague or delayed until too late.
The key distinction is between controlling delivery boundaries and controlling the team’s detailed work.
This keeps acceptance and reporting explicit at work-package level while leaving delivery decisions with the self-organizing team.
Topic: PRINCE2 Agile processes and their application
A project manager is controlling a stage delivered by two mature agile teams. There is no separate team manager role, and the project board wants reliable evidence that the stage remains within tolerances without adding detailed task reporting. Which adaptation is the MOST appropriate?
Best answer: D
Explanation: The best adaptation is to use existing agile collaborative evidence for stage control. Review workshop outputs and team dashboards provide current progress, forecast, and impediment information that can be summarized into checkpoint evidence without creating heavy task-level reporting.
The purpose of Controlling a Stage is ongoing monitoring and corrective action within agreed tolerances. In an agile context, tailoring should preserve that control while using existing team practices wherever possible. For mature teams, outputs from review workshops and team dashboards are strong collaborative evidence because they show current delivery status, likely completion, and emerging blockers. Converting that evidence into a lightweight checkpoint cadence gives the project manager enough information for project-level reporting and timely intervention if tolerances are threatened.
The key is to adapt reporting effort, not remove the control needed to manage the stage.
This reuses agile workshop outputs and artifact evidence to support ongoing stage-level control without undermining team self-management.
Topic: PRINCE2 Agile processes and their application
A PRINCE2 Agile project with two delivery teams is nearing the end of Stage 2. A supplier delay means three high-value stories must move to a later release, although stage tolerance is still forecast to be met. The Project Board will decide tomorrow whether to authorize Stage 3. Team dashboards show velocity and flow, but they do not show the revised release path or value impact. What should the project manager do?
Best answer: C
Explanation: A stage-boundary decision needs project-level evidence about the next stage, not only team delivery data. Updating the release map and project backlog through a collaborative workshop gives the project manager the right evidence to support the end stage report and next stage planning while keeping agile reprioritization visible.
Managing a stage boundary is about giving the Project Board enough evidence to review the current stage and decide whether to authorize the next one. In an agile context, if release content changes but project tolerance is still expected to be met, the project manager should turn team-level delivery information into project-level planning evidence.
A release-planning workshop helps key roles agree the revised sequencing, dependencies, and value path. Its outputs, especially an updated release map and project backlog, can then support the end stage report and the next stage plan. Team dashboards and burn data are useful inputs, but on their own they show short-cycle delivery activity rather than the project-level implications needed for a stage-boundary decision. The key is to provide collaborative evidence that supports governance without losing agility.
This creates project-level collaborative evidence of revised value, sequencing, and dependencies for the end stage report and next stage plan.
Topic: PRINCE2 Agile practices, roles, and their application
A PRINCE2 Agile project is nearing the end of a stage. The delivery team uses automated tests and a team dashboard, and several user stories are marked done. Before the project manager recommends release of a customer portal increment, Project Assurance asks for project-level evidence that mandatory security, accessibility, and user-acceptance checks for the key products have been planned and completed. Which TWO uses of the quality register are appropriate? Select TWO
Best answer: A
Explanation: In PRINCE2 Agile, the quality register gives project-level visibility of planned and completed quality activities for products. Here, it should record the mandated checks and help the project manager and Project Assurance judge whether enough quality evidence exists to recommend the release.
In PRINCE2 Agile, the quality register is not a substitute for team-level boards or detailed test tools. Its purpose is to give the project manager and assurance roles a concise, project-level view of the quality activities that matter for control and decision-making. In this scenario, the release decision depends on evidence that mandatory checks for key products were planned and completed.
Detailed test-case execution belongs in team tools, and MoSCoW reprioritization belongs in backlog management. The closest trap is treating the quality register as a team dashboard, which uses the wrong level of detail.
The quality register is the project-level record of planned and completed quality activities and their outcomes.
Topic: PRINCE2 Agile practices, roles, and their application
A project is delivering a new citizen portal using two agile teams. Mid-stage, a compliance date is brought forward by six weeks, several business areas disagree on release priorities, and the project manager forecasts stage tolerance may be exceeded unless a decision is made within 48 hours. The project executive proposes to bring the key business stakeholders and the Chief Product Owner together immediately, confirm which features are essential to maintain the business case, use executive authority to resolve a cross-department legal dependency, and leave detailed user story ordering to the Product Owners and teams.
How should this approach be evaluated?
Best answer: B
Explanation: The approach is appropriate because the project executive is protecting the business case, making a timely escalated business decision, and using authority to remove an organizational blocker. It also preserves agile working by leaving detailed backlog sequencing to the Chief Product Owner, Product Owners, and teams.
In PRINCE2 Agile, the project executive provides business leadership and remains accountable for continued business justification. Here, the project manager has raised a likely tolerance problem and the project needs a fast decision on business priorities plus help with an external dependency. The proposed response is fit for purpose because it keeps the project executive focused on project-level direction rather than team-level control.
Detailed user story ordering and day-to-day backlog decisions should stay with the Chief Product Owner, Product Owners, and delivery teams. The key distinction is between enabling agile delivery and micromanaging it.
This is correct because the project executive is acting at the right governance level while supporting rapid agile delivery.
Topic: PRINCE2 Agile processes and their application
A retailer is starting a project to launch a digital returns service using two mature agile teams. The Project Executive wants the Starting up a project process completed quickly, but the project board still needs enough information and the right governance to decide whether to authorize initiation. The project manager proposes the following tailoring decisions. Which TWO are fit for purpose in this agile context? Select TWO.
Best answer: B
Explanation: Effective tailoring of Starting up a project makes the work lighter and more collaborative without removing core PRINCE2 Agile controls. A startup workshop and a project canvas are both suitable ways to support fast alignment, but initiation approval and early governance basics must still stay in place.
Starting up a project should provide just enough information, structure, and role clarity to decide whether initiation is worthwhile. In an agile context, this is often tailored by using collaborative workshops and lightweight artifacts rather than heavy upfront documentation. A focused startup workshop helps key people align quickly on the vision, approach, responsibilities, and high-level priorities. A project canvas can summarize essential information and support the outline business case and project brief without forcing detailed requirements too early.
What should not be tailored away are governance decisions and readiness activities. Authorizing initiation remains a project board decision, not a product role decision. Reviewing previous lessons and clarifying roles are also important during startup because they shape how the project will be tailored from the outset. Agile tailoring means lighter and faster, not less controlled.
A collaborative startup workshop is a proportionate way to create shared understanding quickly while informing the project brief.
Topic: PRINCE2 Agile practices, roles, and their application
On a PRINCE2 Agile project, one delivery team works in two-week timeboxes. At the stage-end review, the project manager reports only the team plan, task board, and burn chart. A fixed regulatory release date applies, but there is no release map or project backlog showing how approved changes affect stage outcomes. Which TWO observations correctly indicate that team-level planning has been confused with project-level planning? Select TWO.
Best answer: A
Explanation: Team-level planning artifacts help the team manage short-cycle delivery, but they do not replace project-level planning. In this scenario, the real clues are the reliance on timebox detail for a stage decision and the absence of a release or project-level backlog view.
In PRINCE2 Agile, planning must be clear at different levels. Team-level planning is short term and detailed, such as task breakdowns, timebox plans, and burn charts. Project-level planning must show how work supports stage outcomes, release timing, and tolerances.
Here, the project manager is using only team delivery artifacts at a stage-end review. That is a warning sign, because the Project Board needs evidence about stage viability and the fixed regulatory release date, not just local team activity. The lack of a release map or project backlog is a second clear clue, because approved changes cannot be judged against stage outcomes at project level.
By contrast, story task breakdown and product backlog refinement are normal team planning activities; the problem is the missing project-level view.
Stage-end decisions need project-level planning evidence, not only team-level timebox data.
Topic: PRINCE2 Agile practices, roles, and their application
A project is delivering a citizen portal through two agile teams: one Scrum team and one Kanban supplier team. Both teams are experienced and already use effective team-level acceptance checks. The project manager needs stage-level evidence that mandatory accessibility and security requirements will be met. How should the quality management approach be tailored?
Best answer: C
Explanation: The quality management approach should provide project-level quality control, responsibilities, and evidence, not duplicate all team-level practices. In this scenario, it should align the teams’ agile definitions and product descriptions to mandatory standards so the project manager can see reliable stage-level quality evidence.
In PRINCE2 Agile, the quality management approach is tailored to show how quality will be controlled and evidenced at project level while still enabling agile delivery. Here, the project has two different teams and mandatory accessibility and security requirements, so the approach must define common standards, responsibilities, approval points, and the evidence needed for governance.
The best adaptation is to connect project-level quality expectations to team-level working practices such as Definition of Ready, Definition of Done, and product descriptions, then capture planned and completed quality activity in the quality register. That gives the project manager stage-level visibility without forcing both teams into the same detailed way of working.
Removing the approach weakens governance, while imposing one identical checklist over-tailors delivery. Delaying confirmation until the end of the stage gives quality evidence too late.
This preserves project-level quality control and evidence while allowing each team to work with fit-for-purpose agile quality practices.
Topic: Agile mindset, people, project management, and organizational change management
Two agile teams on a PRINCE2 Agile project share security, operations, and legal specialists. Delivery is slowing because these specialists still work through separate functional queues and join reviews late. Each team coach has improved collaboration inside their own team, but the barrier remains across teams and stakeholders. The project manager wants leadership support without taking over product decisions. Which action best fits the responsibility boundary?
Best answer: C
Explanation: The barrier exists across multiple teams, stakeholders, and functional groups, so it is beyond the scope of a single team coach. Using the agile coach is the best leadership support because that role helps remove wider collaboration impediments while leaving product decisions with the business.
In PRINCE2 Agile, leadership support for collaboration should be applied at the level where the barrier actually sits. Here, the problem is not a team-only practice issue; it is an organizational collaboration problem caused by functional silos and late involvement from shared specialists across more than one team. The agile coach is best placed to help teams, stakeholders, and functional managers agree better ways of working and remove impediments that cut across boundaries. A team coach focuses on helping one team improve. The Chief Product Owner should concentrate on product direction and priorities across teams, not define daily collaboration rules. The Project Executive provides governance and business leadership, but should not manage detailed delivery interactions. The key is to remove the barrier without confusing coaching, product ownership, and governance responsibilities.
The agile coach works across teams and the wider organization to remove collaboration impediments while product decisions stay with business ownership.
Topic: Agile mindset, people, project management, and organizational change management
A PRINCE2 Agile delivery team already uses a product backlog, timeboxes, daily stand-ups, and burn charts. Team members say they understand agile values and want rapid feedback, but in stand-ups they report only to the project manager, wait for work to be assigned, and rarely help each other remove blockers. The stage is within tolerance. What is the best next step?
Best answer: D
Explanation: The team already has agile processes and techniques in place, and the stem says it understands agile values. The visible problem is how people are acting day to day, so the best response is to coach better collaboration and self-management at the behaviour layer of the Agile Onion.
The Agile Onion helps diagnose where a problem sits: mindset, behaviours, techniques, or processes. In this scenario, the outer layers are already present because the team is using a product backlog, timeboxes, stand-ups, and burn charts. The stem also says the team understands agile values, so the main gap is not knowledge of mindset. The weakness is behavioural: reporting upward instead of collaborating sideways, waiting for assignment, and not resolving blockers together.
A proportionate response is to use the team coach to improve working agreements, team interaction, and psychological safety so the team behaves in a more self-managing way. Adding new techniques or extra controls would treat the symptoms and could reinforce the command-and-control pattern already causing the problem. The key is to intervene at the layer showing the real gap.
The gap is mainly in the behaviour layer, so coaching team interaction is more proportionate than changing techniques or adding process.
Topic: Agile mindset, people, project management, and organizational change management
A PRINCE2 Agile project is in delivery stage for a customer portal. One agile team has an experienced team coach. The project manager reviews this retrospective note after tension between developers and the tester.
Exhibit: Retrospective note
- 2 stories were marked done before agreed testing finished
- Tester: "I stopped raising concerns in stand-ups because I get blamed"
- Developers: "Defects are discussed as personal failures"
- The timebox objective is still achievable
Which response best maintains psychological safety and accountability?
Best answer: A
Explanation: The best response is a blame-free, team-level intervention led by the team coach, with agreed corrective actions made visible. This protects psychological safety because people can raise concerns without personal attack, and it keeps accountability because Definition of Done, action owners, and the timebox objective remain transparent.
Psychological safety in PRINCE2 Agile means people can surface problems early without fear, while accountability keeps commitments, quality criteria, and delivery goals visible. Here, stories were marked done without agreed testing and the tester has stopped speaking up, so the immediate need is to restore safe challenge inside the team, not to increase blame or remove direct communication. Because the timebox objective is still achievable, a proportionate response is for the team coach to facilitate a blame-free discussion, re-confirm agreed team behaviours and the Definition of Done, and make corrective actions with owners visible on the team dashboard. That keeps transparency and focus on the objective while preserving team trust. Public blame or premature escalation would hide problems rather than solve them.
The team coach can restore safe communication while making quality expectations and corrective actions visible, so accountability supports the timebox objective instead of blame.
Topic: PRINCE2 Agile practices, roles, and their application
During initiation of a PRINCE2 Agile project with two product teams, the project manager has tailored the project management team structure into a short responsibilities note. It is intended to make agile delivery decision rights clear.
Exhibit: Responsibilities note
Chief Product Owner: answers daily story queries and accepts completed
stories for each team.
Product Owner: sets overall product direction, decides release priorities,
and resolves cross-team priority conflicts.
Project manager: manages stage tolerances and escalates forecast
exceptions.
Team coach: facilitates team events and supports self-management.
Which judgment is most appropriate?
Best answer: D
Explanation: A short responsibilities note can be a good tailoring of the Organization practice, but only if decision boundaries are clear. Here, the exhibit reverses the Chief Product Owner and Product Owner responsibilities, so it is not sufficient for agile delivery across two teams.
In PRINCE2 Agile, tailored role descriptions are acceptable if they still make authority and responsibilities clear enough for governance and delivery. On a project with multiple teams, the Chief Product Owner is the project-level role that sets overall product direction, decides release priorities, and resolves cross-team priority conflicts. The Product Owner works closely with an individual team to clarify stories and accept completed work.
The exhibit reverses those two roles. That creates confusion about who makes cross-team product decisions and who supports day-to-day team delivery, which means the artifact is not fit for purpose even though the project manager and team coach lines are broadly clear.
Brevity is fine; unclear decision rights are not.
It swaps the project-level Chief Product Owner role with the team-facing Product Owner role, so key agile delivery decisions are unclear.
Use this flow when a scenario asks which agile practice, control, or tailoring choice fits the case. Practitioner questions usually reward balancing governance, delivery flexibility, risk, and stakeholder confidence.
flowchart LR
A["Project context and constraints"] --> B["PRINCE2 control needs"]
B --> C["Agile suitability and team capability"]
C --> D["Tailored practice choice"]
D --> E["Tolerance, prioritization, and feedback"]
E --> F["Scenario-based decision"]
| Concept | Practitioner use |
|---|---|
| Tailoring decision | Select practices because they fit the scenario, not because they are fashionable. |
| Control balance | Preserve business justification, roles, tolerances, and quality expectations. |
| Agile suitability | Consider uncertainty, team capability, stakeholder access, and risk. |
| Prioritization tradeoff | Use priorities to protect essential value when constraints are fixed. |
| Scenario evidence | Apply the method to facts such as governance pressure, supplier constraints, or team maturity. |
Use this live PRINCE2 Agile Practitioner V2 page for web and app access, public sample questions, timed mocks, topic drills, plans, and related PM Mastery exam links.
| If you need to practice… | Best page | Why |
|---|---|---|
| classic applied PRINCE2 scenarios | PRINCE2 Practitioner | Best live route for longer governance and tailoring scenarios in the PRINCE2 family. |
| PRINCE2 method fundamentals | PRINCE2 Foundation | Best live route if your core PRINCE2 model still needs work before the agile variant. |
| agile and hybrid delivery decisions | PMI-ACP | Best live route when the real need is cross-framework agile judgment. |
| If you are deciding between… | Main distinction |
|---|---|
| PRINCE2 Agile Foundation Version 2 vs Practitioner Version 2 | Foundation is concept-first; Practitioner is scenario-heavy application. |
| PRINCE2 Agile Practitioner Version 2 vs PRINCE2 Practitioner | PRINCE2 Agile Practitioner keeps agile delivery context; PRINCE2 Practitioner stays inside the classic method. |
| PRINCE2 Agile Practitioner Version 2 vs Leading SAFe | PRINCE2 Agile Practitioner is project-level governance plus agility; Leading SAFe is enterprise agility and ART coordination. |
| Timing | Practice focus | What to review after the set |
|---|---|---|
| Days 7-5 | One 50-question diagnostic plus drills in the weakest applied areas | Whether misses came from tailoring, prioritization, tolerance, agile suitability, or scenario reading |
| Days 4-3 | Mixed practitioner scenarios | Whether you can point to the case fact that makes the best answer proportionate |
| Days 2-1 | Light review of fix-and-flex, tolerances, agile suitability, governance roles, and feedback loops | Only recurring traps; avoid starting new agile frameworks late |
| Exam day | Short warm-up if useful | Choose the answer that is controlled enough for PRINCE2 and adaptive enough for the project |
If you can score above 75% on several unseen scenario sets and explain the tailoring logic behind misses, you are likely ready. Repeating the same bank until the case facts feel familiar can weaken the scenario-reading skill this route requires.