# Running Effective Standups — Quick Reference

## Purpose

**Coordination, not reporting.** Align the team, surface blockers, decide who talks to whom.

## Formats

| Format | How It Works | Best For |
|--------|--------------|----------|
| Three questions | What I did, what I'll do, blockers | Traditional Scrum |
| Walk the board | Column by column, work-focused | Kanban, visual teams |
| Blockers first | "Anyone blocked?" then optional focus | High-dependency teams |
| Async | Post by deadline (Slack, doc, video) | Distributed, flex schedules |

## Timeboxing

- **Max 15 minutes** — preferably 10 or less
- **Take it offline:** "Let's sync on that after standup"
- Use a timer; when someone drones, gently redirect

## Anti-Patterns

| Avoid | Do Instead |
|-------|------------|
| Status report to manager | Facilitate for team; manager observes or skips |
| Problem-solving in standup | "Grab 2–3 people after" |
| Running long | Timebox; move discussions offline |
| Low energy / no one listening | Change format; make it interactive |

## Async Template

```
Yesterday: [1–2 bullets]
Today: [1–2 bullets]
Blockers: [none / describe]
```

**Tools:** Slack, Loom, Geekbot, Standuply, shared doc.

## Remote Tips

1. Cameras on
2. Screen share the board
3. Rotate facilitators
4. Use chat for follow-ups
5. Stable video/audio

## When to Skip

- Work is highly independent
- Team is very small (2–3) and in constant contact
- No one finds value after trying formats

## Sync vs Async

| Sync | Async |
|------|-------|
| Real-time coordination | Flexibility, no meeting |
| Good for: high coordination | Good for: independent work |
| Requires same-time availability | Post by deadline |