The Scrum Master’s First Step Begins with Observation — Find the Thread to Team Improvement
summary
Join a new Scrum team and spend the first two sprints to a month observing actual behavior: sit in mob sessions, Slack huddles and standups, capture factual notes in Confluence, and look for recurring patterns such as estimation gaps or long morning check-ins. Create a short private prioritized impediment list with the top 2–3 issues, surface them in one‑on‑ones and retros, and measure changes in sprint rhythm to drive gradual, repeatable improvements and reduce surprises.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:30First steps as Scrum Master
- 6:42Four focus points
- 9:36When to intervene
- 11:03Impediment list
- 12:32Improvement loop
- 13:36Key lessons
- 15:50Why keep observing
- 16:34Q&A
related talks
19mTwo Examples of Scrum Master Initiatives Supporting the Whole Team in Large-Scale Scrum
11mGuiding self-organising teams
59mFrom Ok-ish to Outstanding: How any team can become a high-performing one
43mEver Since We Started Doing SCRUM Everything's Great. Not!
26mThe systemic Scrum Master
02mInterview with
15mOrganize your SMs and POs development
24mIs the Scrum Master a Coach? Mentor? Facilitator? Exploring Eight Choices