The Daily Scrum That Runs 40 Minutes
A Scrum Master joins a team whose Daily Scrum lasts 40 minutes. Each of the seven Developers gives a detailed status update to the Scrum Master, who takes notes and then assigns follow-up tasks. Two Developers dominate; a third has not spoken in three days. The Scrum Master also uses the meeting to chase blockers and update the burndown chart. Developers say the meeting feels like a reporting obligation to management. The team is distributed across two time zones, and two members join by video while five sit in a room.
1. What is wrong with this Daily Scrum, and what is the Scrum Master's accountability here?
Read the worked answer
The Daily Scrum is for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog; it is not a status report to the Scrum Master or to management. Here it has been captured by the Scrum Master, who takes notes, assigns tasks, and uses it for burndown administration - turning a self-management event into a reporting ritual.
Problems:
- The Scrum Master is directing work rather than the Developers self-organizing.
- 40 minutes for seven people signals detailed problem-solving inside the event.
- Dominant voices crowd out others; the silent Developer is a warning sign.
- The distributed setup is not being handled deliberately.
The Scrum Master is accountable for teaching the team and organization to keep the event focused, self-managed, and within its 15-minute timebox, and for coaching the Developers to own it.
2. How should the Scrum Master address the two Developers who dominate and the one who never speaks?
Read the worked answer
The Scrum Master should not simply police airtime in the meeting; the goal is to help the Developers self-manage the event. Options:
- Coach the Developers to structure the Daily Scrum around progress toward the Sprint Goal rather than round-robin status, which naturally shortens and focuses contributions.
- Encourage the team to agree on how they will ensure all voices are heard - e.g., walking the board together, or having the quiet Developer speak first.
- Privately check in with the silent Developer to understand whether there is a blocker or a psychological-safety issue.
- Model and reinforce that the event belongs to the Developers, so the Scrum Master steps back from note-taking and task assignment.
3. What should the Scrum Master do about the two time zones and the video participants?
Read the worked answer
The Scrum Master should help the team remove the impediment of an unequal meeting. When some members are co-located and others remote, the remote members are disadvantaged: side conversations, hard-to-hear discussion, and a sense that decisions happen in the room.
Practical steps: have everyone join individually from their own device so no one is a second-class participant; use a shared visual board that all can see; rotate the time if the current slot unfairly burdens one time zone; and coach the team to explicitly invite remote input. The Scrum Master's accountability is to the team's effectiveness, and an event that systematically excludes half the team is an impediment to be addressed, not tolerated.