PRINCE2 PRINCE2-Agile-Foundation - PRINCE2 Agile Foundation (Version 2) Exam

Agile workshops are collaborative sessions used throughout the project to address various aspects such as problem-solving, release planning, team alignment, and continuous improvement. Workshops encourage open communication, collective decision-making, and foster a shared understanding of goals and challenges.

Unlike a delegation matrix, which defines roles and authorities, or the project log, which records issues and risks, workshops are interactive events that enable timely resolution of challenges. The Agilometer is a diagnostic tool assessing agility maturity but not a problem-solving forum.

Agile workshops embody the agile principle of collaboration and adaptability, enabling teams to respond quickly to issues and refine plans collectively.

Agile Foundation guidance describes the project canvas as a living, lightweight artifact that supports alignment, transparency, and ongoing benefit realization throughout the project lifecycle. It should not be treated as a one-time planning document. The correct point at which the project canvas should be both updated and used to assess whether intended benefits have been or will be realized is at the end of each delivery stage, making option C the correct answer.

Agile and PRINCE2 Agile approaches emphasize incremental delivery and continuous validation of value. Each delivery stage produces usable outputs or increments that can be reviewed against expected outcomes and benefits. Updating the project canvas at the end of each delivery stage allows the team and stakeholders to reflect on what has actually been delivered, what has changed, and whether assumptions made earlier are still valid. This includes reassessing benefits, risks, stakeholders, and priorities based on real evidence rather than predictions.

Option A, the end of the pre-project stage, is too early, as no meaningful delivery has occurred to assess benefits. Option B, the end of initiation, focuses on planning and setup rather than value realization. Option D, the end of the final delivery stage, is too late because it limits opportunities to adapt if benefits are not being realized as expected.

Agile Foundation documents stress the importance of frequent inspection and adaptation. By reviewing and updating the project canvas at the end of each delivery stage, teams can make informed decisions about continuing, pivoting, or stopping work. This supports effective governance while preserving agility. Regular benefit assessment ensures that the project remains aligned with business objectives and continues to justify investment, reinforcing Agile’s focus on value delivery rather than simply completing planned activities.

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.

The Agilometer is a diagnostic tool used within PRINCE2 Agile to assess the agility maturity and identify risks associated with adopting or operating in an iterative and agile environment. It helps teams and organizations evaluate their current agile capabilities, cultural readiness, and potential challenges that may impact project delivery.

The Agilometer highlights risk areas such as resistance to change, lack of agile skills, unclear roles, or insufficient governance adaptation. By providing a structured assessment, it enables proactive risk management and targeted improvements to reduce uncertainties inherent in iterative approaches.

Other artifacts like the project backlog (A) track requirements, the risk management approach (C) defines the method of managing risks but does not specifically identify iterative risks, and the Definition of Done (D) clarifies completion criteria rather than risks.

The Agilometer supports continuous improvement and risk mitigation aligned with PRINCE2’s risk and quality practices, ensuring agile projects remain viable and controlled.