Agile Foundation guidance identifies the Agilometer assessment as a key tool used to assess risks associated with Agile adoption, making option C the correct answer. The Agilometer is specifically designed to evaluate how suitable Agile approaches are for a particular project, team, or organizational context before or during adoption. It helps organizations understand the level of risk involved in applying Agile and highlights areas that may need additional support, tailoring, or controls.
The Agilometer works by assessing several dimensions related to Agile readiness, such as stakeholder engagement, organizational culture, team capability, leadership support, and delivery environment. By scoring these factors, it provides a structured and transparent view of potential risks and constraints. This allows decision-makers to identify where Agile is likely to succeed easily and where challenges may arise, enabling proactive risk management rather than reactive problem-solving.
Option A, an enterprise agility assessment, focuses on overall organizational maturity and long-term transformation rather than project-level or adoption-specific risks. Option B, a project dashboard, is used for tracking progress, metrics, and status, not for assessing suitability or adoption risk. Option D, a cumulative risk burn-down chart, may be used to visualize risk reduction over time, but it does not assess whether Agile adoption itself is appropriate or risky in a given context.
Agile Foundation documents emphasize that Agile is not a one-size-fits-all solution. The Agilometer supports informed decision-making by encouraging thoughtful consideration of constraints, governance needs, and cultural readiness. By identifying adoption risks early, organizations can tailor Agile practices, apply hybrid approaches where necessary, and set realistic expectations. This structured assessment helps protect value delivery while maintaining the flexibility and responsiveness that Agile aims to provide.

The Progress Review Workshop is the key forum to assess the current status of the project and address challenges or issues affecting progress. It typically involves reviewing the current stage or release against plan, assessing risks, issues, and dependencies, and agreeing on corrective actions or decisions to keep the project on track.
While retrospectives (B and C) focus on reflecting and improving team practices, and team planning (A) looks ahead to upcoming work, progress reviews are focused on monitoring, control, and decision-making at the project or stage level.
This workshop aligns with PRINCE2’s principle of manage by exception, enabling timely interventions without unnecessary escalation.

Agile Foundation guidance recognizes that a smooth and effective handover to operations depends on providing clear, relevant, and usable information about what has been built and how it works. Documentation on functionality is therefore the key factor that ensures the operations team has a clear understanding of deliverables during the handover process, making option C the correct answer.
Although Agile values working solutions over comprehensive documentation, it does not eliminate documentation altogether. Instead, Agile promotes “just enough” documentation that is fit for purpose. During handover, operations teams need to understand system behavior, features, configurations, limitations, and operational requirements. Functional documentation provides this clarity by explaining what the product does, how it should be used, and how it behaves under normal and exceptional conditions. This enables operations teams to support, maintain, and troubleshoot the product effectively.
Option A, retrospective documentation, focuses on lessons learned and process improvements for the delivery team rather than explaining the product itself. While useful for continuous improvement, it does not directly support operational understanding of deliverables. Option B, Kanban or team boards, provide visibility into work in progress and workflow during development, but they are not designed to communicate finalized product functionality during handover. Option D, a risk management approach, helps identify and mitigate risks but does not clearly describe the delivered product or its capabilities.
Agile Foundation materials emphasize collaboration between delivery and operations, often aligned with DevOps principles, to reduce handover friction. Clear documentation on functionality supports this collaboration by ensuring shared understanding and continuity after delivery. When operations teams know exactly what has been delivered and how it functions, they can confidently take ownership, maintain service quality, and respond effectively to issues. This approach aligns with Agile’s focus on sustainable delivery, transparency, and long-term value creation.

The Team Retrospective Workshop is explicitly designed to facilitate team growth and continuous improvement in working practices. It is a fundamental agile practice where the team reflects on the recently completed work or sprint to identify what went well, what didn’t, and what could be improved. The goal is to foster an environment of trust and openness, enabling teams to discuss challenges and successes honestly.
Retrospectives promote inspect and adapt principles by encouraging teams to continuously evaluate their processes, collaboration, and tools. They help uncover systemic issues, process bottlenecks, or interpersonal challenges that may be impeding productivity or quality. Teams use this feedback to implement actionable improvements, which can range from adjusting communication methods to refining definitions of done or ready.
This workshop supports a key agile mindset-continuous learning and improvement-which directly contributes to team maturity, performance, and morale. Importantly, retrospectives are not about assigning blame but rather about fostering a growth mindset that accepts change as an opportunity to evolve.
While Project Kickoff Workshops (A) initiate project alignment and Progress Review Workshops (C) monitor project status, they do not primarily focus on team process improvements. The Team Planning Workshop (D) is concerned with planning upcoming work, not retrospection.
In PRINCE2 Agile, retrospectives are a critical tool to blend traditional project management with agile principles by promoting regular reflection and incremental enhancements.

