Standup Meeting Timer
Embed this timer
Copy and paste this snippet into your website or blog post. Free to use — please keep the credit link so others can find the timer.
Add to Home Screen
Tap Share in Safari, then choose "Add to Home Screen".
Agile standups (daily scrums) are timeboxed to 15 minutes maximum, with each team member speaking for 2–3 minutes covering: what they did yesterday, what they are doing today, and any blockers. A visible interval timer keeps participants concise and prevents the common pattern of standups expanding to 30–45 minutes.
The 2-minute-per-person timebox is the Scrum Guide standard. Research on meeting efficiency shows that visible time constraints reduce speaking time by 30–40% without reducing information quality. A 15-minute standup for a team of 6 provides exactly 2.5 minutes per person — achievable with a simple interval timer.
Standing up is the mechanism
The format is called a standup because people stand, and that is not decoration — mild physical discomfort is what keeps it short. Teams that adopt the name and sit down reliably drift toward twenty-minute meetings.
For remote teams the equivalent constraint has to come from somewhere else, which is usually a visible timer. Without a physical cue or a clock, nothing bounds the meeting except everyone's patience.
It is for blockers, not for status
The genuinely valuable output is a blocker said out loud in front of someone who can remove it. The status portion is mostly for the person speaking, and a written channel serves it better in most teams.
A standup where nobody ever reports a blocker is usually a standup where reporting one feels unsafe rather than one where nothing is blocked. That is worth noticing, because the meeting is then costing time and producing nothing.
Problem-solving is the failure mode
Every standup that overruns does it the same way: someone mentions a problem, two people who understand it start solving it, and everyone else waits. The conversation is valuable and the standup is the wrong place for it.
Naming the topic and who needs to be in it, then moving on within ten seconds, fixes it. That conversation then happens straight afterwards with the three people it concerns instead of the whole team.
Per-person budgets that keep the meeting inside fifteen minutes.
| Team size | Per person | Updates | Remaining |
|---|---|---|---|
| 4 | 90 s | 6 min | 9 min |
| 6 | 75 s | 7.5 min | 7.5 min |
| 8 | 60 s | 8 min | 7 min |
| 10 | 60 s | 10 min | 5 min |
| 12 | 45 s | 9 min | 6 min |
| 15+ | — | — | Split the standup |
- Standing is the constraint. Remote teams need a visible timer because they have removed the physical cue.
- Above ten people, split rather than extend — most listeners find most updates irrelevant.
Sources
- Standup practice follows widely adopted agile convention; the fifteen-minute timebox is set by the Scrum Guide , TheTimerLab — accessed 2026-07-28