Chapter 2: Structure | Standups

Choosing the Right Format

No single standup format works for every team. Choose based on:

Team size
Team maturity
Type of work
Co-located vs. distributed
Team culture and preferences

Format 1: Classic Round-Robin

Each person answers three questions in turn.

The Three Questions

What did I complete yesterday/since last standup?
What will I work on today/until next standup?
What's blocking me or slowing me down?

How It Works

Person 1 → Person 2 → Person 3 → ... → Person N

Each person speaks for 1-2 minutes maximum.

Variations on the Questions

Achievement-focused:

What did I accomplish?
What will I accomplish?
What could prevent me from accomplishing it?

Commitment-focused:

What did I commit to? Did I do it?
What am I committing to today?
What might prevent me from keeping my commitment?

Team-focused:

How did I help the team yesterday?
How will I help the team today?
What does the team need from me?

When to Use

✅ Best for:

Small teams (3-7 people)
New teams learning standups
Teams new to Agile
When everyone needs to speak

❌ Avoid when:

Team is larger than 10 people
Work isn't collaborative
Team is distributed across timezones

Pro Tips

Vary the starting person: Don't always go alphabetically
Use a talking token: Pass a physical/virtual object
Set a timer: 2 minutes max per person
No interruptions during rounds: Save questions for after

Format 2: Walk the Board

Review work items on your board from right to left (or top to bottom).

How It Works

DONE → IN PROGRESS → TO DO
  ↓         ↓          ↓
Review   Discuss    Identify
closed   active     next items
items    items      to pull

Start with the rightmost column (done/completed) and move left.

The Script

Done: "Is this truly done? Who needs to know about it?"
In Review/Testing: "When will this be done? Any blockers?"
In Progress: "Is anyone working on this? When will it be ready?"
Blocked: "What's the blocker? Who can unblock it?"
To Do: "What should we pull next?"

When to Use

✅ Best for:

Kanban teams
Visual thinkers
Flow-based work
Identifying bottlenecks
Teams of 5-12 people

❌ Avoid when:

No visual board exists
Work doesn't fit into discrete items
Team works on many parallel efforts

Pro Tips

Focus on exceptions: Skip items that are progressing normally
Look for pileups: Multiple items in one column = bottleneck
Age items: Highlight items that haven't moved in 2+ days
Color-code blockers: Make blocked items visually obvious

Format 3: Yesterday's Commitments

Review what was committed to yesterday, then make today's commitments.

How It Works

Phase 1: Review (5 minutes)

For each person:
- Did you complete what you committed to?
- If not, why not? (no judgment, just facts)

Phase 2: Commit (5 minutes)

For each person:
- What are you committing to today?
- Is it realistic given yesterday's completion?

Commitment Guidelines

Good commitments:

Specific: "Finish the user API endpoint"
Achievable in one day
Clear definition of done
Visible to everyone

Bad commitments:

Vague: "Work on the feature"
Multi-day: "Complete the entire module"
Unmeasurable: "Make progress"

When to Use

✅ Best for:

Teams needing stronger accountability
Predictable work
Short-cycle work (tasks completable in 1-2 days)
Teams building discipline

❌ Avoid when:

Work is highly uncertain
Tasks regularly span multiple days
Team is new and learning
Psychological safety is low (feels punitive)

Pro Tips

No shame for missing commitments: Focus on learning
Track commitment accuracy: Helps with estimation
Adjust scope: Better to commit to less and deliver
Celebrate kept commitments: Positive reinforcement

Format 4: Blockers First

Start with "Who's blocked?" and handle those first.

How It Works

Round 1: Blockers (3-5 minutes)

Facilitator: "Who's blocked or has risks to share?"
[Only blocked people speak]
[For each blocker: identify who will help and when]

Round 2: Quick Updates (3-5 minutes)

Everyone else: one-sentence update if needed
"Working on X, will finish today"
"Nothing from me"

Blocker Categories

External blockers:

Waiting on another team
Infrastructure issues
Third-party dependencies
Approval needed from outside team

Internal blockers:

Need help from teammate
Don't understand requirements
Technical decision needed
Conflicting priorities

When to Use

✅ Best for:

Mature teams with good self-organization
Fast-paced, crisis situations
Teams with clear ownership
When blockers are frequent

❌ Avoid when:

Team needs more coordination
Important updates get lost
New team members
Manager needs visibility

Pro Tips

Define "blocked": Distinguish between "stuck" and "would like help"
Assign owner to each blocker: Someone commits to unblocking
Set follow-up time: "Let's chat at 10:30"
Track blocker resolution time: Improve your processes

Format 5: Async/Written Standups

Everyone posts their update in a shared space (Slack, Notion, etc.).

How It Works

