What the Daily Scrum is for
The Daily Scrum exists so the Developers can inspect progress toward the Sprint Goal and adapt the Sprint Backlog for the next working day. That is the whole purpose. Everything else people attach to it, reporting, coordination with managers, task assignment, is bolted on.
It is held at the same time and place every working day to remove the overhead of deciding when to meet. It is timeboxed to 15 minutes regardless of team size or Sprint length.
Who owns it
The Developers. The Product Owner and Scrum Master attend only if they are working on Sprint Backlog items, and then they attend as Developers rather than as observers with opinions.
The Scrum Master's accountability is that the event happens, stays positive and productive, and finishes inside its timebox. Teaching the team to run it without them is the job. A Scrum Master still chairing it after six months has not finished the job.
The three questions are optional now
The 2020 Scrum Guide removed the prescribed format. What did I do yesterday, what will I do today, what is in my way was guidance, and it was quietly turning the event into a round of individual status updates.
Any structure is allowed provided it produces a plan for the day that moves the Sprint Goal forward. Many teams get better results by walking the board right to left, discussing the work rather than the people, and stopping the moment the plan is clear.
Six anti patterns worth spotting
- Reporting upward. Everyone addresses the Scrum Master or a manager instead of each other. The plan never gets made because nobody is planning.
- Person by person. Going around the circle means the Sprint Goal is never mentioned. Walk the board instead.
- Solving in the room. A two person debate consumes ten minutes. Note it, park it, take it offline immediately afterwards.
- Silent blockers. People withhold impediments because raising them has previously been treated as a performance issue.
- Skipping when busy. The days the team feels too busy to replan are precisely the days the plan is wrong.
- Attendance creep. Stakeholders join to get an update, and the Developers start performing rather than planning.
Practise the judgement calls
Most Daily Scrum problems are not process problems, they are courage problems. Someone has to say the Sprint Goal is now unreachable, or that a colleague has been blocked for three days without saying so.
The Scrumling simulator puts those exact moments in front of you, scores the call you make against the 2020 Scrum Guide and explains why. It takes minutes and it is free.
Frequently asked questions
What is the Daily Scrum?
A 15 minute event for the Developers, held at the same time and place every working day of the Sprint. Its purpose is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog for the next 24 hours. It is a planning event, not a status meeting.
Who attends the Daily Scrum?
The Developers own it and are the only required attendees. The Scrum Master and Product Owner attend only as Developers when they are actively working on Sprint Backlog items. Others may observe, but the event belongs to the Developers.
Are the three questions still required?
No. The 2020 Scrum Guide removed the mandatory what did I do, what will I do, what is blocking me format. Teams may use any structure they like as long as it inspects progress toward the Sprint Goal and produces an actionable plan for the day.
Why is the Daily Scrum limited to 15 minutes?
The timebox forces the conversation to stay on replanning rather than problem solving. Detailed discussions are taken offline immediately after, often as an informal follow up with only the people involved.
Does the Scrum Master have to run the Daily Scrum?
No. The Scrum Master ensures the event happens, is positive and productive, and stays within the timebox, but the Developers run it. A Scrum Master who chairs it every day is usually the reason the team treats it as a status report to management.
What are the most common Daily Scrum anti patterns?
Reporting to the Scrum Master or a manager instead of to each other, walking the board person by person rather than working toward the Sprint Goal, solving problems inside the timebox, and skipping it whenever the team feels busy.
Can the Daily Scrum be asynchronous?
A written thread can carry the information, but it rarely produces the plan. Distributed teams get better results from a short synchronous call plus an async written summary for people in other time zones.