Scaling Continuous Improvement mindset and making it stick
summary
An agile coaching team teaches facilitation, supplies a retro kit with 15 formats, and mandates the coach-facilitated first two-hour retro; result: coached 25 teams to full ownership, then scale to all 50 IT teams so coaches need under one hour weekly per team. They measure health by asking if teams run two or more reflections in five weeks and track KPIs with the every metric every week board. Watch for the danger zone: same format, manager-dominated sessions, or non-actionable mega-project outcomes.
AI-written summary · about
chapters (16)
- 0:00Introduction and setup
- 1:04Scaling continuous improvement mindset
- 3:36Empowering teams to own improvements
- 7:12Challenges in mindset handover
- 9:18Danger zone in retrospectives
- 13:20Detecting and addressing complacency
- 15:51Measuring team progress
- 18:03Current status in IT teams
- 19:51Expanding beyond IT
- 21:18Pilot challenges with non-IT teams
- 24:59Facilitating first retros for new teams
- 27:07Importance of mindset over tools
- 28:37Overall situation and next steps
- 29:41Key learnings summary
- 32:13Current progress and future goals
- 33:00Q&A session
related talks
42mConfessions of a Reformed Agile Coach
33mCreating a culture of continuous improvement
43m50 Shades Of Retrospective - Your Guide To Continuous Improvement
45mAgile Retrospectives and the Agile Teams of Today and Tomorrow
47mApplied Coaching Practices
39mScaled Retrospective – improvements bigger than a Scrum Team
01h 15mAgile Team Facilitation – moving from Good to Great
48mCoaching Models for Technical Agile Coaching