How to Run a Daily Standup: A Step-by-Step Guide

how to run a daily standup is a key topic in modern project management and teamwork. The daily standup is the most copied and the most corrupted agile ceremony there is. Most teams start with a good intention and end up with a 30-minute status report where a manager interrogates six people about their individual progress. That is not a standup. A standup is a 15-minute alignment meeting that helps the team — not the manager — plan its day around the sprint goal.

This guide gives you the exact mechanics: what a standup is and is not, who should attend, the three questions, the formats that work, how to handle remote teams, the tools that support it, and the mistakes that quietly destroy it. By the end you will be able to run a standup that people find worth their time, which is the actual test of whether you are doing it right.

Quick Answer: How Do You Run an Effective Daily Standup?

An effective daily standup is a 15-minute meeting, held at the same time and place every working day, where each team member briefly shares what they did yesterday, what they will do today, and what is blocking them — focused on progress toward the sprint goal. Run it standing or seated, keep a timer, walk the board, and move any discussion that lasts longer than a minute to a follow-up conversation with only the affected people.

The nuance: there is no single correct format. The scrum framework deliberately leaves the structure to the team — the only non-negotiables are the 15-minute timebox, the daily cadence, and the focus on the sprint goal. A team that talks through the board instead of asking the three questions is running a perfectly valid standup.

What Is a Daily Standup — and What It Is Not?

The Daily Scrum is one of the five events in Scrum. Its purpose, per the Scrum Guide, is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. It is a planning event for the day, built for the people doing the work.

What a standup is not

• Not a status report. You are not updating a manager. You are aligning with peers so the team can re-plan its day.
• Not a problem-solving session. A blocker is named at the standup and solved after it, with only the people who can help. Solving it in the meeting is how a 15-minute standup becomes a 45-minute meeting.
• Not a planning session. Sprint Planning decides what the sprint will contain. The standup only adjusts the current day’s plan.
• Not the only place to raise blockers. If you are blocked, ask for help immediately — nobody should wait until tomorrow morning.

Who Should Attend a Daily Standup?

The Developers — the people doing the work — attend. The Product Owner and Scrum Master join if they are actively working on items in the Sprint Backlog; otherwise they are optional. The Scrum Guide is explicit that the Daily Scrum is an event for the Developers.

This is where many teams go wrong: they invite stakeholders, a manager, and the PMO, and the meeting instantly turns into a reporting session because people talk differently when the boss is in the room. Two practical rules:

• If someone attends, they must speak in “we” language and stay focused on the sprint goal.
• If a stakeholder needs status, give them a report or a board — not a seat in the standup.

What about a Scrum Master or manager?

A good Scrum Master is a facilitator, not a questioner. The best standups are run by the team, often with a rotating facilitator and timekeeper. If the manager does attend, their job is to listen for impediments they can remove — and to say nothing else.

What Are the Three Questions?

The classic standup structure is three questions, answered by each person in turn:

1. What did I do yesterday? — progress toward the sprint goal.
2. What will I do today? — the plan, adjusted to reality.
3. What is blocking me? — impediments, named out loud.

The three questions are a starting point, not a law. Many teams improve them. A popular variant used by teams that want more accountability: “What did I accomplish since the last standup, what will I accomplish by the next one, and what is in my way?” Another good variant adds: “What do I need from my teammates today?” — which turns the meeting explicitly collaborative rather than merely informational.

Why the three questions work

They force brevity, they surface blockers, and they create daily accountability without surveillance. Notice that none of the three questions is “what percentage of your task is complete?” — percentage complete is a status metric; the questions are about movement and obstacles.

How Long Should a Daily Standup Last?

Fifteen minutes, maximum. The Scrum Guide sets the Daily Scrum as a 15-minute event, and most effective standups finish in 8 to 12 minutes for a team of six to nine people.

Three things keep the timebox honest:

• A timer. Someone — ideally rotated — watches the clock. When the timer rings, the meeting is over, and anything unfinished moves to a follow-up.
• A rule for deep work. Any topic that needs discussion gets parked in a “parking lot” (visible on the board or whiteboard) and discussed after the standup with only the relevant people.
• Preparation. Each person should know before they arrive what they did and what they plan. The standup is for sharing, not for thinking on your feet.

