PRINCE2 Agile brings together the structured control of PRINCE2 and the iterative delivery of agile methods. While many guides focus on practices and techniques, the role of behaviour is just as important. Behavioural concepts shape how teams collaborate, how decisions get made, and how governance and delivery remain aligned. This article explains the central behavioural themes in PRINCE2 Agile and how they influence everyday project work.
Boundaries and delegation
PRINCE2 insists on clear roles and tolerances. In an agile context this means leaders must set boundaries and then delegate authority within them. The project board provides the strategic direction and stage tolerances. Agile teams then make day-to-day delivery decisions inside those constraints. Good behaviour here is about trust and accountability: leaders should be willing to let teams make operational choices, and teams should report honestly when tolerances are at risk.
Practical signs of this behaviour
• Clear handover of responsibilities at stage gates and during team formation.
• Teams escalating only when tolerance thresholds are breached.
• Project managers focusing on exceptions rather than routine oversight.
Frequent, honest communication
Agile working depends on short feedback loops. PRINCE2 Agile expects teams to keep stakeholders informed without overloading them. That requires a habit of concise, evidence-based updates and a willingness to raise issues early. Communication should be factual, timely and targeted to the right audience.
Ways to support this behaviour
• Time-boxed stand-ups and succinct highlight reports.
• Use of visual boards and dashboards to make progress transparent.
• Regular reviews where acceptance criteria and priorities are rechecked.
Customer focus and clear acceptance
Delivering fit-for-purpose products requires constant collaboration with the customer or business representatives. Behaviourally, this means prioritising the users needs, defining acceptance criteria early, and testing assumptions through incremental delivery. Business representatives should stay engaged as active decision makers rather than distant approvers.
How this appears in practice
• Early definition of acceptance criteria and definition of done.
• Incremental deliveries for early validation and course correction.
• Active senior user participation in prioritisation decisions.
Flexible planning with discipline
Agile planning is iterative but not careless. PRINCE2 Agile promotes plans that adapt while still respecting stage tolerances and the project case. This balance depends on the behaviour of treating plans as living documents: adjust when justified, but justify every change. That discipline preserves governance while enabling responsiveness.
Techniques to encourage the right behaviour
• Short planning horizons with regular re-planning sessions.
• Transparent change records and impact assessments.
• Clearly documented reasons for reprioritisation.
Continuous improvement and learning
Agile teams should routinely reflect on how they work and make small, incremental improvements. Within PRINCE2 Agile, retrospectives operate alongside formal stage reviews. The desired behaviour is open critique focused on processes and outcomes rather than personal blame.
Steps to embed this behaviour
• Short, constructive retrospectives after iterations and stages.
• Action lists with owners and review at the next retrospective.
• Sharing lessons between teams and incorporating them into the project approach.
Manage by exception and respectful escalation
A core PRINCE2 idea is manage by exception. In an agile setting this reduces unnecessary management interference while preserving escalation routes for exceptions. Respectful escalation means reporting issues with proposed options rather than simply passing problems up the chain.
Good practices here
• Use exception reports confined to material breaches of tolerance.
• Include recommended corrective actions when escalating.
• Keep escalation processes lightweight and decision-oriented.
Collaboration across disciplines
PRINCE2 Agile emphasises multidisciplinary teams that include business, development and assurance perspectives. Behavioural expectations are cooperation, shared responsibility and mutual respect. Teams should pool knowledge, not silo it, and be prepared to make trade-offs jointly.
Ways to show collaborative behaviour
• Co-located planning or virtual collaboration hubs.
• Shared definition of priorities and joint acceptance testing.
• Cross-functional participation in key decision points.
Practical starting points
To encourage these behaviours, teams can:
• Establish a short code of conduct for meetings and decision making.
• Set visible tolerances and escalation routes at project initiation.
• Schedule regular, time-boxed feedback events that include users and the project board where appropriate.
For managers and practitioners, attending to behaviour is not optional. The way people work together determines whether PRINCE2 Agile principles are merely documented or actively practised. Small changes in conduct - clearer delegation, earlier escalation, honest updates and routine reflection - make governance effective without stifling delivery.
For those who want formal training or scheduled sessions to practise these behaviour concepts, Discover courses from Knowledge Train.
Top comments (0)