Standup meeting timer and how long standups should be

The daily standup is supposed to be the shortest meeting on your calendar. Fifteen minutes, tops. Three questions per person, quick updates, and everyone gets back to work. In practice, standups often drift past twenty or thirty minutes because there's no visible clock enforcing the limit, discussions go off-topic, and no one wants to be the person who cuts a teammate off mid-sentence.

A standup meeting timer changes the dynamic by making time visible to everyone. When the whole team can see a countdown, people naturally keep updates concise. There's no awkwardness in wrapping up because the timer is the authority, not any one person. The meeting ends when time is up, and deeper discussions move to follow-up conversations.

This guide covers how long a standup should actually be, how to time individual updates, common formats that work for both in-person and remote teams, and what to do when your standup has gotten out of control.

How long should a standup meeting be

The Scrum Guide recommends that daily standups last no longer than 15 minutes. This isn't arbitrary. Fifteen minutes is enough time for a team of 5 to 8 people to share brief updates (about 1.5 to 2 minutes each) with a small buffer for transitions and clarifications.

If your team has more than 12 people, a single standup will almost certainly exceed 15 minutes. Split into two groups by project area or function. Each group runs its own standup and shares a short written summary with the other.

Setting up a standup timer

The simplest approach is to set a single 15-minute standup timer for the entire meeting. Display it on a shared screen in the room, or share the link in your video call chat so remote participants can see it too. When the timer reaches zero, the standup is over.

Some teams prefer timing individual speakers instead. Set a 2-minute turn timer and reset it when each person finishes. This keeps any one person from taking too long and makes the time constraint feel fair because everyone gets the same amount.

For remote standups on Zoom or Teams, open the timer in a separate browser window. You can screen-share it during the standup, or simply keep it on your own monitor and announce time remaining at key moments. Either way, visibility is the key ingredient.

The three-question standup format

The classic standup structure gives each person three prompts: what did I finish since last standup, what am I working on today, and what's blocking my progress. Keeping updates to these three areas prevents stories from turning into long technical discussions.

If someone's update raises a question that needs a longer conversation, note it and schedule a follow-up. The standup isn't the place for problem-solving. It's the place for surfacing problems quickly so the right people can solve them afterward.

Teams that struggle with this boundary often benefit from a visible rule: "If the timer reaches the halfway mark and half the team hasn't spoken yet, move on." This simple guideline prevents the first few speakers from consuming all the time.

Why standups go off the rails and how to fix it

The most common reason standups run long is that they become status meetings. Instead of quick updates, people explain their work in detail, ask clarifying questions, and debate solutions in real time. The fix is cultural: the team needs to agree that standups are for surfacing, not solving.

• Problem: One person gives a 5-minute update. Fix: Use a 2-minute per-person timer and enforce it consistently.
• Problem: Side discussions start between two people. Fix: The facilitator notes the topic and says "Let's take that offline after standup."
• Problem: People arrive late and the standup restarts. Fix: Start the timer at the scheduled time regardless of who's present.
• Problem: The standup feels pointless. Fix: Focus on blockers, not activity reports. If nothing is blocked, keep updates to one sentence.

Standup formats beyond the classic three questions

Not every team works the same way, and the three-question format isn't the only option. Some variations that work well with a timer:

Walk the board

Instead of going person by person, walk through the work items on your Kanban board from right to left (closest to done first). Each item gets a quick status update from whoever is working on it. This keeps the focus on work progress rather than individual activity. Set the 15-minute timer for the whole walk-through.

Round robin with strict time

Each person gets exactly 90 seconds. When the timer sounds, the next person starts. No exceptions. This format is blunt but effective for teams that have struggled with long standups. After a few weeks, people naturally become concise because they know the clock will cut them off.

Async standups as an alternative

Some distributed teams find that synchronous standups don't work across time zones. In that case, written async standups (posted in Slack, Teams, or a shared document) can replace the live meeting. Even without a live timer, the same principles apply: keep updates to three sentences, flag blockers immediately, and save discussions for dedicated threads.

If your team does meet live but also works across time zones, keep the meeting short enough that everyone can attend without scheduling conflicts. Fifteen minutes is much easier to accommodate than 30 or 45. For broader meeting timer strategies, see our meeting timer guide and the 25-minute meeting format.

A good standup is a short standup. Fifteen minutes, a visible timer, and a team agreement to save discussions for after the meeting. That's all it takes to turn a dreaded daily ritual into something that actually helps your team move faster.