Daily Scrum: Make It Useful, Not a Status Report
The Daily Scrum is for Developers to plan their next 24 hours of work to achieve the Sprint Goal. It is not a status meeting for managers.
Many teams treat the Daily Scrum as a status report. Each Developer states what they did yesterday, what they will do today, and any impediments. This often leads to disengagement. The Daily Scrum is a planning event for the Developers, not a progress update for others. Its purpose is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary. If your Daily Scrums feel like a chore, it is time to change how you approach them.
Focus on the Sprint Goal
The Scrum Guide states the Daily Scrum's purpose plainly: to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. This means the conversation should revolve around the Sprint Goal. Developers should discuss what they need to do collectively to achieve it. Instead of individual status updates, think about the team's shared objective. What is the most important thing for us to work on today to get closer to the Sprint Goal? This shift in perspective makes the meeting far more productive.
The Three Questions are Not Mandatory
The 2020 Scrum Guide removed the prescriptive three questions. While they can be a useful starting point for new teams, they are not a rule. The Developers can select any structure and techniques they want, as long as it facilitates their planning for the next 24 hours. Some teams might walk the board, discussing each item in progress. Others might focus on dependencies or risks. The key is that the Developers decide what works best for them to achieve the Sprint Goal.
Developers Own the Meeting
The Daily Scrum is for the Developers. The Scrum Master ensures the event takes place and that Developers understand its purpose. They do not run the meeting. The Product Owner may attend, but their role is generally to listen, not to direct. Managers from outside the Scrum Team have no role in this event. When Developers take ownership, they tailor the discussion to their needs. This self-management is crucial for an effective Daily Scrum.
Timebox and Follow Up
The Daily Scrum is strictly timeboxed to 15 minutes. This forces brevity and focus. Any detailed discussions or problem-solving should happen immediately after the Daily Scrum, involving only the relevant people. For example, if two Developers identify a technical dependency, they should schedule a separate, short meeting to resolve it. The Daily Scrum itself is a planning sync, not a problem-solving session. Sticking to the timebox keeps the meeting efficient for everyone.
Signs of a Useful Daily Scrum
A truly useful Daily Scrum results in clear benefits for the team. You will notice these outcomes:
- Developers leave with a clear plan for the day's work.
- Dependencies between team members are identified and addressed.
- Impediments are surfaced, and steps for removal are discussed.
- The team's collective progress toward the Sprint Goal is understood.
- The Sprint Backlog is adapted to reflect new information or decisions.
If your team is not seeing these results, it is time to inspect and adapt your Daily Scrum practice. Talk to the Developers. Ask them what they need from this event. Experiment with different approaches. The Daily Scrum is a vital inspection and adaptation point for the Developers. Make sure it serves its purpose.