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.

Within Agile Foundation guidance and PRINCE2 Agile alignment, the Definition of Done (DoD) plays a critical role in supporting an iterative approach to delivery, making option C the correct answer. PRINCE2 Agile combines the governance strengths of PRINCE2 with the flexibility of Agile delivery, and iteration is central to how value is delivered incrementally. The DoD provides a shared and consistent understanding of what it means for work to be complete at the end of each iteration.
The iterative approach in PRINCE2 Agile relies on delivering small, usable increments frequently. The Definition of Done ensures that every increment meets agreed quality standards before it is considered complete. This supports transparency, predictability, and trust, which are essential for iterative delivery. Without a clear DoD, teams risk producing partially finished work that cannot be reviewed, tested, or released, undermining the benefits of iteration.
Option A is incorrect because Agile and PRINCE2 Agile emphasize continuous feedback as a core mechanism for learning and adaptation. Option B, offering predictive insights, is not a defining element of PRINCE2 Agile's iterative approach; Agile focuses more on empirical feedback than prediction. Option D is also incorrect because frequent testing is encouraged, not reduced, in iterative Agile delivery.
Agile Foundation documents emphasize that the DoD acts as a quality gate that supports incremental progress while maintaining control. It aligns delivery teams and stakeholders on expectations and ensures that each iteration produces a potentially usable output. In PRINCE2 Agile, this alignment allows teams to work autonomously within defined tolerances while still meeting governance and assurance requirements. By clearly defining what "done" means, the DoD strengthens the iterative cycle of build, review, learn, and adapt, which is fundamental to Agile and PRINCE2 Agile working together.

The concept of "being Agile" rather than merely "doing Agile" is a central theme in Agile Foundation guidance. "Being Agile" refers to adopting the Agile mindset, values, and principles as a way of thinking and behaving, rather than simply applying a set of tools, ceremonies, or techniques. This mindset emphasizes adaptability, collaboration, continuous learning, and responsiveness to change, which is best represented by option B.
Agile foundations clearly distinguish mindset from mechanics. While timelines, documentation, and techniques have their place, they are secondary to people, interactions, and the ability to respond effectively to changing circumstances. Adaptability means welcoming change, even late in development, when it improves value for customers and stakeholders. Collaboration emphasizes close, ongoing cooperation between cross-functional team members, business representatives, and customers, ensuring shared understanding and faster decision-making.
Option A focuses on strict timelines and task completion, which aligns more closely with traditional predictive or plan-driven approaches. Agile recognizes that rigid timelines can reduce flexibility and discourage learning. Option C emphasizes document-driven processes, which contradict the Agile value of prioritizing working solutions over comprehensive documentation. Documentation is useful, but it should support value delivery, not dominate it. Option D highlights Agile techniques for efficiency, which reflects "doing Agile" rather than "being Agile." Techniques such as stand-ups, boards, or retrospectives only create value when guided by an Agile mindset.
In Agile foundations, "being Agile" enables teams to continuously inspect and adapt their ways of working, improve relationships, and deliver meaningful outcomes. By focusing on adaptability and collaboration, organizations create environments where teams can respond effectively to uncertainty, learn from feedback, and consistently deliver value, which is the true intent of Agile.

In Agile Foundation guidance, the team coach plays a key role in supporting one or more Agile teams in adopting and improving Agile ways of working. A core responsibility of the team coach is to liaise with the agile coach, making option A the correct answer. This relationship ensures alignment between team-level coaching and organization-wide Agile adoption.
The team coach focuses primarily on the day-to-day effectiveness of the team. This includes helping the team understand Agile principles, improve collaboration, enhance communication, and continuously improve their ways of working. The agile coach, on the other hand, typically operates at a broader level, supporting multiple teams, leaders, and the organization as a whole in embedding Agile culture and practices. By liaising with the agile coach, the team coach ensures that insights, challenges, and progress at the team level are shared and addressed consistently across the organization.
Option B, liaising with the project manager, is not a primary responsibility of the team coach in Agile foundations. While coordination may occur, Agile reduces dependency on traditional command-and-control roles. Option C, liaising with the chief product owner, is also not central to the team coach role, as product ownership focuses on value and prioritization rather than team dynamics and Agile maturity. Option D, liaising with project assurance, aligns more with governance and compliance functions rather than coaching responsibilities.
Agile Foundation documents emphasize that effective coaching relies on collaboration between coaching roles. The team coach provides detailed, practical feedback from the team, while the agile coach offers strategic direction, consistency, and organizational support. This collaboration strengthens Agile adoption, helps remove systemic impediments, and ensures that teams are supported both locally and at scale. By liaising with the agile coach, the team coach helps create a coherent, sustainable Agile environment focused on continuous improvement and value delivery.