PRINCE2 Agile® wiki
« Extra-concepts


The term requirement, as used in PRINCE2, is practically a replacement for “scope”, “features” (mostly functional-features), or even “user stories”. Therefore, the requirements focus area explains the way scope is managed in PRINCE2 Agile.

Scope Management in Agile

Agile methods have two major approaches in different contexts:

The second approach is the default in PRINCE2 Agile, and the first one might not be compatible with the governance layers of PRINCE2.


Regardless of the approach, at least a level of scope is dynamic in Agile, which means that its elements can be added, removed, or reinterpreted easily. In order to do so, some kind of prioritization is required. The development would be focused on the highest priority items first, because:

The ideal way of prioritization is to assign business values to each item and use it for ordering (prioritizing). Since this is difficult in most situations, a simple MoSCoW Prioritization is more common and practical.

Note: MoSCoW Prioritization can also be used for quality criteria.

Levels of Requirement Specification

Like planning in general, requirement specification should be done in multiple levels, from high-level to detail. This is aligned with the Manage by Stages and Manage by Exception principles, and also enables Agility.

The following is the levels of requirement specification:


See Also

Written by Nader K. Rad

This is (and will be) a work in progress: More details will be added in the future, depending on the feedback.

This wiki is developed and managed by an accredited trainer, independent of AXELOS. While aligned with their guidelines, it’s not an official resource.