The Standup Nobody Talked In: A Scrum Master Learns to Facilitate
A new Scrum Master — call her Dana — inherited a five-person development team that had gone fully remote in 2020 and stayed that way. On paper everything looked fine: the team held all the events, the board was current, velocity was steady. But the meetings were lifeless. In the Daily Scrum, people read their cards in a monotone and went silent. Retrospectives produced the same two complaints every fortnight and no real change. Dana's first instinct was to push harder — to assign action items and chase them. It made things worse. The team grew quieter, and she started to wonder if remote work had simply killed the conversation.
It hadn't. The problem was that Dana was managing the meetings instead of facilitating them. The Scrum Guide describes the Scrum Master as a true leader who serves the team — and a large part of that service is facilitation: creating the conditions for the team to think and decide well together. That is a skill, not a personality trait, and Dana had never been taught it.
Facilitation is not running the meeting — it is enabling the team
A facilitator does not supply the answers or carry the conversation. They design the interaction so the right conversation happens among the people who own the work. The shift sounds small but changes everything: the Scrum Master stops being the centre of the room and becomes the person who makes the room work.
Dana made four changes, none of them dramatic.
She stopped going round the screen. The card-by-card report had turned the Daily Scrum into status theatre for her benefit. She reframed it around the Sprint Goal: what is in the way of us hitting it, and who needs help today? The Daily Scrum is the developers' meeting to plan their day, not a report to the Scrum Master.
She built in silence and writing. In retrospectives, two minutes of silent written reflection before anyone spoke gave the quieter members something to point to and broke the loudest-voice-wins pattern that remote calls amplify.
She asked open questions and waited. Instead of "any blockers?" (which always gets "no"), she asked "what slowed you down yesterday?" and then held the silence long enough for a real answer to surface.
She made the team own the outcome. Each retrospective ended with one improvement the team chose, owned, and pulled into the next Sprint — not a list she assigned and policed.
What changed, and why it held
Within a few Sprints the Daily Scrum became a planning conversation again; people offered help instead of reciting status. Retrospectives surfaced a recurring handoff delay the team had been quietly absorbing for months, and they fixed it themselves. Crucially, Dana did less talking, not more. Good facilitation is often invisible — when it works, the team feels like it solved the problem on its own, because it did.
Authority makes people comply; facilitation makes them contribute.
Silence and written input level the floor on remote and hybrid calls.
Open questions plus patience beat checklists for surfacing real issues.
When the team owns the improvement, it actually happens.
Facilitation is one of the most underrated parts of the Scrum Master role and one of the most learnable. The teams that get unstuck are rarely the ones with the strictest process; they are the ones whose Scrum Master learned to get out of the way at the right moments.
If your agile events have gone quiet and your retrospectives change nothing, XNM's program & project delivery advisory can help your Scrum Masters build real facilitation skills.