PRINCE2 Agile Foundation V2 PRINCE2-Agile-Foundation Exam Questions

Answer : C

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.

Answer : C

In Agile Foundation guidance, the team retrospective workshop is a key event focused on continuous improvement, making identifying improvement opportunities the correct answer. Retrospectives are held at regular intervals, typically at the end of an iteration or delivery cycle, to allow the team to reflect on how they worked together and how their processes, tools, and interactions can be improved.

The primary purpose of a retrospective is not to plan product features or refine requirements, but to inspect and adapt the team's way of working. During the workshop, team members openly discuss what went well, what did not go as expected, and what could be improved. This reflection helps teams identify specific, actionable improvement opportunities that can be applied in the next iteration. Agile foundations emphasize creating a safe environment during retrospectives so that honest feedback and constructive discussion can occur.

Option A, prioritizing user stories, is typically done during backlog refinement or planning sessions and is the responsibility of the product owner with input from the team. Option B, defining acceptance criteria, usually takes place when preparing user stories before or during iteration planning, not during retrospectives. Option D, updating the project canvas, is a high-level planning or governance activity rather than a team-level continuous improvement practice.

Agile Foundation documents stress that retrospectives are essential for fostering a culture of learning and adaptability. By consistently identifying and implementing improvement opportunities, teams can enhance collaboration, improve quality, reduce waste, and increase predictability over time. Retrospectives also reinforce shared ownership of team performance, encouraging everyone to contribute to positive change. This focus on continuous improvement aligns directly with Agile principles of inspection and adaptation, making identifying improvement opportunities the central and most appropriate activity of the team retrospective workshop.

Answer : C

Answer : C

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.

Answer : B

Answer : B

The Managing Product Delivery process includes agreeing on and controlling the requirements for the delivery of specialist products. This process ensures that team managers understand the scope and quality expectations before work begins and that delivery aligns with the project plan.

Initiating a project and starting up a project establish overall direction but do not handle detailed delivery requirements. Managing a stage boundary reviews progress and plans the next stage.

This process maintains clarity and accountability for delivery within PRINCE2's framework, facilitating effective control over specialist products.

Answer : D