Applying Agile Behaviours, Concepts and Techniques
What you must understand
This domain tests whether you can behave agile inside a PRINCE2 project. Learn the five behaviours precisely and be able to match a scenario to one: transparency (make work and progress visible), collaboration (work jointly toward a shared goal), rich communication (face-to-face, high-bandwidth, frequent), self-organisation (team decides how to do the work), exploration (experiment, learn, adapt).
Know the concepts these behaviours serve: empirical control, servant leadership, timeboxing, prioritisation by value, iterative and incremental delivery, and continuous improvement (retrospectives, Kaizen).
Traps
- Confusing collaboration with rich communication: collaboration is joint work; rich communication is the channel quality.
- Assuming self-organisation means the team sets its own scope and budget; it does not - it decides how to deliver agreed work.
- Treating a retrospective as optional. It is the mechanism for continuous improvement and must be planned.
- Selecting 'tell the team what to do' when the scenario shows a servant-leadership opportunity.
Rule of thumb
When a question describes a problem (e.g. stakeholders surprised by progress), the fix is usually the behaviour that was missing (here: transparency). Diagnose the missing behaviour before choosing an action.
Worked example
A project board complains it only hears about issues at stage end. The team already holds daily stand-ups. The gap is rich communication with the board - add a lightweight, frequent progress radiator (e.g. a burn chart and a short highlight report) rather than more meetings.