Stand-up meeting

A stand-up meeting is a short, timeboxed team sync where members share progress, plans, and blockers — typically lasting 5–15 minutes. Originally held standing to encourage brevity, modern stand-ups are now common in both in-person and remote settings.

Stand-ups help teams maintain momentum, reduce miscommunication, and coordinate daily priorities without long status meetings. They are one of the most widely used rituals in Agile, Scrum, and product-led organizations.

What is a stand-up meeting?

A stand-up meeting is a focused, regular team check-in designed to keep work aligned and surface blockers quickly. Each member gives a brief update — typically answering three questions: what they did, what they plan to do, and what is blocking them. The meeting is strictly timeboxed so it stays efficient and does not expand into discussion or decision-making.

Stand-ups matter for any team that needs frequent alignment. Software engineering squads, product teams, operations groups, and cross-functional pods all benefit. For distributed or global teams, stand-ups can be synchronous (video or audio call) or asynchronous (shared notes or status updates in tools like Slack or Notion), and they should be scheduled to respect time zones.

Standard stand-up agenda

A typical stand-up follows this format and takes 5–15 minutes depending on team size:

1. Open (30 seconds). The facilitator starts the meeting on time and reminds the team of the timebox.
2. Round-robin updates (1 minute per person). Each team member answers three questions:
   • What did I complete since the last stand-up?
   • What am I working on today?
   • Is anything blocking my progress?
3. Log blockers (1–2 minutes). The facilitator captures blockers in a shared tool (Jira, Asana, Notion) and assigns owners for follow-up after the meeting.
4. Close (30 seconds). The facilitator confirms next steps, reminds the team of any upcoming deadlines, and ends the meeting on time.

Sample facilitator script: "Good morning — let's keep this to 10 minutes. We'll go round-robin starting with [name]. Share what you finished, what you're working on, and anything blocking you. I'll capture blockers in Jira and we'll follow up after. Let's go."

Roles and best practices

Facilitator (required): Keeps the meeting on time, enforces the timebox, and redirects off-topic conversations to a follow-up. Rotates weekly so no single person always runs the meeting.

Timekeeper (optional): Tracks time per person and gives a gentle signal when someone approaches their limit. Especially useful for larger teams.

Note-taker (recommended): Logs blockers and action items in a shared doc or project tool. This ensures nothing discussed in the stand-up is lost.

Best practices:

• Start on time, every time. Do not wait for latecomers. Consistency builds the habit.
• Keep updates to 30–60 seconds per person. If a topic needs more discussion, take it offline.
• Focus on blockers, not status reports. The goal is to identify what needs help, not to recite everything completed.
• Use a shared tool for follow-up. Log blockers in Jira, Asana, Trello, or Notion so they are tracked and resolved.
• Rotate the facilitator. This keeps the meeting fresh and gives everyone practice leading.

Remote and asynchronous stand-ups

Synchronous (live): Remote teams run stand-ups over video (Zoom, Google Meet) or audio (Slack huddle, Teams call). Keep cameras on when possible to maintain engagement. Schedule at a time that works across time zones — or rotate the meeting time if the team spans many zones.

Asynchronous: Team members post their three-question update in a shared Slack channel, Notion page, or dedicated stand-up tool (Range, Geekbot) at a set time each day. The facilitator reviews updates, flags blockers, and follows up as needed. Async stand-ups work well for teams spread across more than three time zones.

When to use which:

• Synchronous works best for teams in overlapping time zones (2–3 hours of overlap) and when blockers need real-time discussion.
• Asynchronous works best for globally distributed teams where finding a shared meeting time would force someone into very early or very late hours.

Team size and timing guide

• 3–5 people: 5–8 minutes. Each person gets about 1 minute.
• 6–10 people: 10–15 minutes. Keep updates tight and enforce the timebox.
• 11+ people: Split into smaller pods of 5–7 and run separate stand-ups. A single stand-up with 11+ people loses its efficiency.

Key facts

• Typical duration: 5–15 minutes, strictly timeboxed.
• Usual cadence: Daily for Agile teams. Several times a week or weekly for other teams depending on pace.
• Standard format: Each person answers — What I did yesterday. What I plan today. Any blockers.
• Ideal team size: 5–10 people per stand-up. Larger groups should split into pods.
• Remote options: Synchronous (video or Slack huddle) or asynchronous (posted updates in Slack or Notion).
• Roles: Facilitator (required), timekeeper (optional), note-taker (recommended).

Example

A distributed engineering team holds a 10-minute Zoom stand-up each morning at 9:00 UTC. Each developer gives a 30–60 second update using the three-question format. Blockers are logged as Jira issues and assigned to owners in the shared Notion notes so follow-up happens after the stand-up — not during it.

FAQ

What is a standup meeting? A short, focused team sync where members share progress, plans, and blockers — usually timeboxed to 5–15 minutes.

How long do stand-up meetings last? Most stand-ups run 5–15 minutes. Choose the shortest timebox that covers necessary updates and enforce it with a timekeeper.

What is the difference between a meeting and a stand-up meeting? A stand-up is a brief, timeboxed status sync focused on alignment and blockers. Other meetings can be longer, agenda-led, and include discussion or decision-making.

Can remote teams hold stand-up meetings? Yes. Remote teams can run synchronous video or audio stand-ups, or asynchronous stand-ups using Slack or Notion updates. Always track blockers in a shared tool.

Is a stand-up the same as a daily scrum? They are similar in purpose. A daily scrum follows Scrum rules and focuses on Sprint goals. A stand-up is a more general term used across teams and methodologies.