Daily standups: purpose and anti-patterns

The Daily Scrum exists so the Developers can re-plan their own next 24 hours and surface blockers to each other — it is a team-to-team synchronization, not a status update delivered upward to a manager or Scrum Master. This single fact explains most of what separates a useful standup from a dreaded one: a meeting where people report progress to the Scrum Master has quietly become a status meeting with extra steps, even if it's still called a standup and still happens at 9am on schedule.

The classic three questions ("What did I do yesterday? What will I do today? What's blocking me?") are a useful prompt for keeping the meeting short and focused, not a script to be recited mechanically by every person in turn while everyone else waits their turn to speak. A standup that's just fifteen sequential monologues, each one addressed to the room in general rather than sparking any actual coordination, has kept the format and lost the function.

A better frame for the same three questions: is the sprint goal still on track, and does anything need to change about today's plan to keep it that way? That reframing naturally surfaces the actually-useful information (a blocker two people can solve together right after the meeting, a task that turned out bigger than expected and needs rebalancing) instead of a flat recitation of yesterday's ticket IDs.

Named for the literal physical posture — standing up is meant to create mild discomfort that keeps the meeting short, historically around 15 minutes. A standup that regularly runs 30+ minutes, with everyone seated, has usually also drifted into solving problems live in the meeting rather than surfacing them and taking the actual solving offline. The fix isn't usually "enforce standing" as a rule — it's noticing that problem-solving discussions belong in a follow-up conversation with just the people involved, immediately after standup, not in the full-team sync itself.

If a Scrum Master or lead is actively assigning tasks during the standup ("okay, you take the API work, you take the frontend"), that's a signal the actual planning — deciding who's doing what — never really happened during Sprint Planning, and the standup has become the place where planning is quietly still happening every single day instead of once per sprint. A healthy team self-organizes around who picks up what, adjusting day to day as needed, without a manager-style dispatcher making that call live in the sync.

For distributed teams across time zones, a synchronous 9am meeting may not be practical for everyone. An asynchronous standup — each person posts their three answers to a shared channel by a deadline, everyone reads at their own convenience — can work well, if the team is disciplined about actually reading and reacting to what's posted (following up on a flagged blocker, noticing a plan needs adjusting) rather than treating it as a box-checking ritual nobody actually reads. The failure mode to watch for isn't the async format itself — it's a channel that fills with daily updates nobody engages with, which has all the cost of a status-report standup with none of even the synchronous version's forced attention.

A useful diagnostic for whether a team's standup is working: after the meeting ends, could you say specifically what changed about today's plan as a result of it? If the answer is consistently "nothing, it's the same plan as before the meeting," the standup isn't doing its job — the meeting's whole reason to exist is exactly that re-planning, not the ritual of speaking three sentences in turn.