PRINCE2 Agile Practitioner Practice Questions

The Definition of 'Ready' (DoR) is a checklist of criteria that a user story must meet before it can be considered ready for the team to take into a sprint. This typically includes things like being clear, testable, and having acceptance criteria defined. Implementing a DoR ensures that stories are well-formed and understood before work begins, directly addressing the problem of ambiguity and rework.

Setting scope tolerance allows the delivery team a degree of flexibility. It empowers them to make decisions at the detail level, such as swapping out one feature for another of similar value and effort, as long as it doesn't breach the overall goals for the release or stage. This reduces bureaucracy and speeds up decision-making, which is a key goal of blending PRINCE2 with agile. It is a core part of how change is managed dynamically at the delivery level.

Lean Startup is based on validated learning and testing hypotheses, often via an MVP. The PRINCE2 principle of 'continued business justification' must still be met. The appropriate tailoring is to create a business case that reflects this uncertainty. It should be high-level, focusing on the overall vision and the value proposition, but framing the initial work as a series of experiments to validate assumptions. The business case then evolves as learning occurs, which is a perfect blend of the two approaches.

A key responsibility of the Scrum Master (and therefore the Team Manager in this context) is to remove impediments that are blocking the team's progress. Since this is an internal team issue that has persisted, the Team Manager's role is not to solve it for them, but to act as a servant-leader and facilitate the necessary collaboration to get it resolved quickly. This should happen immediately after the stand-up to avoid derailing the meeting itself.

A core purpose of a retrospective is for the team to inspect its own process and identify actionable improvements for the next work cycle. This directly supports the PRINCE2 principle of 'learn from experience' and the agile value of continuous improvement.

The retrospective should be a blame-free event where the team can openly and honestly discuss challenges and successes. Creating this psychological safety is essential for meaningful reflection and genuine process improvement.

Collaboration is the most effective behavior to foster here. The issue is a systemic one involving the product owner's availability, which is a key stakeholder interface. Actively collaborating with the product owner and their functional manager to agree on dedicated time addresses the root cause of the decision-making bottleneck. While transparency and self-organization are important, they do not resolve the fundamental resource conflict. Exploration is not the primary behavior needed to solve this problem.

In a typical PRINCE2 Agile project with a fixed deadline (Time) and budget (Cost), Scope and Benefits are the primary targets that are flexed. This allows the project to deliver the most valuable features (MoSCoW prioritization) within the fixed constraints, ensuring a viable product is delivered on time and on budget even if not all originally conceived features are included.

In a typical PRINCE2 Agile project with a fixed deadline (Time) and budget (Cost), Scope and Benefits are the primary targets that are flexed. This allows the project to deliver the most valuable features (MoSCoW prioritization) within the fixed constraints, ensuring a viable product is delivered on time and on budget even if not all originally conceived features are included.

A low Agilometer score for communication highlights a significant risk. The most appropriate and pragmatic response is to formally address it in the communication management approach within the PID. Investing in tools that facilitate face-to-face (video) interaction and defining core hours for synchronous collaboration directly mitigates the risk of poor communication in a distributed team. Email stand-ups are a poor substitute for rich communication. Full co-location is often prohibitively expensive and impractical. Simply accepting the risk ignores the Agilometer's purpose.

False. While agile events like sprint reviews and release planning provide vital input and can make the 'Managing a Stage Boundary' process much leaner, they do not completely replace it. The PRINCE2 process ensures governance by requiring the project manager to report stage performance, update the business case and project plan, and create a plan for the next stage for the project board to formally authorize continued work. These governance activities go beyond the scope of typical agile team-level ceremonies.

The 'Focus on Products' principle is about understanding and defining what needs to be delivered, including the quality criteria. In a Scrum context, the Definition of Done (DoD) is the key mechanism for ensuring quality. By incorporating the mandatory government standards into the DoD, the project manager ensures that every product increment delivered by the team meets these essential, non-negotiable quality criteria, thereby correctly applying the principle in an agile way.