The Standup Is Not a Status Report

I have observed hundreds of standups across different teams and organizations. The most common failure mode is the same everywhere: the standup becomes a status report to the PM or Scrum Master. Everyone takes turns reciting what they did yesterday. Nobody listens to anyone else. The whole thing takes twenty minutes and adds zero value.

Why This Happens

Teams default to status reporting because it is safe. Saying "I worked on ticket PROJ-1234 yesterday and will continue today" requires no vulnerability. It does not expose blockers, uncertainties, or the fact that you have been stuck on the same problem for two days. The round-robin format makes it easy to hide.

What a Good Standup Looks Like

The best standups I have facilitated focus on three things: what is at risk of not getting done this sprint, who needs help from someone else on the team, and what information does the team need to share to coordinate effectively. That is it.

I stopped asking "what did you do yesterday" two years ago. Instead, I ask "is anything blocking your progress toward the sprint goal" and "does anyone need something from another team member today." These questions surface real information instead of performative updates.

The Walking-the-Board Approach

For teams using Kanban or a visual board, walking the board from right to left is the most effective standup format I have found. Start with items closest to done. Focus on what needs to happen to get them across the finish line. Then move left. This approach naturally prioritizes finishing work over starting new work, which is exactly the behavior you want.

The Test

If your standup could be replaced by a Slack bot that posts everyone's Jira activity, it is not adding value. A good standup creates coordination that cannot happen asynchronously. That is the bar.