PRINCE2-Agile-Foundation PRINCE2 Agile Foundation (Version 2) Exam Questions and Answers

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.

Stakeholders are best described as those who can affect or be affected by the project. This definition is aligned with PRINCE2’s view and recognized globally in project management standards. Stakeholders include anyone with an interest or influence in the project outcomes, including project team members, users, suppliers, and external entities. Understanding and managing stakeholder engagement is crucial for project success, as stakeholders’ expectations and needs impact decisions and project delivery.

Options A, B, and D describe subsets or partial perspectives of stakeholders but do not capture the full inclusive scope.

The Delivering level is responsible for the day-to-day management and decision-making within the constraints set by the project manager. Delivering teams carry out the actual work to create the project products and manage their activities under the project’s governance framework. The Project Manager manages the overall project, while directing sets the strategic direction and commissioning authorizes initiation.

This separation ensures clear responsibilities and empowers the delivery teams to self-manage within defined boundaries.

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.

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.

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.

User inputs are initially gathered as user stories in the product backlog in PRINCE2 Agile. User stories represent small, customer-focused requirements that capture the "who," "what," and "why" of a feature. These stories form the foundation of requirements and quality criteria for the product and ensure that development is driven by user needs and value delivery.

The Definition of Done is developed later as part of the quality management approach to specify when work is complete. Epic user stories are larger features that can be broken down into smaller user stories. The quality register tracks quality-related activities but is not the first step for gathering user inputs.

Reference https://publications.axelos.com/prince2agile2016/content.aspx?page=pra_126 &showNav=true&expandNav=true

Delegation poker is a collaborative game used to define and clarify decision-making authority within teams. It helps teams agree on who has the power to make decisions for specific areas, from the team level to senior management. Using cards representing different levels of delegation, team members discuss and align expectations, ensuring clarity and reducing conflicts.

This technique fosters transparency, shared ownership, and empowerment, which are critical for agile teams operating under PRINCE2 governance. It also helps balance autonomy and control, supporting the principle of manage by exception.

Other options: a team skills matrix documents competencies, personas represent user archetypes for design, and magic estimation is a sizing technique — none focus on decision authority.

Delegation poker aligns well with PRINCE2 Agile’s emphasis on defined roles and empowered teams.

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.

A primary benefit of an organization being and doing agile is faster time-to-market. Agile methods emphasize iterative delivery, frequent releases, and continuous feedback, enabling organizations to deliver value sooner and adapt quickly to changes. This benefit directly supports business agility and competitive advantage.

Using agile techniques alone (B) is a means, not a benefit. Focusing solely on tasks (C) ignores value and flow, and setting tolerances to zero (D) is neither practical nor encouraged.