PRINCE2 Agile Foundation v2 Risk, Change, and Stage Control

Agile delivery expects change and learning. PRINCE2 expects controlled management of risk, issues, and change. PRINCE2 Agile combines those expectations by allowing flexibility within defined governance.

Risk and change are not failures

In an agile context, feedback may reveal risk earlier or show that the product should change to deliver better value. That is useful. The issue is whether the project handles the learning responsibly.

Low-level adaptation inside tolerance may be handled by the team or project manager. A change that affects business justification, tolerance, major scope, cost, time, quality, or risk exposure may require escalation.

Stage control

Stages help senior decision makers review progress, risk, value, and continued justification. Agile delivery inside a stage can still use iterations, releases, and feedback cycles. The stage boundary remains a governance point.

Sample Exam Question

Customer feedback suggests a new feature would add value but would exceed agreed stage tolerance. What should happen?

A. The team should add it immediately because agile welcomes change.
B. The issue should be escalated through the appropriate PRINCE2 control route because tolerance may be exceeded.
C. The feedback should be ignored because PRINCE2 does not allow change.
D. The project should close automatically.

Best answer: B

Why: PRINCE2 Agile welcomes learning, but changes that exceed tolerance require governance.