Study PRINCE2 Agile Foundation v2 BE Agile and DO Agile in PRINCE2 Agile: key concepts, common traps, and exam decision cues.
BE agile is about mindset and behaviour. DO agile is about using agile practices and techniques. Foundation candidates need this distinction because many weak answers reduce agility to tools, ceremonies, or team labels.
An organization can hold daily stand-ups, maintain a Kanban board, or deliver in short iterations and still behave in a non-agile way if it suppresses feedback, hides problems, ignores customer value, or refuses to adapt. Conversely, a team can show agile behaviour by collaborating, learning quickly, and making work transparent even before every technique is fully mature.
BE agile emphasizes adaptability, transparency, collaboration, trust, learning, and responsiveness. In PRINCE2 Agile, those behaviours do not remove governance. They make governance more effective because project boards, project managers, teams, and stakeholders see issues earlier and can make better decisions.
DO agile includes practical techniques such as iterative delivery, visual boards, timeboxing, prioritization, workshops, burn charts, stand-ups, demos, retrospectives, and frequent feedback. These techniques are useful only when they support the project objective and fit the context.
The common trap is choosing an answer that names an agile technique without explaining the behaviour or project-control reason behind it. Foundation questions often reward the option that connects technique, mindset, and PRINCE2 governance.
A team holds daily stand-ups but does not discuss impediments openly because members are afraid of blame. What is the best Foundation-level interpretation?
A. The team is fully agile because it uses a daily agile event.
B. The team is doing one agile technique but is not fully showing agile behaviours such as transparency and trust.
C. The team should remove all PRINCE2 governance.
D. The team should stop communicating until the next stage boundary.
Best answer: B
Why: PRINCE2 Agile distinguishes mindset from technique. A stand-up alone does not prove agile behaviour if transparency and collaboration are missing.