The daily scrum: how to keep standups short, honest, and worth having

The daily scrum is the most frequently held Scrum event and the most frequently ruined one. Done well, it is a fifteen-minute course correction that saves hours of drift. Done badly, it is a daily status trial where twelve people wait their turn to prove they were busy yesterday.

The difference is not energy or discipline. It is understanding what the meeting is for.

What the daily scrum is actually for

The daily scrum has one purpose: the Developers inspect progress toward the Sprint Goal and adapt the plan for the next twenty-four hours. It is a planning meeting, not a reporting meeting. The audience is the team itself, not a manager, and the output is a slightly better plan for today than the one you had yesterday.

That framing answers most of the common questions:

• Who speaks? The Developers. The Scrum Master and Product Owner may attend, and often usefully do, but the meeting belongs to the people doing the work.
• How long? Fifteen minutes, hard stop, regardless of team size. The timebox is a design feature: it forces the meeting to surface topics rather than resolve them.
• When and where? Same time, same place, every working day. The consistency removes a daily scheduling negotiation and builds the rhythm the sprint runs on.

Why the three questions were retired

For years, most teams ran the standup on three questions: what did I do yesterday, what will I do today, what is blocking me. The 2020 Scrum Guide removed them, and it is worth understanding why, because the reason explains most bad standups.

The three questions quietly change the meeting's subject from the work to the workers. Each person accounts for their individual time, in sequence, to the room. Three predictable things follow. People stop listening between their turns. Answers optimise for sounding busy rather than being useful. And the one question that matters, "will we hit the Sprint Goal, and what should change today if not", never gets asked at all.

A team we worked with had a twelve-person standup that ran twenty-five minutes and had visibly become a ritual: eleven people on mute while the twelfth recited yesterday. They changed one thing, described below, and the meeting dropped to nine minutes while becoming the most useful slot in the day. Nobody worked harder. The meeting just changed subject.

Walk the board, not the room

The single highest-leverage change for most teams: stop going around the people and start going around the work.

Put the sprint board on the screen. Start from the right-most column, because work nearest to done carries the most invested effort and the most risk, and walk left, ticket by ticket:

• "This one is in review since Tuesday. Who can pick up the review today?"
• "This one has not moved in three days. What does it need?"
• "This one is blocked on the vendor. Any word? Should we swarm on something else and park it?"

Then one closing question: "Given all that, are we still on track for the goal, and is today's plan right?"

Why this works:

• Silent work becomes visible. A ticket that has not moved is awkward to skip when it is literally on screen, whereas a person can narrate around it indefinitely.
• It rewards finishing over starting. Walking right to left keeps the team's attention on getting things out the door, which is where sprints are actually won.
• People with nothing relevant say nothing, which is fine, and the meeting is shorter for it.

The prerequisite is that the board is true. If people batch-update tickets in the minutes before standup, the board is a daily reconstruction rather than a live instrument, and the meeting inherits the lag. This is where a real-time tracker pays for itself: in WannaTrack the board updates for everyone the instant a ticket moves, and pull request state from GitHub shows on the ticket itself, so "in review, since when, by whom" is a fact on screen rather than a memory someone has to produce out loud.

Blockers: surface, then leave

The standup surfaces blockers; it does not solve them. The moment two people start designing a fix, the other six are hostages. The standard move is the "sixteenth minute": note who needs to talk, finish the walk, close the meeting, and let those two stay on while everyone else leaves. Protecting the timebox this way is the classic Scrum Master job in this meeting.

The other half of blocker discipline is follow-through. A blocker mentioned at standup and forgotten by lunch was never really raised. Make blockers visible artifacts rather than spoken ones: flag the ticket, name an owner for the unblock, and check it first tomorrow. Teams running several projects have a wider version of this problem, where a blocker in one team quietly stalls another; that cross-team view is what a portfolio roll-up like WannaTrack's is for, so a dependency between teams is a visible red flag rather than a surprise in week two.

Remote and async standups

Distributed teams have two honest options.

Synchronous over video works with the same rules and one addition: screen-share the board, always. A remote standup without a shared board degenerates into radio, and radio standups drift back to the three questions within a fortnight.

Async works when time zones make a shared quarter-hour impossible, but be honest about the trade. Posting three bullet points into a channel keeps the reporting function of a standup and loses the planning function, which was the point. If you go async, structure it around the same two questions the live version answers: what changed on the board since yesterday, and is the goal at risk. A live board with notifications does the first part automatically, watchers on a ticket hear about movement without anyone writing a digest, so the humans only need to write the judgement call, not the inventory. Many distributed teams land on a hybrid: async on most days, one synchronous standup mid-sprint, and an agreement that anyone can call a live huddle when the async thread starts going in circles.

Anti-patterns and their fixes

The manager's report. A lead or stakeholder attends, and the meeting silently reorients toward them; people speak to the most senior person in the room instead of to each other. Fix: the observer stays silent, questions wait for after, and if that fails, the observer stops attending. The reporting need is real but belongs in a different channel, ideally a live dashboard rather than a meeting at all.

The status séance. Each person reconstructs yesterday from memory in long narrative form. Fix: walk the board; the board already knows what happened yesterday.

The stale board standup. The first five minutes are people moving tickets to reflect reality before discussion can start. Fix: the working agreement is that the board is updated as work happens, not before the meeting. Real-time tooling makes this nearly free.

Problem-solving creep. Two engineers deep-dive an issue while everyone waits. Fix: the sixteenth minute, enforced kindly and every time.

The skipped standup. "We sit together, we talk all day anyway." Ambient chat is not inspection; it follows the interesting, not the important. The quiet stuck ticket is precisely the one ambient chat never finds. Fifteen structured minutes exists to catch what the hallway misses.

Goal amnesia. A technically tidy standup that never mentions the Sprint Goal. Ten fine standups can still add up to a failed sprint if nobody asks the steering question. Keep the goal pinned above the board and end on it explicitly: on track or not?

A note on the burndown

The daily scrum is also the natural moment to glance at the sprint's instruments, and the burndown chart earns its keep here. Four days of flat line while the board looks busy means work is starting but not finishing, which is the earliest visible symptom of trouble, oversized tickets, hidden blockers, or too much work in progress. Because WannaTrack recomputes the burndown the instant tickets change, the chart at standup always agrees with the board behind it, so the team can argue about what to do rather than whose numbers are right.

Fifteen minutes is a small price for a daily answer to the only question that matters mid-sprint: are we still on course, and if not, what changes today? Get that answer honestly every morning and the sprint review at the end of the sprint stops being a surprise, which is exactly what the next guide covers.