Study PRINCE2 Agile Practitioner v2 Tailoring by Risk, Complexity, and Maturity: key concepts, common traps, and exam decision cues.
Tailoring is not weakening the method. It is adapting PRINCE2 Agile so that control and agility fit the project context. Practitioner scenarios often describe projects with different levels of risk, complexity, agile experience, and stakeholder pressure.
A low-risk internal project with experienced agile teams may need lighter documentation and more delegated delivery choices. A regulated, high-risk, or multi-supplier project may still use agile techniques, but it needs stronger evidence, clearer controls, and more explicit decision rights.
Teams new to agile may need coaching, clearer working agreements, and gradual introduction of techniques. Mature teams may be trusted with more adaptation inside tolerances. The answer should not assume the same approach fits both.
Complexity increases the need for coordination. Multiple teams, dependencies, external suppliers, contractual boundaries, or safety constraints require visible interfaces and governance, not simply more agile ceremonies.
A project has high regulatory risk, multiple suppliers, and low team experience with agile. Which tailoring approach is strongest?
A. Remove governance so the teams can learn faster.
B. Apply agile techniques with stronger evidence, clearer decision rights, and explicit controls.
C. Ban all agile techniques.
D. Let each supplier define its own reporting format without coordination.
Best answer: B
Why: PRINCE2 Agile should be tailored to context. High risk and low maturity call for proportionate controls, not the abandonment of agility or governance.