PRINCE2-Agile-Foundation PRINCE2 Agile Foundation (Version 2) Exam Free Practice Exam Questions (2026 Updated)

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 clearly identifies Scrum as an iterative and timeboxed approach to product delivery, making option A the correct answer. Scrum is built around fixed-length iterations called sprints, which are typically one to four weeks long. These timeboxes create a regular cadence for planning, development, review, and improvement, enabling teams to deliver usable increments of a product frequently and predictably.

Scrum emphasizes iterative delivery by breaking complex work into smaller, manageable pieces that can be completed within a sprint. Each sprint begins with planning, where the team selects work from the product backlog, and ends with a review and retrospective. This structure supports frequent inspection of both the product and the team’s way of working, allowing for continuous adaptation based on feedback and learning. Agile Foundation documents highlight that timeboxing is a key mechanism in Scrum, helping teams focus, limit work in progress, and reduce risk.

Option B, Kanban, is not timeboxed. Kanban focuses on continuous flow, visualizing work, and limiting work in progress rather than delivering in fixed iterations. Option C, the Agilometer, is an assessment tool used to evaluate suitability and risks of Agile adoption, not a delivery approach. Option D, Lean, is a broader philosophy focused on eliminating waste and optimizing value flow; while it can influence Agile delivery, it is not inherently iterative and timeboxed in the way Scrum is.

Agile Foundation materials stress that Scrum’s iterative and timeboxed nature supports transparency, predictability, and early value delivery. By delivering small increments regularly, teams can gather feedback early, reduce uncertainty, and adapt priorities as needs change. This makes Scrum particularly effective in environments where requirements evolve and learning is essential.

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 Foundation guidance clearly states that the project retrospective workshop is the workshop designed to extract actionable insights for future iterations, making option C the correct answer. Retrospectives are a core Agile practice focused on learning, reflection, and continuous improvement. Their primary purpose is to help teams and stakeholders understand what has happened, why it happened, and how future ways of working can be improved.

During a project retrospective workshop, participants reflect on recent iterations or delivery stages, examining aspects such as collaboration, communication, processes, tools, quality, and decision-making. The emphasis is not on assigning blame, but on identifying patterns, root causes, and opportunities for improvement. From this reflection, the team agrees on concrete, actionable actions that can be implemented in upcoming iterations to enhance effectiveness and outcomes.

Option A, the progress review workshop, focuses on assessing current status, deliverables, and performance against plans or objectives. While it may highlight issues, it does not primarily aim to generate improvement actions. Option B, the project initiation workshop, occurs at the start of the project and establishes vision, scope, and approach, rather than extracting learning from experience. Option D, the team planning workshop, concentrates on selecting and organizing upcoming work, not on analyzing past performance or improving ways of working.

Agile Foundation documents emphasize that retrospectives are essential for embedding a culture of learning and adaptability. By regularly extracting actionable insights, teams can continuously refine their processes, strengthen collaboration, and improve quality and delivery speed. Retrospectives also support psychological safety by creating a structured space for honest discussion and shared ownership of improvement. This focus on turning reflection into action ensures that learning is applied, not just observed, making the project retrospective workshop the primary mechanism for driving improvement across future iterations.

The starting-up workshop is the initial workshop where the foundation for the project is established, including the creation and clarification of project role descriptions. Defining roles early ensures clarity of responsibilities, helps establish governance, and sets expectations for the project team.

Kickoff (B) focuses on launching the project, initiation (C) develops detailed plans, and the project canvas (D) is a tool for capturing high-level information but does not define roles explicitly.

Culture refers to the collective attitudes, values, beliefs, and goals shared by a group or organization. It shapes how people behave, make decisions, and interact. In PRINCE2 Agile, understanding and adapting organizational culture is critical for successful agile adoption and delivery.

Leadership (B) influences culture but is distinct, co-creation (C) is a collaborative approach, and management (D) relates to planning and control activities.

A positive, agile-friendly culture fosters openness, trust, and continuous improvement.

The burn-down chart is a visual tool used in agile to monitor progress by tracking the remaining work against time. It provides teams and stakeholders with a clear, real-time view of project status and forecast completion, allowing for early identification of potential delays or bottlenecks.

The delegation matrix (A) defines authority, swarming (B) is a team collaboration technique, and t-shirt sizing (C) is an estimation method, none of which directly monitor progress.

Agile Foundation guidance explains that the purpose of the agile enablement workshop is to identify, assess, and plan for risks associated with Agile adoption, making option C the correct answer. This workshop is a structured activity designed to help organizations and project teams understand how well Agile ways of working fit their specific context and what challenges may arise when adopting Agile approaches.

The agile enablement workshop focuses on readiness rather than delivery execution. It examines factors such as organizational culture, governance expectations, stakeholder engagement, team capability, leadership support, and external constraints. By discussing these areas openly, participants can identify potential barriers to Agile adoption, assess their impact, and agree on actions to reduce or manage those risks. This proactive approach supports informed decision-making and avoids unrealistic expectations about Agile.

Option A, risks associated with project delivery, relates more to traditional project risk management practices. Option B, team delivery risks, focuses narrowly on team-level execution issues rather than adoption. Option D, enterprise agility risks, applies at a broader organizational transformation level and goes beyond the typical scope of an agile enablement workshop, which is usually project- or initiative-focused.

Agile Foundation documents emphasize that Agile adoption is not risk-free and should be approached thoughtfully. The agile enablement workshop helps ensure that Agile is tailored appropriately rather than applied mechanically. It supports alignment between Agile teams and governance structures, clarifies where flexibility is possible, and highlights where controls are required. By identifying and planning for adoption risks early, organizations increase the likelihood of successful Agile implementation while preserving the core values of adaptability, collaboration, and value-driven delivery.

In Agile Foundation guidance, the risk practice is explicitly responsible for the identification, assessment, and management of uncertainties, making option A the correct answer. Risk is defined as uncertainty that, if it occurs, will have a positive or negative impact on objectives. Agile recognizes that uncertainty is inherent in complex and adaptive work, so effective risk management is essential to successful delivery.

The risk practice focuses on proactively identifying uncertainties early, assessing their likelihood and impact, and determining appropriate responses. Agile Foundation documents emphasize that risk management in Agile is continuous rather than a one-time activity. Risks are regularly reviewed, updated, and addressed throughout the lifecycle as new information emerges. This aligns with Agile principles of transparency, inspection, and adaptation, allowing teams to respond to uncertainty in a timely and informed manner.

Option B, plans, focuses on outlining how objectives will be achieved and how work will be organized over time. While planning may take risks into account, it does not primarily identify or assess uncertainties. Option C, quality, ensures that outputs meet agreed standards and acceptance criteria but does not deal directly with uncertainty. Option D, business case, justifies why a project should proceed by outlining costs, benefits, and risks at a high level, but it does not actively manage or assess uncertainties on an ongoing basis.

Agile Foundation guidance highlights that Agile approaches often reduce risk by delivering incrementally, seeking early feedback, and validating assumptions quickly. However, this does not eliminate the need for a structured risk practice. Instead, risk management supports Agile delivery by making uncertainties visible and manageable. By embedding risk identification and assessment into regular team activities, organizations can make better decisions, protect value, and increase confidence among stakeholders while still maintaining flexibility and responsiveness to change.