Standup Meeting: How to Run One Worth 15 Minutes

Nine people on a call. The fourth says "yesterday I mostly carried on with the thing I mentioned yesterday," and somewhere on the grid a camera goes off. It's 9:47. This started at 9:30.

A standup meeting is supposed to cost fifteen minutes and produce a plan for the day. Plenty cost twenty-five and produce a status report for whoever is most senior on the call — a different meeting, under a name that no longer fits.

The fix isn't discipline. It's what the meeting asks for — and most teams still ask the three questions the format's own authors stopped recommending years ago.

What a standup meeting actually is

A standup meeting is a short daily sync for a team that shares a goal. Everyone looks at the same work, says what's stuck, and adjusts the plan for the day. It isn't a progress report, and it isn't where decisions get made — though it's often where you find out one is needed.

The practice has two parents. Ken Schwaber and Jeff Sutherland first co-presented Scrum at the OOPSLA conference in 1995, and the framework includes a daily event; the word "scrum" came from a 1986 Harvard Business Review article by Hirotaka Takeuchi and Ikujiro Nonaka, borrowing the rugby image of a team moving the ball together. A daily stand-up also turns up among Extreme Programming's practices at the end of the 1990s. Most people use both names for the same thing.

Standing was a hack, not a principle: a meeting held on your feet gets uncomfortable, and discomfort caps the length. No version of the Scrum Guide has ever required it, and insisting on it excludes anyone who can't stand comfortably.

One boundary: this is the daily team sync. Not the recurring session where a manager works through priorities with their team — a different animal, covered in how to run an effective staff meeting. And certainly not the company-wide all hands meeting. When standup content migrates into either, something upstream has broken.

What the Scrum Guide says now, and what it stopped saying

Most teams are running a format from a document that no longer says what they think it says.

The 2020 Scrum Guide — the current version — describes the Daily Scrum as "a 15-minute event for the Developers of the Scrum Team," held at the same time and place every working day of the sprint. Its purpose is to inspect progress toward the sprint goal and adapt the sprint backlog. The Product Owner and Scrum Master take part only when they're working on items in that backlog.

Then the sentence almost nobody has read: developers can choose whatever structure and techniques they like, provided the meeting focuses on progress toward the sprint goal and produces an actionable plan for the next day's work.

Which means the famous three questions are gone. Earlier editions prescribed them; the 2020 revision stripped that out along with much of the other prescriptive language. Nothing in current Scrum requires anyone to say what they did yesterday. The guide also notes, in passing, that this isn't the only time a team may re-plan.

Why the three questions aged badly

What did I do yesterday. What will I do today. What's blocking me. As training wheels for a team that has never done this, fine. As a permanent structure it fails in four predictable ways.

It's addressed to people, not to work. Nine people times three answers is twenty-seven small monologues, of which any listener needs about four. The goal never comes up, because no question asks about it.

"Yesterday" is an audit prompt. Ask someone to account for their previous day in front of colleagues and you'll get a defence, padded to sound like a full one. That's what the question invites.

The reporting direction drifts. Eye contact goes to the most senior person present, and within three weeks it's a briefing for them rather than a sync between peers.

It hides the state of the sprint. Everyone can be busy, nobody blocked, and the goal still slipping. The format has no way to show it.

Try this once: run a standup where nobody is allowed to say what they did yesterday. If it still does its job — and it usually does — the question was never carrying the value.

Better standup meeting questions

The shift that fixes most standups is walking the work instead of the room. Pull up the board and go item by item, right to left — start with what's closest to done, because finishing beats starting. People speak when their item comes up, and nobody performs a daily report.

The questions that earn their place:

• What has to happen today for this item to move? Asked of the item, answered by whoever's holding it.
• What's at risk, and when will we know? The blocker question rewritten so it can be answered honestly. "At risk" costs nothing to admit. "Blocked" sounds like a confession.
• What changed since yesterday that someone else needs to know? Catches the side-channel decision three people haven't heard.
• Who needs ten minutes from whom after this? The highest-return question in the meeting, and the one that keeps the other fourteen minutes clean.
• Are we still going to hit the goal? Two or three times a week, out loud. A team that can't answer doesn't have a shared goal — a planning problem in a standup costume.