The Team Planning Workshop is primarily held to update the product backlog. This collaborative session allows the delivery team to break down, refine, and reprioritize user stories or tasks to prepare for the upcoming iteration or sprint. The team reviews the product backlog items, clarifies acceptance criteria, estimates effort, and commits to the planned work.
Updating the product backlog at this level ensures that detailed planning aligns with the overall project vision and release goals. It empowers the team to self-organize and manage their workload, supporting agile principles of autonomy and collaboration.
While the project dashboard (A) provides status reporting, the release map (C) focuses on higher-level release planning, and OKRs (D) relate to strategic objectives, these are not the central focus of the team planning workshop.
PRINCE2 Agile promotes team planning workshops as essential forums for translating business priorities into actionable, manageable work for delivery teams.
Reference: PRINCE2 Agile Foundation Version 2, Section 6.3 “Team Planning,” and PRINCE2 Agile Study Guide, Chapter 6.

Trading/swapping is a technique used within the issues practice to manage and resolve conflicts or competing priorities by negotiating trade-offs. For example, scope items, resources, or deadlines may be traded or swapped between stakeholders to reach agreements that keep the project on track.
This collaborative negotiation supports flexible, pragmatic issue resolution, aligning with agile values of collaboration and customer focus. It enables project teams to balance competing demands while maintaining progress and business justification.
Objectives and key results (B) are goal-setting tools, refactoring (C) is a technical practice for code improvement, and delegation poker (D) is about decision-making authority – none specifically target issue resolution.
Trading/swapping aligns with PRINCE2’s controlled management of issues and agile’s collaborative problem-solving approach.

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 often explains Agile concepts using the “Agile Onion” model, which shows how different layers of Agile build upon one another. Within this model, principles provide the core guidelines that help teams understand the purpose behind Agile practices, making option D the correct answer. Principles act as a bridge between high-level values and practical methods, explaining why certain ways of working are encouraged.
The Agile Onion typically places mindset at the center, followed by values, then principles, and finally practices, techniques, and processes on the outer layers. While practices describe what teams do and processes describe how work flows, principles explain the intent that guides those actions. They help teams make informed decisions when situations change or when standard practices do not fit the context. By understanding principles, teams can adapt their practices while still remaining aligned with Agile thinking.
Option A, processes, focus on structured sequences of activities and are concerned with execution rather than purpose. Option B, mindset, represents underlying beliefs and attitudes, which shape behavior but do not explicitly provide guidance on how or why specific practices are used. Option C, values, define what is important, such as collaboration or customer focus, but they do not give enough direction on how to translate those values into action.
Agile Foundation documents emphasize that principles are essential for sustainable Agile adoption. They enable teams to move beyond mechanical “doing Agile” and toward thoughtful “being Agile.” When teams understand the principles behind practices, they are better equipped to tailor their approach, respond to change, and apply Agile effectively in different environments. Principles ensure consistency of intent while allowing flexibility in execution, which is fundamental to Agile success.

Kanban uses a flow-based approach to visualize and control work in progress (WIP). It emphasizes limiting WIP to improve flow and reduce bottlenecks, with continuous monitoring via Kanban boards. This approach supports flexibility, transparency, and efficiency in managing tasks.
The Agilometer (A) measures agility, Lean (B) is a broad philosophy focusing on waste reduction, and Scrum (D) is an iterative framework but uses time-boxed sprints rather than flow-based control.

The PRINCE2 practices represent the essential aspects of project management that must be applied consistently from start to finish in every project. These practices cover key areas such as managing risks, issues, quality, plans, progress, and change. They provide structured guidance and tools to ensure the project remains viable, controlled, and aligned with business objectives.
While processes define the stages and flow of activities, and the people element refers to roles and skills, practices are the ongoing activities and controls embedded throughout the project lifecycle. The project context shapes how practices and processes are tailored but does not itself define the consistent elements.
This consistent application of practices supports governance, transparency, and control, critical for successful project outcomes.