PRINCE2 Agile Foundation Free Sample Questions

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.

The Definition of Ready (DoR) is a checklist of criteria that a user story must meet before it can be taken into a sprint. It ensures that stories are well-understood, have clear acceptance criteria, and are small enough to be completed. Implementing a DoR would directly address the problem of poorly defined stories entering the sprint.

PRINCE2 Agile does not eliminate the Business Case; it adapts it. The initial Business Case may be less detailed, with assumptions that will be tested. It is seen as a living document, with a strong focus on the incremental release of value and benefits. While it's continuously considered, formal re-validation typically happens at stage boundaries or key release points, not necessarily after every sprint, which would be too frequent and bureaucratic.

The primary purpose of WIP limits in Kanban is to optimize the flow of value. By limiting the amount of work in any given state, teams can quickly identify and address bottlenecks. This prevents tasks from piling up, reduces context switching, and encourages a 'pull' system where new work is only started when there is capacity, leading to a smoother, more predictable delivery process.

In PRINCE2 Agile, the 'Managing Product Delivery' process is where the delivery team performs its work. The Project Manager's role is not to manage the team's day-to-day activities (which is the responsibility of the Team Manager or the self-organizing team itself), but to manage the link between the project and the team. This involves authorizing Work Packages, receiving Checkpoint Reports, and ensuring that what the team is delivering aligns with the overall project objectives and tolerances.

Information radiators are tools for making progress, impediments, and plans visible to everyone. Their effectiveness depends entirely on the behaviour of Transparency. If the information displayed is not honest, accurate, and up-to-date, the radiator becomes misleading and loses its value. Transparency ensures that what is displayed reflects the true state of the project.