What should be decided when configuring PRINCE2 effectively?

Configuring PRINCE2 for an agile environment is not about removing core elements or making significant changes. The official guidance emphasizes that all PRINCE2 principles, themes, and processes are still valid. The key to effective configuration is tailoring the implementation by deciding where to put the emphasis (e.g., more focus on frequent delivery) and where to add specific agile guidance, techniques, and behaviors (e.g., using retrospectives for the 'learn from experience' principle). This approach ensures governance is maintained while enabling agile delivery.

A. The guidance explicitly warns against removing PRINCE2 elements; instead, they should be tailored to the project's context.
C. PRINCE2 should not be 'significantly changed'. The framework is designed to be tailored, not fundamentally altered, to create the blend.
D. This is a negative framing; configuration is about enabling agile to work with all areas of PRINCE2, not identifying areas that cannot.

- AXELOS. (2018). PRINCE2 Agile® Foundation. TSO (The Stationery Office). Section 5.1, p. 33. "When tailoring PRINCE2 in an agile context, the art is to know where to put the emphasis and what agile techniques to add in."

- AXELOS. (2018). PRINCE2 Agile® Foundation. TSO (The Stationery Office). Section 5.2, p. 34. "It is a common misconception that you need to remove parts of PRINCE2 in order to use agile."