Four Months as a New Scrum Master — Escaping 'Running Scrum Events Without Feeling Any Impact'
summary
A new Scrum Master with no prior Scrum experience applied concrete changes over four months: re-reading the Scrum Guide, weekly coaching, enforcing a focused daily Scrum (separating help requests), adding a 15-minute daily refinement, introducing relative estimates and velocity tracking, requiring a Definition of Done, and running real reviews with external domain experts using business scenarios. These practices led to measurable improvements: sprint goals met more consistently, fewer handbacks and interruptions, better estimation efficiency and domain knowledge, and team feedback shifting from stalled to steadily delivering customer value.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:32Team structure and struggles
- 5:03First actions
- 7:30Daily and Retrospective improvements
- 9:35Second event improvements
- 11:20Daily refinement and feedback
- 13:07Focus on value delivery
- 13:50Business scenario reviews
- 17:47Summary
related talks
14mThe 4 Hours Scrum Master
43mEver Since We Started Doing SCRUM Everything's Great. Not!
15mOne, Two, Three — You'll Be the Scrum Master!
22mIntense Recording: Ten Months of Development Close-Up — The Case of the Vanished Sprint Goal
15mAdvanced Scrum techniques for optimal delivery
41mThe New Era of the Scrum Master
19mTwo Examples of Scrum Master Initiatives Supporting the Whole Team in Large-Scale Scrum
26mThe systemic Scrum Master