The Daily Scrum belongs to the Developers. The Scrum Master makes sure it happens and stays inside the timebox.
The Scrum Master does not run it.
That sentence is easy to agree with and remarkably hard to obey. What follows is what it looks like when you don't, and then what it looks like when you stop.
The Sprint Goal these three meetings are steering toward
“Enable new BCA members to securely create an account, log in, and establish their initial identity with a display nickname within the app.”
Day 4 — everything goes through the Scrum Master
Read that back and say what's wrong with it.
It's friendly. It's on topic. It finishes in twelve minutes. Every question asked was a good question.
And every single word goes through the Scrum Master.
He calls on Hans. Hans answers him. He acknowledges, then calls on Greta. Greta answers him — though watch her slip one sentence sideways to Hans about the error codes, which is the only genuinely useful exchange in the entire meeting, and the only one he didn't cause.
This is the most common Scrum Master mistake there is, and it doesn't feel like a mistake at all.
It feels like facilitation. The team is talking. The meeting is efficient. Nobody's unhappy.
What's actually happening is that two developers are quietly learning that alignment is something the Scrum Master does for them.
It ran like this for four consecutive days.
Day 5 — what changed
One sentence at the start, and then silence.
This is your meeting. I'm here to hear about impediments.
Day 8 — the team runs it, and the impediment surfaces
Same fifteen minutes. Entirely different meeting.
They're planning against each other now instead of reporting upward. Hans re-plans his day inside the meeting based on what Greta just told him. They schedule their own follow-up without asking permission.
And the only thing that comes to the Scrum Master is the one thing he can actually do something about.
That last line is what a Daily Scrum is for. Everything before it was the team managing itself. The impediment surfaced because there was room for it — not because anyone asked a question that went fishing.
What the three meetings show
| Day 4 | Day 5 | Day 8 | |
|---|---|---|---|
| Who speaks first | Scrum Master | SM once, then silence | Developers |
| SM turns | 3 of 5 | 1 of 6 | 0 of 6 |
| Dev-to-dev exchanges | 1, sideways | 1 design decision | Continuous |
| Re-planning in the meeting | None | None | Yes |
| Impediments raised | None | None | One, to the right person |
The developers did not become more capable over four days. The room made space for capability that was already there.
Impediment or problem?
Greta raised two things across those transcripts and only one of them was for the Scrum Master. Telling them apart is most of the job.
| Impediment | Something blocking the team that the team cannot resolve itself. A missing licence. An unresponsive vendor. A decision belonging to somebody with authority the team doesn't have. |
| Problem | Something hard that the team can solve. A failing test. An architecture disagreement. A tricky bug. |
Greta's database connection pool was a problem, and she had already solved it by the time she mentioned it. The missing email provider was an impediment, because the decision sat outside the team.
A Scrum Master who solves problems steals learning. A Scrum Master who ignores impediments wastes the team's time.
Get it wrong in either direction and you damage the team.
On the structure
The “yesterday / today / blockers” round is not required by Scrum. It was removed from the Guide in 2020, precisely because it turns the event into a reporting ritual.
Developers may use any structure they like, as long as it focuses on progress toward the Sprint Goal. The Day 8 transcript has no structure at all. That is allowed, and it is working.
What happened to the impediment
It reached the Scrum Master on day eight and he did not clear it. Not because he forgot — because chasing a provider decision through procurement felt less urgent than the things in front of him that week.
Surfacing an impediment is not the same as clearing it. What that one cost is in chapter 1, free to read.
Where this sits
The Daily Scrum steers a Sprint between Planning and the Review. The dependency Greta raised had already failed the Definition of Ready before the Sprint started — the Daily Scrum is where it became visible again, with most of the Sprint spent.