PRINCE2 Updated PRINCE2-Agile-Foundation Exam Questions and Answers by marlowe

The Agile Enablement Workshop provides a collaborative environment where teams and stakeholders define critical agile artifacts, including the Definition of Ready. This definition specifies the criteria a user story or product backlog item must meet before work can begin, ensuring clarity and readiness.

The workshop facilitates alignment on quality standards, scope, and expectations, reducing ambiguity and improving flow through development cycles. By involving all key participants, the Definition of Ready is meaningful and practical, tailored to the project's specific context.

While starting up (A), kickoff (B), and initiation workshops (C) focus on project foundation and planning, they do not specifically focus on agile readiness criteria.

This workshop is essential for embedding agile practices within PRINCE2 governance and fostering effective delivery.

The Manage by Exception principle empowers individuals and teams by delegating decision-making within defined tolerances. It ensures governance is efficient by allowing project managers and teams to operate independently within agreed limits, escalating only when exceptions occur. This approach promotes self-management, autonomy, and accountability, which are key to agility, while maintaining control through governance boundaries.

The other principles focus on different aspects: business justification relates to ongoing viability, tailoring adapts the method, and focusing on products emphasizes deliverables but do not specifically address empowerment through governance.

Agile Foundation guidance, aligned with PRINCE2 Agile, explains that the Definition of Ready (DoR) and Definition of Done (DoD) should be agreed as early as possible to establish clear expectations around quality, readiness, and completion. The workshop to agree both DoR and DoD is conducted during the Initiating a Project process, making option A the correct answer.

The Initiating a Project process is where the foundations for successful delivery are set. Its purpose is to ensure that there is a shared understanding of how the project will be delivered, governed, and controlled before significant work begins. Agreeing the DoR and DoD at this stage provides clarity on what “ready to start” and “done” actually mean for the project. This helps align stakeholders, delivery teams, and governance roles on quality expectations and acceptance standards.

Option B, Directing a Project, focuses on senior-level decision-making, authorization, and overall control rather than detailed delivery agreements. Option C, Controlling a Stage, deals with monitoring progress and handling issues during execution, not defining core quality agreements. Option D, Managing Product Delivery, concentrates on coordinating work between the team and project management but assumes that definitions such as DoR and DoD are already established.

Agile Foundation documents emphasize that DoR and DoD support transparency, consistency, and trust. The DoR ensures that work entering a delivery cycle is sufficiently understood and prepared, reducing waste and rework. The DoD ensures that completed work meets agreed quality criteria and is potentially releasable. Establishing these definitions during Initiating a Project supports Agile principles of built-in quality and shared understanding, while also satisfying governance needs. By agreeing them early, teams can work autonomously within clear boundaries, improving flow, predictability, and value delivery throughout the project.