Fifteen minutes, and where they go

The timebox doesn't scale with headcount — fifteen minutes is fifteen minutes whether you're four people or ten. Do the arithmetic on a ten-person team and you get ninety seconds each, which is the clearest possible signal that a round robin is the wrong shape.

Standups bloat in three ways. Someone starts solving a problem in the room. Someone briefs an absent stakeholder. And people narrate to prove effort — a symptom of how the meeting has been used before, not laziness.

The fix for all three: name it, own it, put a time on it. "That's a design question — Rosa and Tunde, straight after this, fifteen minutes." Anything that becomes a commitment leaves as a proper task, and there's a method to phrasing those in our guide to writing action items people finish.

If the overrun happens most days, stop calling it a discipline failure. The overrun is a meeting your team needs — and a weekly working session with a real meeting agenda template behind it does that job better than ten minutes bolted onto every morning.

A daily standup meeting template you can copy

One board, one timer, six steps. The format is deliberately item-first: a name only appears when somebody needs something from somebody else.

Template — 15-minute daily standup

[TEAM] STANDUP — [date] · 15 min · timer: [who]

Goal we're working toward: [one line — read it out only when it has changed]

Walk the board, right to left

[Item] — [state] — [what has to happen today for it to move] — [who's holding it]

At risk of not landing

[Item] — [why] — [when we'll know]

Changed since yesterday

[The thing others need to know — decisions, breakages, new information]

Needs someone today

[Name] needs [what] from [name] — [when they're meeting]

Parked

[Topic] → [who owns it] → [when it happens]

Filled example — 15-minute standup

PAYMENTS SQUAD STANDUP — Tue 1 Sep · 15 min · timer: Meg

Goal: refunds go through the new ledger before the 12th.

Walk the board, right to left

Refund reversal — in review — needs Nils to look before lunch — Rosa

Reconciliation job — in progress — running against September data today — Tunde

Partial refunds — not started — nobody picks it up until reversal ships

At risk of not landing

Reconciliation job — the September export is missing two days of data — Tunde will know by 14:00

Changed since yesterday

Finance moved their cutoff to the 10th. Two days earlier than the date on the board.

Needs someone today

Rosa needs a review from Nils — before lunch · Tunde needs the missing export from data eng — Meg is chasing at 10:00

Parked

Whether partial refunds ship in this batch at all → Meg → 20 minutes after this, with Tunde

Run well, that takes about seven minutes. The other eight are the buffer that stops anyone rushing the item that needed a conversation.

Async standups, and when they're just status theatre

An async standup replaces the meeting with written updates posted to a channel by a cutoff time. Done properly it beats the live version for a lot of teams. Done badly it's a ritual nobody reads — worse than the meeting it replaced, because at least in a meeting people listen.

Async wins when the team spans more than a few hours of time zones and any live slot punishes somebody; when the work is loosely coupled; and when the team's value comes from long uninterrupted stretches, where a fixed 9:30 is an interruption dressed as coordination.

Keep it live when people are in the same files and a collision costs half a day, when the team is new, or when the posts have quietly stopped being read — detectable in a minute by checking whether anyone ever replies.

Staying live and distributed makes timing harder than it looks, because a daily meeting can't be rotated the way a monthly one can: an unkind slot is unkind to the same person every day for a year. Put it inside the real overlap window, not at the start of headquarters' morning. Under about three hours of overlap, async is the honest answer, not the lazy one.

The rule that makes async work: a post naming another person is a request, not a status line, and requests get an answer the same working day. Without it you have a wall of updates and no coordination.

Template — async standup post

#[team]-standup — [date] · post by [time, your local]

Four lines. Thread the detail.

Moving

[The one thing you'll finish today. Not a list.]

At risk

[What might not land, and when you'll know]

Ask

[@name — what you need and by when — or "none"]

Heads-up

[One thing the team would be annoyed not to hear]

Filled example — async post

#payments-standup — Tue 1 Sep · Tunde, 09:10 WAT

Moving

Reconciliation job running against September data — aiming to have a result before I sign off.

At risk

Two days missing from the export. If it isn't fixed by 14:00 UTC this slips to Thursday.

Ask

@meg — can you chase data eng for the 3rd and 4th? Need it by 14:00 UTC.

Heads-up

Finance moved their cutoff to the 10th. The board still says the 12th.

Being straight about tooling: a fifteen-minute standup does not need a transcript, and anyone selling you one is solving a problem you don't have. The exceptions are narrow — the distributed team whose "standup" is really a recorded video half of them watch later, and the standup that keeps turning into a decision meeting nobody wrote down. For those, an AI meeting assistant that records and summarises the call earns its keep: Laxis covers Zoom, Google Meet and Teams, pulls out the action items and who owns them, and handles 100+ languages. For a normal seven-minute sync, a board and a timer beat any software.

Four ways a standup dies

How to kill or fix a standup nobody values

Don't put it to a vote in the standup. Ask people one at a time, because in a group nobody wants to call a meeting a waste of time in front of whoever scheduled it.

Then run the experiment. Cancel it for two weeks and replace it with nothing — not a different meeting, nothing — writing down first what you expect to break. Most teams get about four days before two people collide on the same work or a decision gets made twice. That collision is the value the meeting was providing, and now you know its size.

If nothing breaks, the team wasn't sharing work in the first place. The standup was compensating for parallel tracks that don't need daily coordination, and the honest fix is changing how the work is split rather than keeping the ceremony alive.

Short of killing it, halve the frequency. Three mornings a week is legitimate outside Scrum; inside Scrum it means you've left the framework, which is fine as long as you decide it rather than drift into it. And if what survives is a decision meeting rather than a sync, treat it like one: an agenda, a facilitator, a written record. Remembering is what a standup is worst at.

For the meetings that do need a record

Laxis joins the calls that matter on Zoom, Google Meet and Teams, writes the summary, and lists every action item with the person who owns it. The free tier includes 300 minutes of transcription a month.

Try Laxis Free

Where that leaves you

A standup is one of the few meetings whose value is easy to test, and almost nobody tests it. Cancel it and watch what falls over. Change one question and hear how differently people talk. Move it half an hour later and find out whether the morning was worth protecting.

The people who wrote the rules quietly stopped telling you how to spend the fifteen minutes. That's an invitation, not an oversight.

Frequently asked questions

What is a standup meeting?

A standup meeting is a short daily sync, usually 15 minutes, where a team working toward a shared goal checks progress and adjusts the day's plan together. It exists to surface what is stuck and who needs whom, not to report status upward. In Scrum the equivalent event is called the Daily Scrum.

How long should a daily standup meeting be?

Fifteen minutes, and the number does not scale with headcount. The 2020 Scrum Guide fixes the Daily Scrum at 15 minutes regardless of team size, which is precisely why a person-by-person round robin stops working past six or seven people. If you consistently need thirty, you are holding a working session inside a standup.

What are the three standup meeting questions?

What did I do yesterday, what will I do today, and what is blocking me. Earlier versions of the Scrum Guide prescribed them, but the 2020 revision removed the prescription entirely. Teams may still use them, and many new teams find them a useful set of training wheels, but nothing in Scrum requires them now.

Do you have to stand up in a standup meeting?

No. Standing was a trick to make the meeting uncomfortable enough to stay short, and the Scrum Guide never requires it. Insisting on it also excludes anyone who cannot stand comfortably, and it does nothing for a remote team. Use a visible timer instead; it does the same job without the theatre.

Should a manager attend the daily standup?

Only if they have work on the board. The Scrum Guide frames the Daily Scrum as an event for the Developers, and the moment a manager attends as an audience the meeting quietly becomes a status report addressed to them. If you need visibility as a manager, read the board or ask for a weekly summary instead.

Are async standups better than live ones?

Async standups win when the team spans more than a few hours of time zones, when the work is loosely coupled, or when protecting focus time matters more than immediacy. Live wins when people are working on the same files, when the team is new, or when written updates have stopped being read by anyone.