How an Agile Coach Changed a Team That Had Once Given Up on Scrum
summary
A team that had abandoned Scrum after a large schedule-driven rollout restarted six months later as a pilot with organizational backing and an agile coach. The coach used Scrum Guide readings, hands-on Miro sessions, and a staged approach (starting with a sprint zero and later adding stakeholder reviews) to change planning toward smaller slices, restore transparency, delegate implementation decisions from the PO, make sprint goals shared, shorten lead time, and enable incremental releases and candid feedback with measurable improvement.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:14First failed Scrum attempt
- 6:14Why Scrum failed
- 8:39Team's reaction to restart
- 10:55Second Scrum attempt with support
- 12:17Agile coach's impact
- 14:23Feedback and transparency
- 15:49Mindset shift and culture
- 16:56PO's role and empowerment
- 18:21Key differences and future steps
- 18:45Closing remarks
related talks
26mGet agile and don't die trying
07mInterview with Dominik Jungowski on Agile
52mAgile from the Trenches
05mFrAgile - lessons from a failed agile transformation
35mAgile Scrum Overview
11mLeading Agile Teams to Success: Lessons from the Trenches
16mLightning Talks
28mLessons and Expierience from 15 years of Agile Coaching