PRINCE2 Agile Practitioner v2 Scaling Agile with Flexible Control

Scaling agile increases the need for clarity. More teams, suppliers, dependencies, and stakeholders create more interfaces. Practitioner scenarios may test whether you can preserve agile benefits while adding enough coordination and control.

Scaling concerns

Look for dependencies, duplicated work, inconsistent definitions of done, unclear priorities, weak integration, supplier boundaries, and poor visibility. The answer should improve transparency and coordination without turning delivery into excessive bureaucracy.

Flexible control

Flexible control means applying the minimum control needed for the risk and complexity. A simple team can use lightweight coordination. A complex multi-team project may need integrated planning, shared cadence, dependency management, clear escalation, and agreed reporting.

Sample Exam Question

Three agile teams are delivering related products, but dependencies are causing repeated delays. What is the strongest action?

A. Let each team work independently with no shared visibility.
B. Add dependency visibility, coordination cadence, and escalation routes while preserving team-level agility.
C. Stop all agile work because scaling is impossible.
D. Ask the project board to manage every task-level dependency.

Best answer: B

Why: Scaling requires transparency and coordination. The answer should add enough control without removing useful team-level agility.