What Is a Daily Standup? 15 Minutes That Keep Teams Honest

The daily standup — or Daily Scrum, if you want to be official — is the most famous meeting in Agile. It's also the most frequently ruined one. Let me tell you what it's actually for, because most teams get it subtly wrong and then wonder why it feels like a waste of time.

The basics

Every day, same time, same place, the team meets for 15 minutes — ideally standing up, which is where the name comes from. The point of standing is physical: you don't want to be comfortable, because this meeting is supposed to be short and you're supposed to get back to work.

It's not a demo. It's not a status report. It's a daily re-sync so the team knows where things stand and can spot problems early.

The three questions

Classically, everyone answers three things:

1. What did I do yesterday?
2. What am I doing today?
3. What's blocking me? (Anything in my way — a dependency, a question, an access permission that doesn't exist.)

That's it. Fifteen minutes, three questions, around the circle. The third question is secretly the most important one — the whole point is to surface blockers while they're still cheap to fix, not a week later when everything's on fire.

Who it's really for

Here's the mindset shift that makes standups work: the update isn't for the manager, it's for the team. Your teammates need to know what you're doing so they can help, coordinate, or warn you about the thing you're about to collide with.

If a standup turns into a performance review — "what have you got for me today?" — people stop being honest and start being defensive. Blockers get hidden, and the meeting becomes theatre. Keep it peer-to-peer and it stays useful.

The traps that kill a standup

I've seen every one of these, and I've caused a couple:

• The problem-solving pit. Someone mentions a bug, and suddenly three people are debugging on the spot while everyone else watches. That's not a standup — that's a working session. Park it: "let's grab a room after."
• The daily demo. Detailed walkthroughs of yesterday's work. Save that for the sprint review. Here, one or two sentences.
• The 45-minute update. If it's regularly running long, your stories are too big or your team is too big. Split either.
• The boss-report. The moment it becomes status-to-management, honesty dies. Protect it.

The real example

We had a standup where someone casually mentioned they'd been "waiting for the staging environment all week." Nobody had said anything because nobody asked. That one sentence unblocked three days of work. The environment was fixed that afternoon. Standups are cheap insurance against silent waiting — which is why the blocker question matters more than the other two put together.

The remote twist

Remote teams make standups both easier and harder. Easier because async updates in Slack or Teams are genuinely fine for many teams. Harder because a video standup across timezones means someone's usually eating breakfast or wearing their pyjama top on camera.

The golden rule for distributed teams: pick a time that's actually in everyone's working hours, even if it means someone starts slightly earlier or stays slightly later. One person permanently at 11 PM is how you lose them. And keep the three-question format tight — remote standups drift even faster than in-person ones.

Quick answers

Do we have to stand? No, but the standing is a useful nudge. If you sit, cap it at 15 minutes anyway.

What if someone's on holiday? They're not there. You mention it once and move on. No need to update for them.

Can we skip it if nothing's changed? Teams sometimes do "no blockers, moving on" days, but the habit is worth keeping — problems usually announce themselves on the day you'd skip.

Tip: For distributed teams, agree on the standup time using your team's actual timezones — ClockHive shows you the overlap in seconds so you can pick a slot that doesn't make anyone a 6 AM zombie.