How to Run a Daily Standup: Step by Step

Here is a repeatable process that works for most teams.

Step 1: Set the time and place (once)

Pick a time that works for the whole team and hold it there every working day. Common choices are 9:00–10:00 a.m. for co-located teams, or a fixed time that overlaps the best for distributed ones. Same time and same place reduce complexity — nobody has to think about when or where the standup is.

Step 2: Bring the board (every day)

Put your scrum board or kanban board where everyone can see it. The board is the shared artifact — it keeps the conversation about work, not about feelings. Teams without a board drift into vague chat.

Step 3: Go around, one at a time (5–10 minutes)

Each person answers the three questions in about 60–90 seconds. People speak to each other, not to a facilitator. When someone mentions a blocker, note it visibly and move on — the resolution happens after.

Step 4: Park deep topics (as they arise)

When a conversation starts to spiral — someone explaining a technical problem or two people negotiating an approach — cut it: “Let’s take that offline with you two after this.” Add it to the parking lot so it is not lost.

Step 5: Close on time and confirm the day’s plan (1 minute)

The standup ends when the timer ends. The team should leave knowing what each person is doing today and what impediments are being handled. If the sprint goal or plan needs a bigger change, that happens in a separate conversation with the Product Owner.

What Are the Alternative Formats?

The three-question round-robin is not the only valid format. Choose the one that fits your team.

Walk-the-board format

The team walks the columns of the board from right to left (from Done back to To Do) and discusses the status of each work item rather than each person. This is better for teams with lots of small items or where work moves between people, because the conversation centers on the work, not on individuals. The trade-off: it is easy to drift into status-reporting about items nobody cares about — keep it tied to the sprint goal.

The async standup

For distributed teams across many time zones, a synchronous 15-minute meeting may be impossible or deeply inconvenient for someone. An async standup replaces the meeting with written updates: each person posts their yesterday/today/blockers in a team channel, or records a short video, by a deadline each morning. Teammates read them at their own pace and follow up as needed.

The trade-off: async standups lose the spontaneous “oh, I can help with that” moments, and they can silently degrade into silent check-ins that nobody reads. Make them work by keeping a hard deadline, keeping updates short, and holding one or two weekly synchronous standups if the team is only lightly distributed.

The scrum-of-scrums (for bigger groups)

For teams larger than one scrum team, each team’s representative (often the Scrum Master or a nominated person) meets in a scrum-of-scrums — typically three times a week — and shares coordination information: what their team is doing, what they will do, and what blockers cross team boundaries. This keeps a 24-person group aligned without putting 24 people in one 15-minute meeting.

How Do You Run a Standup for a Remote or Hybrid Team?

The one rule that solves most remote-standup problems: if one person is remote, treat everyone as remote. That means everyone joins the video call from their own machine — no huddle of five people around a laptop while three people stare at a ceiling.

Remote standup specifics that work in practice:

• Everyone on their own video call. This levels the playing field: side conversations and body language are visible to everyone, or to no one.
• A visible board. Screen-share your digital board, or agree on a single source of truth that everyone looks at during the meeting.
• Prefer async for very wide time zones. If the spread is more than a few hours, an async standup is more respectful of people’s schedules than a 7 a.m. call for someone on the other side of the world.
• Rotate the facilitator and timekeeper. In a remote meeting, someone must actively drive the order or people talk over each other.

What Tools Support Daily Standups?

For teams that want the standup’s artifact and its follow-ups in one workspace, Doitify’s project management platform combines a kanban board, sprints and backlogs, task owners and due dates, team chat, and meeting notes — so the standup’s decisions turn into tracked tasks instead of fading from memory. To be transparent: Doitify is our product, which is why we know its capabilities from the inside. The trade-off is that it is a broader platform than a single-purpose standup app — a tiny team that only needs a daily check-in might be fine with a lightweight board alone.

A note on the board: the standup tool matters far less than the shared artifact behind it. A team that walks a real board in any tool is ahead of a team with a perfect tool and no board.

Real Scenarios With Numbers

Scenario 1: The six-person team that fixed a drifting standup

