Agile Project Manager Master Class

Doing agile' means applying agile tools and ceremonies — standups, sprints, backlogs — without adopting the underlying values that make them effective. 'Being agile' means genuinely embracing adaptability, transparency, customer focus, and continuous improvement as the way a team thinks and behaves — with tools and ceremonies following from those values rather than substituting for them. This distinction is the most important concept in the master class because delegates who leave understanding only 'doing agile' will consistently underperform relative to those who genuinely 'are agile' in how they lead and manage.  

Day 3 covers the Scrum framework comprehensively within the broader context of value-driven delivery and customer centricity, examining the Scrum roles, events, and artefacts and how they are applied to agile planning and iterative delivery. Delegates develop the Scrum application capability to use the framework purposefully in delivery contexts rather than mechanically — understanding why each Scrum element exists and what it contributes to value delivery, rather than simply following the prescribed ceremonies without understanding their function.  

Agile risk management and continuous improvement are addressed within Day 4, examining how risk is identified and managed within iterative delivery cycles, how problem detection and resolution operate within agile teams, and how retrospective practices create the systematic reflection and improvement that differentiates agile teams that continuously improve from those that simply repeat the same sprint cycle without learning. Delegates develop the improvement discipline that sustains agile performance over extended delivery programmes.  

Servant leadership is addressed within Day 2 as the foundational leadership model for agile delivery, examining how servant leaders create the conditions for team performance rather than directing through authority, how they remove impediments, build psychological safety, and empower self-organisation. Delegates develop the servant leadership awareness and behavioural repertoire to lead agile teams in a way that amplifies their capability rather than constraining it a shift that requires genuine personal leadership development, not just conceptual understanding.  

Design thinking is addressed within Day 4 as a complementary discipline that strengthens the customer centricity and problem framing that agile delivery relies on. Delegates examine how design thinking's empathise, define, ideate, prototype, and test approach integrates with agile sprint cycles to ensure that what is being built iteratively is genuinely solving the right problem for the right users — addressing one of the most common failure modes of technically well-executed agile delivery that misses its intended impact.  

AI in agile projects is addressed within Day 5 as one of the current trends reshaping agile adoption and delivery practice — examining how AI tools support sprint planning, retrospective analysis, backlog prioritisation, velocity forecasting, and automated quality checking. Delegates develop the forward-looking awareness to evaluate AI applications within their agile delivery contexts critically and to identify where AI genuinely enhances agile performance versus where it creates adoption complexity without proportionate value.