Free PRINCE2 PRINCE2-Agile-Foundation Practice Exam with Questions & Answers | Set: 4

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.

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.

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.

The Progress practice in PRINCE2 Agile is focused on providing a forecast of the project's viability by monitoring actual progress against plans and predicting future performance. It ensures that decisions can be made based on current status and trends, enabling timely interventions if necessary.

This practice involves collecting progress data, reviewing milestones, updating forecasts, and communicating status to stakeholders. Forecasting viability includes assessing whether the project remains aligned with business justification and expected benefits.

While opportunities and threats are part of risk management (B), user needs belong to requirements management (C), and accountability is a broader governance concern (D), progress specifically deals with tracking and forecasting delivery status.

The practice combines traditional PRINCE2 stage controls with agile iterative reviews, providing an integrated view of progress.