Pass the PRINCE2 Agile PRINCE2-Agile-Foundation Questions and answers with Dumpstech

Personas in PRINCE2 Agile serve as fictional, archetypal users representing the needs, behaviors, and goals of real users. In the business case practice, personas are used to identify and articulate specific user benefits. This ensures the project focuses on delivering value that meets the actual needs of different user groups.

By understanding personas, teams can tailor product features and prioritize requirements that provide meaningful benefits, thereby strengthening the business case and increasing stakeholder buy-in. Personas help clarify who will use the product, what problems they face, and how the solution delivers value.

Personas go beyond demographic grouping (A); they are detailed profiles including motivations and pain points. They do not relate directly to timelines (B) or product version differentiation (D).

Using personas aligns with agile principles of customer focus and continuous stakeholder engagement embedded in PRINCE2 Agile.

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.