PRINCE2 Agile Foundation Practice Questions

This is a classic 'Manage by Exception' scenario. The Project Manager has forecasted that stage tolerances will be exceeded. The correct PRINCE2 action is to create an Exception Report to inform the Project Board. This report should not just state the problem but also provide options. In an agile context, the most common options are to use the flexibility of scope (by de-scoping less important features using a method like MoSCoW) or to request a change to the stage's time/cost tolerances, allowing the board to make an informed decision. This respects PRINCE2 governance while embracing agile's responsiveness to change.

A retrospective is a meeting held at the end of an iteration where the team reflects on what went well, what didn't, and why. The goal is to identify and agree on specific actions to improve processes, tools, or relationships for the next iteration. This directly supports the PRINCE2 principle of 'Learn from experience'.

The Project Board's role remains one of governance, not day-to-day management. In an agile context, they adapt by empowering the Project Manager and delivery teams within clearly defined tolerances (fix and flex). Their involvement is crucial at key decision points, such as authorizing stages ('Managing a Stage Boundary'), but they should avoid interfering with the team's self-organization during a stage. They maintain control through Highlight Reports and Exception Reports.

The Project Product Description (PPD) defines what the project must deliver to be accepted. In an agile context, it's crucial for setting the overall vision and boundaries, even when the detailed features are expected to emerge. It outlines the customer's quality expectations and the acceptance criteria for the final, complete product. This provides a guiding star for the iterative development and prevents the project from drifting away from its core purpose.

T-shirt sizing is a form of relative estimation used for large or poorly understood work items like epics. Its main advantage is speed and simplicity. It helps teams and stakeholders quickly agree on the relative magnitude of work (e.g., 'this epic is much larger than that one') without the false precision of estimating in hours or days, which would be impossible and wasteful at such an early stage.

In PRINCE2 Agile, it is fundamental to protect the level of quality. The scenario explicitly states a fixed delivery date, so time must also be fixed. To accommodate emergent requirements and stay within the fixed time and quality constraints, scope and cost are the targets that should be flexed. This allows for prioritization of features (scope) and potential adjustments to resources (cost) while ensuring a timely, high-quality delivery.

A Spike is a type of user story or task aimed at answering a question or gathering information, rather than producing a shippable feature. It's used to explore a technical approach, understand a requirement better, or estimate a large, uncertain piece of work. The developer's investigation perfectly fits this definition.

The quadrant chart places 'Rich Communication' in the top-right quadrant, labeled 'Action Required', indicating it is both high priority and high risk. Agile methods rely heavily on effective and frequent communication. A low score in this area is a major impediment and represents the most significant risk that must be addressed for the project to succeed using agile.

This statement is false. The 'Manage by Exception' principle is complemented, not replaced, by agile practices. Daily stand-ups and burn charts provide early warnings of potential tolerance deviations at the team level. However, the formal mechanism of escalating exceptions to the next level of management (e.g., from Project Manager to Project Board) when stage tolerances are forecast to be exceeded remains a core PRINCE2 control.