A six-person development team ran a daily standup that had drifted to 35 minutes. The fix was mechanical: a 15-minute timer, a parking-lot column on the board, and a rule that any topic requiring more than a minute of explanation moved offline. Within two weeks the meeting ran 10–12 minutes daily. The time saved was concrete: 20–25 minutes per day across six people is roughly 100–125 minutes per day of recovered focus — the equivalent of about a full developer-day per week returned to deep work.

Scenario 2: The blocker that surfaced and got fixed same-day

A team of seven was losing roughly two developer-days per incident to an environment problem nobody had reported — because the standup had become a status report and people were embarrassed to say they were stuck. After the team changed the format to focus on blockers and celebrate them as findings, a developer mentioned on Monday morning that the staging environment had been broken since Friday. Two people paired for an hour and fixed it. The estimated cost of the undiscovered blocker was two developer-days; the cost of naming it was 15 seconds and one hour of pairing. Blocker-focused standups are cheap insurance.

Scenario 3: The global team that switched to async

A 24-person team spread across San Francisco, Warsaw, and Sydney could not find a 15-minute slot that worked for everyone — the spread was about 9 hours. They switched to an async standup: each person posted a two-sentence update (done / next / blocked) in a shared channel before 9 a.m. their time, with a Loom video once a week for demos. The result: the meeting time simply disappeared, and the number of cross-team blockers raised in the week’s scrum-of-scrums stayed constant. The trade-off they accepted: less spontaneous collaboration, which they recovered with one weekly synchronous all-hands.

Scenario 4: The team that walked the board instead of the people

A support team of five tried the three-question format and it failed — their work was tickets, not stories, and asking “what did you do yesterday” felt like accounting. They switched to walking the board column by column, discussing each in-flight ticket and its blocker. Standup time dropped from 20 minutes to 9, and the conversation became about the work. The lesson: the format must match the work. For ticket-driven teams, board-walk beats the three questions.

Common Mistakes

• Turning it into a status report to a manager. When stakeholders or a manager sit in and interrogate, people stop speaking honestly. Keep the audience to the people doing the work.
• Letting it run long. A 15-minute timebox is not a suggestion. No timer, no timekeeper, no parking lot — and the meeting doubles.
• Solving problems in the meeting. Deep discussions pull the whole team into a conversation only two people need. Park it and continue offline.
• Skipping the sprint goal. A standup that does not reference the sprint goal is just a round of personal updates. The goal is why the meeting exists.
• Meeting at different times or missing days. Irregular standups kill the habit. Same time, same place, every working day.
• Ignoring blockers. If blockers are raised and then never tracked or resolved, people stop raising them. Put them on the board and follow up.
• Making it voluntary or attendance-checked. A standup is a commitment, not an optional check-in — but the enforcement is cultural, not punitive.
• Forcing one format on every team. The three questions work for some teams; board-walk works for others. Pick the format that fits the work and renegotiate it in the retrospective.

Know This Before You Choose

• Decide the purpose first: alignment on the sprint goal and the day’s plan. If a meeting does not serve that, it is not a standup.
• Name the non-negotiables: 15 minutes max, every working day, same time and place, focused on the sprint goal.
• Choose a format deliberately: three questions, walk-the-board, or async — and be ready to change it when the team changes.
• For remote teams, apply the one-remote-treat-all-remote rule from day one.
• Make blockers visible and owned: a parking-lot or a “blocked” column on the board, with someone responsible for chasing them.
• Review the standup in the retrospective. If the team is not getting value from it, change it — the standup itself should be agile.

Conclusion

A great daily standup is small: 15 minutes, same time, same place, one shared board, a clear focus on the sprint goal, and blockers that actually get resolved. Everything else is noise. Run it as a team planning tool rather than a reporting ritual, keep a timer, park the deep discussions, and match the format to your work — three questions, walk-the-board, or async for global teams. Review how the standup feels in your retrospective, and change it when it stops earning its time. If you want the whole loop in one place — a kanban board, sprints and backlogs, task owners and due dates, team chat, and meeting notes so the standup’s decisions actually stick — Doitify’s project management platform is built for exactly that.