Daily by 9am (or team's chosen time):

Each person posts:
✅ Yesterday: [completed items]
🎯 Today: [planned items]
🚫 Blockers: [issues or none]

Team reads and responds asynchronously.

Platform Options

Slack/Discord:

Dedicated #standup channel
Threads for discussions
React with emoji for "read it"

Notion/Confluence:

Daily page per person
Archive old updates
Easier to search history

Dedicated tools:

Geekbot
Standuply
Dailybot
Range
Standup Alice

When to Use

✅ Best for:

Distributed teams across time zones
Teams with deep work focus (minimize interruptions)
Introverts who communicate better in writing
Teams with async culture

❌ Avoid when:

Team needs face-time
Rapid collaboration required
Written communication is poor
People skip reading them

Pro Tips

Set clear expectations: When to post, what to include
Make it public: Don't DM the facilitator
React to show you've read: Thumbs up, emoji, etc.
Have a weekly sync: Video call to build connection
Automate reminders: Bot reminds people to post

Hybrid Format

Combine written async updates with a shorter sync meeting.

How It Works

Before meeting:

Everyone posts written update
Team reads updates

During 5-minute meeting:

Skip routine updates
Only discuss blockers and collaboration needs
"Anyone need to go deeper on something?"

When to Use

✅ Best of both worlds for distributed teams that want connection but respect focus time

Timing Best Practices

Time of Day

Morning (most common):

Pros: Sets direction for the day, builds momentum
Cons: People arrive at different times, morning chaos
Best time: 9:30-10:00am (after people settle in)

Midday:

Pros: Everyone's present, check afternoon plans
Cons: Interrupts deep work
Best time: 12:00pm (lunch boundary)

End of day:

Pros: Review what was accomplished, plan next day
Cons: Energy is low, people leave early
Best time: 4:00-4:30pm

Choose based on your team's natural rhythm.

Frequency

Daily: Standard for most teams
3x/week (Mon/Wed/Fri): For teams with longer-cycle work
After every deploy: For continuous delivery teams
Never: For independent workers with no shared goals

Duration

Target: 5-10 minutes for most teams

Team Size	Target Duration
3-5 people	5 minutes
6-8 people	7-10 minutes
9-12 people	12-15 minutes
13+ people	Split into sub-teams

If your standup regularly exceeds 15 minutes, something is wrong.

Physical Setup

Co-located Teams

Stand in a circle:

Everyone sees everyone
No head of table
Natural eye contact

Stand near your board:

Easy to reference work items
Visual alignment
Reduces "where were we?" confusion

Same place every day:

No time wasted finding the team
Builds ritual and routine

Remote Teams

Video on, always:

Builds connection
Nonverbal communication matters
Shows respect and engagement

Gallery view:

See everyone simultaneously
Notice who's distracted
More engaging than speaker view

Stable backgrounds:

Minimize distractions
Professional appearance
Good lighting on faces

Facilitation Techniques

Starting on Time

Don't wait for latecomers.

Waiting punishes on-time people
Rewards late behavior
Shows standup isn't important

Start exactly at the scheduled time, even if people are missing.

Keeping Time

Use a timer:

Visible countdown clock
2-minute warning
Gentle but firm time enforcement

Park discussions:

"Great topic. Let's discuss after standup."
Write it on a "parking lot" list
Commit to follow-up time

Interrupt politely:

"Thanks John. To keep us on time, let's take details offline."
"I'm hearing a blocker. Who can help John after standup?"

Keeping Energy

Vary the routine:

Change who goes first
Try a different format
Add a quick team-building question

Stand up (if co-located):

Literally standing keeps energy up
Discourages rambling
Makes long standups uncomfortable (which is good)

Start with wins:

"Any wins to celebrate?"
30 seconds of positivity
Builds momentum

Running Your First Standup

Before First Standup

Explain the purpose: Why we're doing this
Set expectations: Format, timing, behavior
Choose format: Start with round-robin if unsure
Pick a time: Survey team for preferences
Set location: Physical or virtual

First Standup Script

"Good morning! This is our first standup. The goal is to sync on work,
surface blockers, and help each other. We'll keep it to 10 minutes.

Format: Each person shares:
- What they completed yesterday
- What they're working on today  
- Any blockers

I'll go first as an example, then we'll go around the circle.

[Your update]

[Point to next person]"

After First Standup

Immediate retrospective: "How did that feel?"
Adjust next time: Based on feedback
Set next standup: Same time tomorrow

Rotating Facilitator

Don't let one person always run standup.

Benefits

Shared ownership
Leadership development
Prevents facilitator burnout
Everyone learns facilitation skills

How to Rotate

Daily rotation:

Monday: Alice
Tuesday: Bob  
Wednesday: Carol
Thursday: David
Friday: Alice

Weekly rotation:

Week 1: Alice
Week 2: Bob
Week 3: Carol
Week 4: David

Facilitator Responsibilities

Start on time
Keep energy and pace
Enforce time limits
Park detailed discussions
Ensure everyone speaks (if using round-robin)
Capture action items
End clearly

Ending the Standup

Clear Close

Bad ending: "Okay, I guess that's everything. Bye."

Good ending: "Great standup. Three action items:

Bob will unblock Sarah by noon
Alice and Carol will chat about the API design at 2pm
David will follow up with the ops team today

Thanks everyone. Let's crush it today."

Action Item Tracking

Capture during standup:

Who will do what
By when
Write it down visibly

Follow up:

Check action items in next standup
If not done, reassign or reprioritize
Don't let action items linger

Common Structural Problems

Problem: Standup Takes Too Long

Solutions:

Enforce 2-minute per person limit
Use timer with alarm
Try "blockers first" format
Park all detailed discussions
Split large teams

Problem: Not Everyone Speaks

Solutions:

Use explicit round-robin
Ask quiet people directly: "Sarah, anything from you?"
Create psychological safety (Chapter 4)
Allow "nothing from me today"

Problem: People Arrive Late

Solutions:

Start exactly on time
Don't restart for latecomers
Rotate late people to go last
Address chronic lateness 1-on-1

Problem: Detailed Technical Discussions

Solutions:

Facilitator interrupts: "Let's take this offline"
Create parking lot list
Schedule follow-up immediately after
Train team to recognize when they're too deep

Key Takeaways

Choose format based on your team's needs, not what's "supposed" to be done
Shorter is almost always better: aim for 5-10 minutes
Start and end on time, no exceptions
Park detailed discussions for after the standup
Rotate facilitation to build shared ownership
Experiment and evolve: standups should change as your team matures
Async standups work great for distributed teams across timezones

What's Next

Now that you know how to structure standups, let's learn how to communicate effectively within them:

→ Chapter 3: Communication: Master the art of standup communication