Standup Per-Person 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".
The daily standup is timeboxed at fifteen minutes in the Scrum Guide[1]. Sixty seconds per person keeps a team of up to ten inside that, and the per-person timer is what makes the cap achievable rather than aspirational.
Sixty seconds is enough to say what you did, what you are doing and what is blocking you. It is not enough to explain a technical problem, which is the point — the standup exists to surface blockers, not to solve them.
Problem-solving is the drift
Every standup that overruns does so the same way: someone mentions a problem, two people who understand it start solving it, and eight people wait. The conversation is valuable and the standup is the wrong place for it.
The fix is a parking lot — noting the topic and the people who need to be in it, and moving on within ten seconds. That conversation then happens immediately afterwards with the three people it concerns rather than the whole team.
Blockers are the actual purpose
The status portion is largely for the person speaking. The genuinely valuable output is a blocker stated out loud in front of someone who can remove it, and a standup where nobody ever reports a blocker is usually a standup where reporting one feels unsafe.
Reserving a moment specifically for blockers, rather than leaving them as the third thing in a rushed sixty seconds, is a small change that meaningfully improves what the meeting produces.
Scale by splitting, not by extending
Above about ten people the arithmetic stops working: fifteen people at sixty seconds is fifteen minutes of updates before any discussion. The answer is smaller standups per sub-team rather than a longer one.
A large standup also has poor attention economics — with fifteen people, each listener finds thirteen of the fourteen updates irrelevant, which is why big standups feel like a waste even when they are efficiently run.
Per-person budgets that keep the meeting inside the fifteen-minute timebox[1].
| Team size | Per person | Updates total | Slack |
|---|---|---|---|
| 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 |
- Overruns are almost always problem-solving. Park the topic with the names of who needs to be in it, and move on within ten seconds.
- Above ten people, split rather than extend — with fifteen people each listener finds thirteen updates irrelevant.
Sources
- The Scrum Guide — Daily Scrum timebox , Scrum.org / Ken Schwaber and Jeff Sutherland (Verify current edition) — accessed 2026-07-28