Free PRINCE2 Agile Foundation V2 PRINCE2-Agile-Foundation Exam Questions

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 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.

Psychological safety is a critical enabler of effective Agile teams, and Agile Foundation materials often reference the four progressive levels of psychological safety: inclusion safety, learner safety, contributor safety, and challenger safety. Among these, contributor safety is the level that specifically encourages individuals to share their ideas, knowledge, and skills openly while making meaningful contributions to the team's work.

Contributor safety exists when team members feel trusted and empowered to apply their skills, experience, and ideas without fear of embarrassment, rejection, or negative consequences. At this level, individuals are not only accepted as part of the team but are also encouraged to actively participate, take ownership of tasks, and contribute value. Agile environments rely heavily on this level of safety because collaboration, cross-functional work, and self-organization depend on people confidently sharing what they know and what they can do.

Option C, inclusion safety, is more foundational. It ensures that individuals feel accepted and respected as members of the group, but it does not necessarily mean they feel safe enough to contribute ideas or skills. Option D, learner safety, focuses on the ability to ask questions, experiment, and make mistakes in order to learn. While important, it centers on learning rather than contribution. Option A, challenger safety, represents the most advanced level, where individuals feel safe to challenge existing ideas, processes, and decisions. This goes beyond sharing skills and ideas into constructive dissent.

Agile Foundation guidance emphasizes contributor safety because Agile teams thrive when every member actively contributes to delivering value. When contributor safety is present, teams benefit from diverse perspectives, improved problem-solving, higher engagement, and stronger accountability. This level of psychological safety directly supports Agile principles such as collaboration, transparency, and continuous improvement, making option B the correct answer.

The principle that establishes governance by delegating responsibilities and setting tolerances is manage by exception, making option C the correct answer. Agile Foundation guidance, aligned with PRINCE2 and PRINCE2 Agile principles, explains that effective governance does not require constant oversight or micromanagement. Instead, it relies on clearly defined roles, delegated authority, and agreed tolerances within which teams are empowered to operate.

Manage by exception works by setting measurable tolerances for key aspects such as time, cost, scope, quality, risk, and benefits. As long as work remains within these agreed limits, the team or delivery level can proceed independently without escalation. This creates clarity around accountability while allowing teams the autonomy needed to work efficiently and respond to change---an essential aspect of Agile delivery. Escalation only occurs when forecasts indicate that tolerances will be exceeded, ensuring that senior management attention is focused where it adds the most value.

Option A, ensure continued business justification, focuses on confirming that the project remains viable and worthwhile, but it does not define how governance is enacted day to day. Option B, tailor to suit the project, emphasizes adapting methods and controls to the project context rather than establishing governance through delegation. Option D, focus on products, ensures clarity around outputs and acceptance criteria but does not address governance or escalation mechanisms.

Agile Foundation documents highlight that manage by exception supports agility by balancing control with empowerment. Teams gain the freedom to self-manage and deliver iteratively, while leadership retains confidence that risks are controlled and objectives are protected. This principle reduces unnecessary reporting, speeds up decision-making, and supports trust between governance levels. By clearly delegating responsibilities and defining tolerances, manage by exception provides a practical and effective governance model compatible with Agile ways of working.

Speaking the language of leadership is essential for securing leadership buy-in when scaling agile. This means framing agile benefits, risks, and requirements in terms that resonate with leaders---such as business value, risk management, and return on investment---rather than just agile jargon.

While empowering teams (D) and emphasizing agile practices (C) are important, without leadership understanding and support, agile scaling is unlikely to succeed. Ensuring all decisions come from leadership (B) contradicts agile principles of decentralization and empowerment.

Effective communication tailored to leadership priorities fosters alignment and commitment.

The Recommend step in issue management involves analyzing the issue and evaluating possible options to resolve it. At this stage, the project team or responsible individuals identify potential solutions, weigh their pros and cons, and recommend the best course of action to decision-makers.

Capture is the initial identification and recording of the issue, Decide involves making the final decision on the recommended solution, and Implement is the execution of the chosen resolution. Evaluating options thoroughly during the Recommend phase helps ensure informed decision-making and effective issue resolution.

This structured approach aligns with PRINCE2's focus on proactive issue management, maintaining control and reducing risk impacts.

Agile Foundation guidance explains that the release planning workshop is the forum where personas and evolving user needs are revisited and refined, making option C the correct answer. Release planning focuses on aligning upcoming work with user value, business priorities, and learning gained from previous deliveries. As Agile delivery is iterative and incremental, understanding users is not a one-off activity but an ongoing process that evolves as feedback is gathered.

During a release planning workshop, teams review insights from recent increments, stakeholder feedback, and real user behavior. Personas---representations of key user types---are revisited to confirm whether assumptions remain valid or need adjustment. As products evolve, new needs may emerge, priorities may shift, and earlier hypotheses about users may prove incomplete. Release planning provides the structured opportunity to incorporate this learning and refine the understanding of who the users are and what they need most next.

Option A, the team retrospective workshop, focuses on improving the team's ways of working rather than reviewing user needs or personas. Option B, the project kickoff workshop, is typically held at the start of the initiative to establish initial vision, scope, and understanding, but it does not revisit evolving needs. Option D, the agile enablement workshop, concentrates on assessing and planning for risks associated with Agile adoption, not on refining user personas.

Agile Foundation documents emphasize that Agile success depends on continuous alignment with customer and user value. Release planning workshops support this by ensuring that upcoming work reflects the latest understanding of user needs rather than outdated assumptions. By regularly revisiting personas during release planning, teams strengthen customer focus, reduce waste, and improve the likelihood that delivered increments will meet real user expectations. This approach reinforces Agile principles of feedback, learning, and value-driven delivery.

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.

A key benefit of being and doing agile is increasing user satisfaction by delivering value early and continuously, adapting to feedback, and ensuring the product meets real user needs. Agile approaches emphasize collaboration with customers and iterative delivery, which enhances satisfaction compared to traditional, rigid methods.

While following processes (A) and using agile techniques (B) are means to an end, they do not directly guarantee benefits. Focusing solely on tasks (D) risks losing sight of value delivery.

User satisfaction is a central measure of agile success and reflects the effective application of agile principles.