Daily Standup

The daily standup, also called the daily Scrum, is a short daily meeting for the development team. Its purpose is coordination, not reporting. The team gathers briefly to inspect progress toward the sprint goal, identify anything blocking that progress, and adjust their plan for the day accordingly.

The Scrum Guide specifies a 15-minute time box. That limit is not arbitrary, it is structural. The 15-minute constraint forces the meeting to stay focused on what matters at the team level and pushes anything requiring deeper discussion into a separate conversation. The standup is where you discover you need to talk, not where you have the talk.

Standups are held at the same time and place every day of the sprint. Consistency matters here. When the standup time shifts around, team members cannot build the routine around it, and attendance becomes unreliable. Same time, same virtual room or physical space, every working day.

The standup is for the development team. The Scrum Master attends as a facilitator and to remove impediments. The Product Owner attends as a team member but should not turn the meeting into a status briefing for themselves. Stakeholders and managers may observe but should not participate — their presence changes team behavior in ways that undermine the meeting's purpose.

Instead of going person by person through the three questions, some teams walk their sprint board from right to left, meaning from "Done" toward "To Do." The team discusses each active ticket: where is it, is it blocked, what needs to happen next?

Walking the board focuses the standup on work items rather than individuals. It naturally surfaces items that have been sitting untouched, identifies tickets with no clear owner, and keeps the conversation grounded in the sprint goal rather than personal task lists. Teams that use Kanban or Kanban-influenced Scrum often prefer this approach because it matches how they think about work.

The tradeoff is that walking the board can run longer than the three questions format for large boards. If your sprint board has 40 items in progress, walking each one in 15 minutes is not realistic. Limit the walk to items in active columns — anything in "In Progress" or "In Review" — and park everything in the backlog. Items that have been in the same column for two or more days get flagged automatically for discussion.

Some teams use a hybrid: walk the board first (5 minutes) to surface anything stuck or at risk, then do a quick round of blockers by person (5 minutes), and close with any announcements (2 minutes). This covers both work-centric and person-centric information within the time box.

The traditional standup is synchronous — everyone on a call or in a room at the same time. This works well for co-located or minimally distributed teams. For teams where every member is in the same or adjacent time zones, synchronous standups are generally worth the coordination cost because they enable real-time clarification and immediate blocker discussion.

Async standups involve team members posting their three questions in a dedicated Slack channel or tool at any point during a defined window, say between 9 AM and noon in each person's local time. No one needs to be online simultaneously. Async is particularly well-suited for teams with more than four hours of time zone difference, where a synchronous standup would require someone to join at 7 AM or 9 PM.

The real benefit of synchronous standups is the ability to notice things you cannot see in text: hesitation when someone says they are fine, side conversations that emerge after the meeting, or the energy in someone's voice when they say they are blocked. Async standups lose that signal. The best async setups compensate with a weekly synchronous touchpoint where the team reviews blockers together, even briefly.

The worst outcome is a synchronous standup that has become a performance. Team members show up, recite their three answers with no real information, and the meeting ends having achieved nothing. If your synchronous standup has devolved into ritual rather than coordination, either fix the facilitation or switch to async until you rebuild the habit.

Time zone distribution is the single most common reason standup formats break down for distributed teams. There is no perfect solution, but there are approaches that minimize the damage.

If your team must have a synchronous standup across a significant time zone spread, rotate the meeting time periodically so the inconvenience is shared. If it is always the person in Singapore who joins at 8 PM, you have created an unfair burden that builds resentment over time. Rotating quarterly, or setting up two meeting times when the gap is too large, distributes the cost more equitably.

For genuinely global teams, a hybrid model often works better than either pure sync or pure async. Team members in overlapping time zones meet synchronously, and those who cannot join post asynchronously with a time stamp. A designated person reads the async updates in the sync standup so everyone's information is present in the conversation.

Record your synchronous standup if team members frequently miss it due to time zones. A 10-minute standup recording is much faster to consume than a written summary because people can listen at 1.5x speed during their own morning. Keep recordings in a shared location that is easy to find, not buried in a chat thread.

Define clear expectations for async participants around response windows. If your async standup window is 9 AM to noon local time, communicate that blockers need to be posted by noon so the team has time to respond during overlap hours. Vague async norms lead to updates posted at end of day that no one reads until the next morning.

Remote standups have a unique failure mode: the illusion of presence. People are technically on the call but not genuinely engaged. Every tool and habit you build around the remote standup should work against passive participation.

Keep cameras on. This is not about surveillance. It is about social cues. When you can see your teammates, you are more inclined to pay attention, and they can see when you are confused, distracted, or have something to add. Text-only standups miss these signals entirely. Video is worth the bandwidth.

Use a digital board that is visible to everyone during the call. Screen-share your sprint board and walk tickets during the meeting rather than doing it from memory. This grounds the conversation in actual work items, prevents people from giving vague answers, and makes it immediately obvious when a ticket has been stuck for two days.

Designate a rotating facilitator role rather than having the Scrum Master run every standup. Rotation keeps the meeting from feeling like a top-down structure and builds facilitation skills across the team. The facilitator's job is simple: keep time, move through the team in order, note blockers, and enforce the parking lot.

Create a dedicated standup channel in your team chat tool. Post a summary of blockers and action items immediately after the meeting ends. Team members who missed the call can catch up in 30 seconds, and the blockers summary creates a lightweight accountability record that the Scrum Master can reference when following up on impediments.

For async standups, use a bot or structured message format so updates are consistent and scannable. A freeform Slack message is harder to parse than a structured update with clear Yesterday / Today / Blockers sections. Consistency in format means less cognitive load when the team reads each other's updates.