Mind the gap – incorporating the change agenda into scaled Agile.
summary
Argues scaled Agile frameworks like SAFe scale delivery but miss the business change needed so features sit unused; points to repeated cases where teams deliver every two weeks yet value in use only appears after six months and long programs drift for 18 months. Uses PI planning to map work to people, processes, policies and applies ADKAR/Prosci (awareness, desire, knowledge, ability, reinforcement) to design increments. Shows a practical plan tying five dev teams’ increments to existing comms and role‑based change activities to avoid the delivery‑adoption gap.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 4:51Programme management
- 10:29Scaled Agile approaches
- 20:04Change problems
- 26:13Why change facilitation?
- 28:07Building blocks of change
- 33:11Nothing happens differently until we reach Ability
- 34:593 levels of change
- 40:37Building a change approach
related talks
58mScaling Agile in Organizations
51mMastering Trade-offs for Scaled Agile Success
58mAgility at Scale: Tactical and Strategic Approaches
47mThe Only 2 Things needed to Scale Agile
29mBringing the Gap Between Agile, Engineering, and Leadership
26mAgile Version 2016
51mAgility at Scale: A Meeting of Mindsets
28mPhilips scaled Agile Transformation journey