Daily Standup Meeting: How to Run It in 15 Minutes

Marco's team calls it the "15-minute standup." Last Tuesday it ran 38 minutes. Two engineers debated a database index while six people stood around checking their phones, and the one real problem of the day, a vendor API that had been down since 7 a.m., came up in the last 90 seconds. Nobody wrote it down. (Marco's team is a composite, not a real team.)

Everyone who runs a daily standup meeting knows it should be short. The hard part is staying short while still catching what matters.

This guide gives you what the Scrum Guide actually says (including the three questions it dropped), a 15-minute run sheet with the lines to use when the meeting drifts, four standup formats, better questions, and a notes template with a blocker log that doesn't lose problems overnight.

What is a daily standup meeting?

A daily standup meeting is a short meeting, usually 15 minutes or less, where a team checks progress toward its goal, plans the next day of work and raises anything blocking it. It happens at the same time every working day. The name comes from the habit of standing to keep it brief, though nothing requires it.

In Scrum it's called the Daily Scrum. Outside software it goes by daily huddle or morning check-in, and sales, operations and support teams run it too.

What the Scrum Guide says about the standup

The 2020 Scrum Guide is short on this event, and the details matter:

• Purpose: "to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work."
• Timebox: "The Daily Scrum is a 15-minute event for the Developers of the Scrum Team."
• Rhythm: it is "held at the same time and place every working day of the Sprint."
• Who: the Developers. If the Product Owner or Scrum Master are working on Sprint Backlog items, "they participate as Developers."
• Format: "The Developers can select whatever structure and techniques they want," as long as the meeting focuses on the Sprint Goal and "produces an actionable plan for the next day of work."

What happened to the three questions?

Many guides still present "What did I do yesterday? What will I do today? Any blockers?" as the official Scrum format. That isn't accurate.

The 2017 Scrum Guide listed those three questions as "an example of what might be used." The 2020 version removed them altogether. The Scrum Guide revision history lists "removed Daily Scrum questions" as part of making the guide less prescriptive.

The three questions are still allowed. They're just one option.

Who attends, when and how long

• Who: the people doing the work toward a shared goal. In Scrum, that's the Developers. Managers can listen, but the standup is for the team's plan, not a status report upward.
• When: the same time every day, early enough that the plan still shapes the day. Many teams pick the first hour of the working day; distributed teams pick the overlap in their time zones.
• How long: 15 minutes at most; a team of four rarely needs more than 8. Regular overruns mean the team is too big or solving problems in the room.
• Size: if more than about 10 people speak, split into smaller standups. Our meeting cadence guide shows how the standup fits with your other recurring meetings.

A 15-minute standup meeting agenda (run sheet)

Use this daily standup meeting agenda as a starting point. The right-hand column is what the facilitator says when the meeting starts to slip.

Three lines do most of the work:

• When a discussion starts: "Good topic. Who needs to be in it? Let's park it for right after."
• When an update turns into a report: "What does that change about today's plan?"
• When someone says "no blockers" three days running on a late item: "What would make this go faster?"

Anything parked goes on a list, and only the people involved stay behind. Our guide to the parking lot in meetings explains the method.

Want your standup notes without a note taker? Put ParrotNotes on the table and get a summary and action items when the meeting ends. Try ParrotNotes free.

Four standup meeting formats and when to use each

Rotate if the meeting goes stale. Pick by what your team needs most.

A composite example: a six-person product team switched from round-robin updates to walking the board. Standups dropped from about 20 minutes to 9, and fewer tasks sat half-finished, because every morning started with "what does this item need to get to done?"

Standup meeting questions that beat "what did you do yesterday?"

Pick two or three, not all six.

About the goal

1. Are we still on track for the goal? What's the biggest risk to it?
2. What's the one thing that has to happen today?

About the work 3. What's closest to done, and what does it need? 4. What has been "in progress" for more than two days?

About blockers 5. What is slowing you down, even a little? 6. Is anyone waiting on someone outside the team?

Daily standup meeting notes: a one-screen template

A common rule is "don't take notes at standup." The problem is blockers. Without a written record, the same problem gets mentioned on Monday, Tuesday and Wednesday, and nobody owns it.

Keep notes to one screen: blockers and decisions, not what each person said. Copy this daily standup meeting template:

STANDUP NOTES
Team:              Date:            Day __ of __
Goal:

1. OPEN BLOCKERS (carried from yesterday)
   Blocker | Owner | Raised on | Status today

2. NEW BLOCKERS
   Blocker | Owner | Clear by

3. PLAN CHANGES (only what changed)

4. PARKING LOT (topic | who stays)

5. DECISIONS

A filled example: a field sales team's Monday standup

Standups aren't only for software teams. Here's the template filled in for a regional sales team that meets for 10 minutes before reps head out (a composite example):

STANDUP NOTES
Team: Midwest field sales (6 reps + manager)   Date: Monday, Oct 12   Week 2 of 13
Goal: 4 signed renewals and 12 demos this week

1. OPEN BLOCKERS
   Pricing approval for Hartley Foods (12% discount) | Dana (manager) | Thu | Still with finance
   Demo unit for Joliet branch is out of stock | Luis | Fri | Cleared, unit arrives Tue

2. NEW BLOCKERS
   Hartley's buyer wants contract redlines by Wed | Dana | Tue noon
   CRM won't sync on Priya's phone | Priya | today, IT ticket opened

3. PLAN CHANGES
   Sam takes Priya's 2 p.m. Rockford visit (Priya at the trade show)

4. PARKING LOT
   Q4 territory split | Dana, Sam, Luis stay 10 min

5. DECISIONS
   Renewals over 10% discount go to Dana the same day, not Friday

Notice what isn't there: every call each rep made yesterday. That belongs in the CRM. Standup notes hold what the team has to act on.

Blockers that stay open for more than two days belong in your team's main task list. Our guide to action items tracking shows a running log with statuses and carry-forward rules, and the meeting notes template covers longer meetings.

Remote and async standups

Remote standups work, with three adjustments:

• Cameras on, agenda on screen. Share the board or the notes template so everyone follows the same list.
• Fixed speaking order. Alphabetical or by board column. It saves the "who's next?" pause.
• Async for updates, live for blockers. If your team spans more than about four hours of time zones, post written updates by a set time and keep a short call only for people with blockers.

Common standup problems and how to fix them

If the standup keeps raising the same process problems, save them for your retrospective meeting, which is built for fixing how the team works. The standup plans the day; the retro improves the sprint.

Should you record the daily standup?

Recording lets the facilitator run the meeting instead of typing, and gives anyone who missed it a quick way to catch up.

Ask the team first. Say why you're recording, who will see the notes and how long you keep them, and stop if anyone objects. Consent rules also vary by location; our guide to one-party consent states covers the US basics.

ParrotNotes records on the phone you already carry, so there's no bot to invite and nothing to set up for an in-room standup. Every recording gets an AI summary, and AI-powered recordings add action items. On Pro, speaker ID shows who raised each blocker, and AI search finds when a problem first came up across weeks of standups.

Run tomorrow's standup in 15 minutes

A good daily standup meeting is short because it has one job: agree on today's plan and clear what's in the way.

• Start on time and state the goal.
• Review yesterday's open blockers first.
• Pick a format that fits the team, and rotate if it goes stale.
• Park every discussion for right after.
• Keep one screen of notes: blockers, owners, decisions.

Try the run sheet and template tomorrow. If you'd rather watch the team than a keyboard, let ParrotNotes take the notes. Download ParrotNotes free and record your next standup.