The 4 Hours Scrum Master
summary
Claims sustained success running four teams while spending about four hours a week on Scrum Master work, proven over two years. Techniques: deliberate absence and lateness to force self-organization, delegate one eager team member to run events, teach tools once then stop doing the task, and pin printed burndown charts until teams care. Results: a two‑day release planning ran without presence, three of four teams adopt daily burndown reviews, caution that this only works with performing teams and requires emotional investment.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:28The 4 Hours Workweek
- 0:58Best Scrum Master is Invisible
- 1:56Scrum Lab
- 2:07The Deadlines
- 3:13Being Late
- 5:22Excuses
- 7:05Delegation
- 8:05Tasks
- 9:29The Warning
- 9:57Emotional Investment
- 11:55Three Simple Steps
- 12:26Experiment
- 12:52Your job
- 13:12Whats next
related talks
20mFour Months as a New Scrum Master — Escaping 'Running Scrum Events Without Feeling Any Impact'
15mAdvanced Scrum techniques for optimal delivery
44mHow Lean is Your Scrum
19mTwo Examples of Scrum Master Initiatives Supporting the Whole Team in Large-Scale Scrum
48mMeasuring Performance: Quantifying the Work of a Scrum Master
36mHow YOUR scrum team can excel in a remote setting
45mKeynote: The 8 Stances of a Scrum Master
21m600 Days of LeSS: A Practice Chronicle