What is a standup meeting? Purpose, history and the 15-minute rule

A standup meeting is a short, daily synchronization, usually fifteen minutes and usually held standing, where a team shares progress, surfaces blockers, and re-plans the next day together. It is a meeting the team runs for itself: a coordination checkpoint, not a status report to a manager. That one distinction decides whether the fifteen minutes are worth it.

Most teams run a standup. Far fewer run one worth the time, and the difference is almost never the format. It’s whether the meeting coordinates the team or just audits it.

Why it’s called a standup

The name is the constraint. You stand because standing gets uncomfortable, and the discomfort does a job: it caps the meeting before it sprawls into design debate. Take away the chairs and you take away the incentive to ramble.

The format predates Scrum. It comes from Extreme Programming in the late 1990s, where the daily standup was one of the original team practices, and it was later folded into Scrum as the Daily Scrum. If you want the terminology untangled (daily scrum, daily standup, daily huddle), see daily scrum vs daily standup. For this chapter, treat them as the same event.

What a daily standup is for

Strip it back and a standup does three things:

• Builds a shared picture of progress toward the sprint goal: not a task-by-task audit, but enough for everyone to know where the work stands.
• Surfaces blockers early, while they still cost an hour instead of a day. A blocker named on Tuesday morning is a blocker someone can clear by Tuesday afternoon, and one that isn’t cleared comes back the next morning in a daily standup tool that carries open blockers forward.
• Lets the team re-plan the next day around each other: who pairs with whom, what gets picked up, what waits.

None of that is reporting. The failure mode is a room of people taking turns narrating yesterday to a manager while everyone else waits for their turn and tunes out. That is a status meeting wearing a standup’s clothes, and teams can feel the difference. It’s the version people quietly start skipping.

The fifteen-minute rule

Fifteen minutes is the ceiling, not the target. For a team of five or six, a good standup is often done in eight.

The rule that makes the timebox real is simple: you may raise a problem in the standup, but you may not solve it there. The second two people start debugging, everyone else is paying rent on a conversation they aren’t in. Note it, name who needs to follow up, and take it offline the moment the standup ends: the “parking lot.” A fifteen-minute meeting that spawns three five-minute follow-ups with the right two people is working exactly as intended.

Who should be there

The people doing the work, and few others. A delivery team of four to nine is the sweet spot; past that, the round-robin alone eats the timebox and you should split the team or the standup.

Managers are the recurring tension. There is nothing wrong with a manager or product owner attending, but they attend to coordinate their own work, not to receive a report. The instant the meeting is performed at someone, people start describing effort instead of naming problems, and the honest material (“I’m stuck, I’ve been stuck since yesterday, I don’t know who to ask”) is exactly what stops getting said. If you’re wondering whether your standup has tipped into surveillance, that question has its own chapter: why your standup is broken.

Where the standup fits

The daily standup is one of a handful of recurring agile meetings: planning at the start of the sprint, the standup every day, a review and a retrospective at the end. It’s the only one that happens daily, which makes it the heartbeat of the sprint and also the one most easily hollowed out by habit. For how the whole set fits together, see the agile ceremonies guide; for the sprint’s opening move, see sprint planning.

Once you’re clear on what a standup is for, the rest of this guide is the practical how, starting with what to actually say and how to facilitate it so it stays fifteen minutes.

Frequently asked questions

What is the purpose of a daily standup?

To coordinate, not to report. A daily standup gives the team a shared picture of progress toward the sprint goal, surfaces blockers while they are still cheap to fix, and lets people re-plan the next day around each other. The moment it becomes a status update read out to a manager, it has stopped doing its job.

How long should a daily standup be?

Fifteen minutes, timeboxed, and most teams can do it in less. If it regularly runs longer, the team is problem-solving in the meeting instead of after it. End on time even mid-sentence. The overrun is the signal, and protecting the timebox is what keeps people showing up.

Why is it called a standup?

Because you hold it standing up. The physical discomfort is deliberate: standing makes a long meeting unpleasant to sustain, so it caps the length without anyone having to police it. The name predates Scrum (it comes from Extreme Programming), and the constraint is the point of the format.

Who should attend a daily standup?

The people doing the work. Keep it to the delivery team: the developers, testers, and designers actually moving items this sprint. A product owner or Scrum Master can attend, but as participants coordinating their own work, not as an audience being reported to. Once managers turn up to listen, the honest material dries up.