The Risk practice is specifically aimed at controlling uncertainties that could impact the achievement of the project’s objectives. In PRINCE2 Agile, risk management involves identifying, assessing, and controlling threats and opportunities to reduce negative impacts and maximize positive outcomes.

Effective risk management is a core theme and practice in PRINCE2 Agile and is crucial for agile environments where change and uncertainty are inherent. The practice ensures that risks are continuously monitored and appropriate responses are planned and implemented. This proactive management helps keep the project viable and aligned with business justification.

While plans support managing scope and resources, issues deal with current problems rather than potential future events, and quality ensures that products meet requirements, risk management uniquely focuses on uncertainty.

The PRINCE2 Agile guidance emphasizes integrating agile techniques such as frequent reviews and retrospectives to improve risk awareness and control.

The Release Planning Workshop is the forum where planning for the next stage occurs in PRINCE2 Agile. This workshop brings together the project management team and delivery teams to plan the scope, schedule, and resources for the upcoming release or stage. It helps align business priorities with delivery capacity and supports incremental and iterative delivery approaches.

The Team Planning Workshop focuses on more detailed planning at the team level within the release, the Team Retrospective Workshop is dedicated to reflecting on performance and improving processes, and the Progress Review Workshop is for reviewing progress against the plan rather than planning future work.

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.