Daily standup is the most defended ceremony in agile. Suggest skipping it and someone will say “but how will we coordinate?” It’s also the most expensive — not because any single standup is long, but because the math compounds. This post is the honest accounting: what your daily standup actually costs, three signs you’re paying too much for it, and the four formats that buy more value per pound.
The math nobody runs
A 6-person engineering team. Each engineer is on a £80,000 salary. The fully-loaded cost (salary + 30% overhead) is £104,000 per year per engineer. Across 220 working days, that’s £473 per engineer per day, or £59 per engineer per hour.
A 15-minute standup, 5 days a week:
- 6 people × 0.25 hours = 1.5 person-hours per standup
- 1.5 × £59 = £88 per standup
- 250 working days/year ÷ 5 days = 50 weeks × 5 standups = £22,000/year
That’s just the meeting itself. Add the warm-up cost (engineers stop deep work 5-10 minutes before standup), the cool-down cost (10-15 minutes to re-enter flow after), and the actual cost is closer to £40,000-£50,000 per year for a 6-person team.
That’s a junior engineer’s salary, every year, paid in standup time. Your finance director would notice if you hired a ghost engineer to attend standup. They don’t notice this because it’s distributed.
(Plug your own numbers: Sprint Cost Calculator gives the per-team math.)
“But it’s only 15 minutes”
The 15-minute claim is the central lie of standup. Real cost is bigger because:
1. Standups regularly run 20-30 minutes. Not because anyone wants them to. Because someone goes deep on a bug, the team starts solving it together, and 15 minutes becomes 25.
2. Context-switching cost. Engineers writing or debugging at 9:55 know standup is at 10:00. They stop pulling on threads in the last 5 minutes. After standup, getting back to where you were takes 10-15 minutes of warm-up. Cal Newport’s research puts the full task-switching tax at 23 minutes. Even a tight standup eats nearly an hour of effective time per engineer per day.
3. Warm-up vs cool-down isn’t optional. You can tell the team to “just dive back in.” It doesn’t work. Brain context isn’t a switch.
If you take warm-up + cool-down seriously, a 15-minute standup costs each engineer 35-45 minutes of effective time. For 6 people that’s 3.5-4.5 person-hours per day, or roughly £200-£270 per day, or £50,000-£68,000 per year.
This isn’t an argument to skip standup. It’s an argument to be honest about what you’re paying for.
Three signs you’re paying too much
Sign 1: Engineers describe yesterday-today in vague terms because everyone already knows
If most of standup is “I worked on the X ticket yesterday, today I’m continuing the X ticket, no blockers” and that information is also visible on the board, the meeting is a coordination ritual without coordination value. You’re paying £88/standup for a feeling of co-presence.
Sign 2: The same blocker comes up three days in a row
If standup surfaces a blocker on Monday, Tuesday, and Wednesday — and each time it’s “I’m still waiting on X” — standup didn’t unblock anything. The blocker would be no worse on Wednesday if Monday and Tuesday’s standups had been skipped.
The fix: when a blocker surfaces, route it to a synchronous 5-minute resolution conversation that day, not the next standup.
Sign 3: The lead is the only one asking questions
When standup is the lead going around the room asking “anything else?” and getting one-word answers, the team isn’t using standup for coordination — they’re reporting status to the lead. That’s a 1:1, badly. Either get the lead’s status from a Slack thread instead (cheaper), or replace standup with structured async + occasional sync (much cheaper).
Four formats with better cost-per-value
If you’re going to spend £40,000-£68,000/year on coordination, here’s the spectrum from cheapest to most-expensive, with what each actually buys.
1. Async written (cheapest, ~£8,000/year)
Each engineer posts a 3-line status update in a Slack thread by 11am: yesterday, today, blocked. Lead reviews and surfaces real blockers. Cost: ~3 minutes per engineer per day to write, no warm-up/cool-down because no synchronous interruption.
Buys: visibility, blocker surfacing, lead can act on patterns.
Doesn’t buy: shared awareness of in-progress work, cross-team conversation, accidental discovery (“oh wait, I’m working on the same thing”).
Best for: distributed teams, senior teams with strong ticket discipline.
2. Walk-the-board, 5-minute (£15,000-£20,000/year)
Same time and people, but the format is “walk the right side of the board, ticket-by-ticket: what’s the status of this near-done item?” Skip “what I worked on yesterday” — the board shows it. Skip “what I’m working on today” — the board shows that too.
Buys: targeted unblocking, cross-team awareness on items near done.
Doesn’t buy: deep coordination, project-level discussion.
Best for: teams with clean tickets, good board hygiene.
3. Classic three-question standup, 10 minutes (£30,000-£40,000/year)
Yesterday-today-blockers, person-by-person. The default format.
Buys: full team awareness, social cohesion, blocker surfacing.
Doesn’t buy: actual blocker resolution (that needs a follow-up call), focused work time.
Best for: small in-person teams, junior teams that benefit from forced status check-in.
4. No standup, weekly sync only (cheapest meeting time but highest coordination risk)
Replace daily with one 30-minute weekly sync. Async chat for blockers in real-time.
Buys: maximum focus time, ~£60,000/year saved.
Doesn’t buy: short-cycle coordination. Risk: blockers fester for 2-3 days because nobody surfaces them.
Best for: very senior teams that genuinely self-coordinate, distributed teams across multiple timezones.
The take
Daily standup costs more than your AWS bill. It’s worth it if and only if it produces the value you’re paying for: blocker resolution, cross-team awareness, course correction. If your standup is a 15-minute status report nobody acts on, you’re paying junior-engineer-salary for a coordination ritual.
Three diagnostic questions worth asking at the next retro:
-
In the last 5 standups, what’s one thing that happened in standup that wouldn’t have happened without it?
If the team can’t answer with concrete examples, the standup isn’t earning its cost. -
Could a blocker raised in standup be raised faster in Slack?
If yes, standup isn’t where blockers belong. -
Are we running standup because we need it, or because we’ve always run it?
This is the real question.
You don’t have to abolish standup. You have to make it earn its cost. The cheapest version of “team coordination” that delivers what you actually need is usually not the format you’re running today.
TL;DR
- A 15-minute daily standup for a 6-person team costs £40,000-£68,000/year including context-switching tax
- Three diagnostic signs you’re overpaying: vague yesterday-today reports, blockers that recur for days, lead does all the asking
- Four format options ordered by cost: async written < walk-the-board < classic three-question < no-standup-with-weekly-sync
- The right standup format is whatever delivers the coordination value at the lowest cost — don’t run the format you’ve always run; run the cheapest format that still works
- Plug your own team’s numbers: Sprint Cost Calculator