Study PRINCE2 Agile Foundation v2 Blending Agile Delivery with PRINCE2 Control: key concepts, common traps, and exam decision cues.
PRINCE2 Agile combines agile delivery with PRINCE2 project governance. The project still needs business justification, roles, management by stages, plans, risk control, change control, and progress reporting. Agile changes how delivery teams work within that governance.
PRINCE2 gives the project a management structure. Agile gives teams ways to deliver, learn, and adapt. The exam often tests whether you know which level a decision belongs to.
For example, a delivery team may reprioritize detailed backlog items inside agreed tolerances, but the project board still owns major business-justification decisions. A project manager may encourage frequent feedback, but that does not mean uncontrolled scope growth is acceptable.
Agile without governance can lose strategic alignment. Governance without agility can become slow, late, and detached from real customer learning. PRINCE2 Agile aims for control with flexibility.
| Situation | Stronger interpretation |
|---|---|
| team changes low-level backlog order | likely delivery-level adaptation |
| stage tolerance forecast will be exceeded | needs management escalation |
| customer feedback changes priority | review value, scope, and control impact |
| team wants no documentation | wrong if governance evidence is still needed |
A delivery team wants to change the order of low-level backlog items after customer feedback. The change remains within agreed tolerances. What is the strongest PRINCE2 Agile response?
A. Escalate every backlog reorder to the project board.
B. Allow appropriate team-level adaptation while keeping PRINCE2 controls and tolerances visible.
C. Stop using PRINCE2 because agile teams do not need governance.
D. Freeze the backlog for the entire project.
Best answer: B
Why: PRINCE2 Agile supports flexible delivery inside agreed governance. Adaptation is appropriate when it remains within delegated authority and tolerance.