Origins
The Daily Scrum was specified in early Scrum descriptions as a 15-minute daily team event focused on inspect-and-adapt. The classic format asked each team member to answer three questions: What did you do yesterday? What will you do today? What's blocking you?
The 2020 Scrum Guide explicitly removed the three-question format. The current guide describes the Daily Scrum's purpose as the Developers' opportunity to inspect progress toward the Sprint Goal and adapt their plan — without prescribing how to do it. The change reflected a recognition that the three questions had become anti-pattern in many teams — producing rote status reports rather than the planning the event was supposed to enable.
What the Daily Scrum Is For
Two specific purposes:
- Inspect progress toward the Sprint Goal: are we on track to hit what we committed to?
- Adapt the plan for the day: based on what we now know, what changes about who's doing what?
Things the Daily Scrum is not:
- Status reporting to the Scrum Master or manager.
- Per-person accountability theater.
- A meeting where stakeholders interrogate the team.
- A problem-solving meeting (those happen after, with the relevant people).
The Three Questions (and Why They Often Fail)
The original three-question format — yesterday, today, blockers — works when used as a conversation prompt. It fails when used as a script.
Common failure modes:
- Each person reports to the Scrum Master, who nods, then the next person reports. The team isn't actually inspecting or adapting; they're performing for the facilitator.
- People list everything they touched yesterday in irrelevant detail.
- Blockers go unaddressed because the meeting moves on too fast or because addressing them would derail the format.
- The same format runs every day for years; the team stops paying attention.
Better Formats
Walk the Board
Start at the right side of the board (work closest to done) and walk left. For each item: what's needed to move it forward? Who's on it? Anything blocking it? The format anchors on work rather than people, surfaces blockers naturally, and matches the priority of finishing started work over starting new work.
Focus on Blockers and Aging Items
Skip status. Open with: "What's blocked, and what's been sitting for too long?" Address those items; everything else stays implicit. Especially useful for mature teams whose status is visible on the board.
Sprint Goal Check-In
Each person says one thing about the Sprint Goal — are we on track? What might prevent us hitting it? What needs to change? The goal-orientation pulls the conversation away from individual tasks.
Swarm Standup
For teams doing mob or paired work. "Where did we get to yesterday? What's the plan for today's swarm? What needs the team's collective attention?" Single-track conversation; no per-person reporting.
Three Questions (Reframed)
If you keep the three questions, reframe them around the goal: What did I do to move the Sprint Goal forward yesterday? What will I do today? What might prevent me from contributing? The frame keeps the questions useful.
What Makes Any Format Work
- Held by the team, for the team: not for managers, not for stakeholders. Outside attendance is fine but as guests, not principals.
- Time-boxed to 15 minutes: hard cap. Discussion that exceeds the box moves to a follow-up meeting after.
- Standing: literally or virtually. The standing format makes long meetings uncomfortable, which keeps them short.
- Same time and place every day: predictability matters. Different time every day kills attendance and energy.
- Action-oriented output: every Daily Scrum should produce decisions about who's doing what next, not just status updates.
When to Change the Format
- The same format for months: rotation prevents the meeting from becoming wallpaper.
- Status reporting creeping in: the format has slid into "what I did yesterday" theater. Switch to walk-the-board.
- Blockers piling up: focus on blockers and aging work for a few sprints.
- Sprint Goal getting lost: Sprint Goal check-in format pulls attention back.
- Team feels disengaged: try a new format; sometimes attention just needs the change.
Common Pitfalls
- Status reports to manager: the most common failure. The meeting becomes daily reporting; the team disengages.
- Problem-solving in the standup: a blocker surfaces; the team spends 20 minutes debugging it together. Push problem-solving to a follow-up with just the relevant people.
- Skipped when "nothing to report": the meeting's purpose is plan adjustment, not reporting. Even days when "nothing's new" benefit from the brief sync.
- Time creep: 15 minutes becomes 25, then 40. Once it grows it stays grown. Cut hard at 15.
- Same time forever: a Daily Scrum that doesn't match the team's actual rhythm produces resentment. Match time to when the team is genuinely starting work, not arbitrary calendars.
- Wrong attendees: stakeholders who want to "check in on progress" attending daily. The format becomes performance for them.
Coaching Tips
Walk the Board
The single most effective shift for teams stuck in status reporting. Start at the right side of the board and walk left, item by item.
Defend the 15 Minutes
Time creep is the most common drift. Cut hard at 15; push remaining discussion to a follow-up with relevant people.
Push Problem-Solving After
A blocker surfaces; team starts debugging together. Stop the conversation, schedule a 30-minute follow-up with the relevant people, continue the standup.
Watch the Audience
If managers attend regularly, the meeting becomes status theater. Coach the boundary — the standup is the Developers' event.
Rotate Format Quarterly
Even good formats become wallpaper. Try a new format every quarter or two to keep the meeting alive.
End with Decisions
Every standup should produce at least one decision — who's doing what, what to escalate, what to swarm. Standups without decisions are reports.
Summary
The Daily Scrum is one of the most-attended and least-loved Agile events. Its potential is real — a fast daily sync that keeps the team coordinated and surfaces blockers early — but the format has to fit the purpose. The three-question default that became standard in early Scrum implementations produced rote status reporting in too many teams; the 2020 Scrum Guide's removal of the prescribed format was overdue recognition.
The honest practice is choosing the format that produces what the meeting is for: plan adjustment, not status. Walk the Board, blocker focus, Sprint Goal check-in — each works in different team contexts. Rotation prevents any format from becoming wallpaper. The 15-minute box keeps the meeting honest. Done well, the Daily Scrum is one of the highest-leverage 15 minutes in the team's day; done as the textbook three-question recital, it's a daily tax on team energy.
- Schwaber, K., & Sutherland, J. (2020). The 2020 Scrum Guide. scrumguides.org.