PRINCE2 Agile defines specific agile 'concepts', which are distinct from agile 'behaviours' or 'techniques'. The official guidance discusses 'Requirements' as a key concept, highlighting that a common way to define them in an agile context is through 'user stories'. Although 'daily stand-up meetings' are classified as a technique, this option is the only one containing an element (user stories) that is explicitly and centrally discussed under the 'Key concepts' chapter of the PRINCE2 Agile framework. The other options clearly fall into different PRINCE2 Agile categories, making this the best possible answer.

A. Prioritizing what needs to be delivered.

This describes an activity typically carried out using a technique. In PRINCE2 Agile, MoSCoW is the primary technique used for prioritization.

B. Trusting and not blaming others.

This is an example of a PRINCE2 Agile 'behaviour'. It is fundamental to creating the collaborative and transparent environment that agile ways of working depend upon.

C. Setting tolerances for each project objective to establish limits of authority.

This is a direct application of the core PRINCE2 principle of 'Manage by Exception', which is tailored but not fundamentally changed in a PRINCE2 Agile context.

---

& Explanation:

AXELOS. (2015). PRINCE2 Agile® Guidance. The Stationery Office (TSO). Chapter 10

"Key concepts

" specifically Section 10.2

"Requirements

" which states

"A common way to define requirements in an agile way is in the form of user stories" (p. 82).

AXELOS. (2015). PRINCE2 Agile® Guidance. The Stationery Office (TSO). Chapter 24

"The daily stand-up

" identifies this as a technique (p. 193). The question combines a concept with a technique

but it is the only option containing a concept.

Why Incorrect Options are Wrong:

A: AXELOS. (2015). PRINCE2 Agile® Guidance. The Stationery Office (TSO). Chapter 22

"Prioritization

" describes MoSCoW as the primary technique for this purpose (p. 183).

B: AXELOS. (2015). PRINCE2 Agile® Guidance. The Stationery Office (TSO). Chapter 5

"PRINCE2 Agile behaviours

" details the importance of behaviours such as collaboration and transparency

which encompass trust (p. 41).

C: AXELOS. (2015). PRINCE2 Agile® Guidance. The Stationery Office (TSO). Section 4.2.6

"Manage by Exception

" explains how this core PRINCE2 principle is applied in an agile context (p. 37).