The Two Approaches
The traditional Scrum daily standup uses the three questions: what did I do yesterday, what will I do today, what's blocking me? Each person answers in turn. The format produces a complete status sweep across the team in fifteen minutes.
The flow-based alternative — sometimes called walking the board — starts at the right side of the board (closest to done) and works left, focusing on what's stuck, what's aging, and what needs to move. People speak about work, not about themselves.
Both formats are technically Scrum-compliant (the Scrum Guide does not actually mandate the three questions). The disagreement is about what the standup is for.
The Case for Three Questions
- Predictable, learnable structure. New team members know exactly what's expected.
- Equal voice by design. Every person speaks. Quiet team members don't get skipped.
- Surfaces individual blockers reliably. The "what's blocking me?" prompt forces the question every day.
- Useful in remote settings. The round-robin works well when video latency makes ad-hoc conversation harder.
How Three Questions Goes Wrong
- Status report to the Scrum Master. People speak to the SM or the room generally, not to each other. The standup becomes a check-in, not a coordination.
- "Yesterday I worked on Jira-3421" with no context. The format produces compliance, not communication.
- Doesn't surface aging work. An item that's been "in progress" for two weeks gets re-reported as in-progress without anyone noticing the age.
- Inflates with team size. Seven people answering three questions, even briefly, is twenty-one mini-reports. The format scales poorly past five.
The Case for Flow-Based Standup
- Work-centric, not person-centric. The conversation is about items on the board, not about what individuals did yesterday.
- Aging surfaces immediately. Walking right-to-left, the oldest items in progress are the first thing discussed.
- Right-side bias. Items closest to done get attention first, which encourages finishing rather than starting.
- Surfaces system-level issues. A column with five items aging — review backlog, test queue — becomes visible in a way the three questions cannot expose.
How Flow-Based Standup Goes Wrong
- Quiet voices skipped. Without a round-robin, people whose work isn't on the board don't get heard.
- Requires a board the team trusts. If the board is out of date, the standup becomes a board-update meeting instead of a coordination.
- Coaching dependency. Walking the board well requires a facilitator who knows what to look for — aging, WIP limits, swarming opportunities. Without that skill, the format drifts.
- Blockers can be missed. Without an explicit "blockers" sweep, individual obstacles may go unsurfaced if they're not visible on the board.
The Hybrid That Works
Most healthy teams converge on a hybrid:
- Walk the board from right to left, item by item.
- For each item: what's needed to move it forward?
- Surface aging items explicitly — "this is on day four; what's blocking?"
- End with a quick round: anything else not on the board?
- Total time: still 15 minutes.
This hybrid preserves the work-centric focus of flow standup while keeping the safety net of "anyone got something not visible?" that the three questions reliably provided.
What the Standup Is Actually For
The deeper question this debate hides: what should the team accomplish in fifteen minutes together each day? Two reasonable answers:
- Coordinate today. Identify blockers, find swarming opportunities, decide who pairs with whom. Tactical.
- Sense the sprint. Notice whether the sprint is on track, whether aging work is piling up, whether the goal is still reachable. Strategic.
Three questions tends to optimize for the first. Flow-based tends to surface the second. The right format depends on what the team most needs to do daily. If the team is well-coordinated but losing the bigger picture, switch to flow. If the team is losing each other's threads, switch to three questions.
Coaching Tips
Walk the board from right to left.
Start with what's almost done. The bias toward finishing changes how the team thinks about the day.
Watch aging explicitly.
"This is on day five — what's the plan?" Aging visibility is the single most useful flow-standup signal.
Add a closing safety round.
"Anyone got something not visible on the board?" catches what work-centric format misses.
Don't speak to the Scrum Master.
If the team faces the SM rather than each other, the format has decayed into status reporting. Rearrange the room.
Time-box ruthlessly.
Fifteen minutes max. The standup is a coordination point, not a meeting.
Park deep dives.
"Let's take that after standup." A two-person conversation is not a fifteen-person agenda item.
Summary
The daily standup debate is really about whether to coordinate around people or around work. Three questions makes people the unit; flow-based makes the board the unit. Healthy teams use both signals — work-centric for most of the meeting, person-centric as a safety check at the end. The point of the standup has always been to make the day better, not to comply with a format. The teams that remember that adjust the format to fit; the teams that don't end up running a ritual everyone tolerates.
- Schwaber, Ken and Jeff Sutherland. The Scrum Guide. 2020.
- Anderson, David J. Kanban. Blue Hole Press, 2010.
- Yip, Jason. "It's Not Just Standing Up: Patterns for Daily Standup Meetings." Martin Fowler's blog, 2016.