---
name: agile-standup
description: Use when asked to run a daily standup (daily scrum) — the three-question format, timeboxing, and common failure modes — including whether a team should even run one at all, as distinct from a broader agile-coaching engagement (see agile-coaching) that would help diagnose that question.
---

# Agile Standup

A standup meeting (daily scrum) is a short, typically-morning meeting
where a team reviews progress, discusses challenges, and plans the day
ahead — named for participants standing up during it, which helps keep
the meeting short and focused almost by physical discomfort alone.

## The three-question format

Each team member briefly answers:

- What did I work on yesterday?
- What am I planning to work on today?
- What obstacles or challenges are blocking my progress?

The point is keeping everyone informed, surfacing potential roadblocks
early, and creating a brief opportunity for teammates to offer support —
not detailed problem-solving, which should be deferred to a separate,
smaller conversation with just the relevant people.

## Making it actually effective

- **Timebox strictly** — commonly around 15 minutes regardless of team
  size; a standup that regularly runs long has stopped being a standup.
- **Same time, same place, every day** — consistency reduces the
  coordination overhead of remembering to attend and keeps it a genuine
  habit rather than an ad hoc meeting.
- **Physical/visual anchor** — standing in a circle near a task board (or
  a shared screen for remote teams) naturally encourages brevity and
  gives a visual reference for current work.
- **Defer complex discussion** — the Scrum Master or facilitator's real
  job is keeping tangents and detailed problem-solving out of the
  standup itself, redirecting them to a follow-up conversation instead.
- **Speak openly but respectfully** — ground rules for honest,
  constructive communication (see [[ways-of-working]] for the
  general meeting/communication norms this draws from).

## Whether a team should even run one

Standups aren't mandatory for being agile — some genuinely successful
teams eliminate them, especially remote/distributed teams working across
time zones, relying instead on asynchronous tools (shared dashboards,
CI/CD pipeline visibility, async status updates in chat) and organic,
as-needed conversation when a blocker actually arises. Continuous
integration and automated pipeline visibility can make routine status
reporting genuinely redundant. The underlying agile principles
(responding to change, frequent delivery, real collaboration) don't
themselves require a daily synchronous meeting — a standup is one
implementation choice for achieving them, not a requirement.

## Deciding which fits your team

Favor a standup when the team is co-located or working in largely
overlapping hours and needs quick daily coordination. Favor
async/no-standup approaches when the team is distributed across time
zones, already has strong tooling-driven visibility (CI/CD, project
boards), and finds a mandatory daily sync creates more meeting fatigue
than coordination value.

## Common pitfalls

- **Becoming a status report to management** rather than a peer-to-peer
  coordination tool — changes the meeting's whole character and tends to
  make people perform rather than communicate honestly.
- **Solving problems live in the standup** — derails the timebox and
  loses the people not involved in that specific problem; defer to a
  smaller follow-up conversation.
- **Running it out of habit without checking it's still adding value** —
  a team should periodically ask whether the standup (in its current
  form, or at all) is still the right tool, rather than assuming it
  always will be.

## Learn more

- [[ways-of-working]] for the general meeting/communication norms a good standup follows.
- [[agile-coaching]] for help diagnosing whether standups (or a specific format of them) actually fit a given team.
- [[agile-principles]] for the underlying principles a standup is one way of serving.