My team's Daily Scrum is turning into a 30-minute status report for me, rather than a 15-minute synchronization for the developers. How can I shift the focus back to the team so they collaborate on the Sprint Goal instead of just listing what they did yesterday?
3 answers
The biggest mistake is the Scrum Master standing at the front taking notes. Try physically (or virtually) stepping back. Remind the team that the Daily Scrum is for the developers. Instead of the "three questions" (What did I do, what will I do, any blockers), try "Walking the Board." Start from the items closest to "Done" and ask, "What do we need to do to get this item over the line today?" This naturally focuses the conversation on finishing work and meeting the Sprint Goal. If a technical deep-dive starts, use a "parking lot" to defer that conversation until after the 15-minute time-box is over.
Melissa, "Walking the Board" sounds great for workflow, but what if the team is working on unrelated tasks because the stories were poorly decomposed? If there is no shared goal, won't they just revert to individual status updates anyway because their work doesn't actually overlap?
Don't forget the PR value. Being one of the few brands in your niche offering a polished AR experience can earn you significant organic reach and "earned media" from tech blogs.
That is a perfect suggestion, Robert. It builds leadership within the team and reinforces the idea that the meeting belongs to them, not the Scrum Master or the PM.
Brandon, you’ve identified a deeper issue: a weak Sprint Goal. If the team feels like they are just working on a random list of tickets, the Daily Scrum will always fail. As a Scrum Master, you need to challenge the Product Owner during planning to define a single, cohesive objective. When everyone is focused on one goal, the collaboration during the stand-up happens naturally because they actually need each other to succeed.