Friday Night Wiki
TopicsTagsAbout
Buy me a coffee
Standups Tutorial

Chapter 1: Foundations

What standups are, what they are for, and the principles that decide whether yours is worth showing up to.

What a Standup Is

A standup (also called a daily standup or daily scrum) is a short, time-boxed meeting where a team synchronises work, surfaces blockers, and commits to the day ahead.

Key Characteristics

  • Time-boxed. 5 to 15 minutes, never longer
  • Daily. Same time, same place (physical or virtual)
  • Team-focused. About the work and collaboration, not status reporting
  • Action-oriented. Ends with clear next steps
  • Standing. Traditionally done standing to keep energy up and the duration short

The Real Purpose

What Standups Are NOT For

  • Status reports for managers
  • Detailed problem-solving
  • Sprint planning or retrospectives
  • Individual performance reviews
  • Showing how busy you are
  • Social hour and small talk

What Standups ARE For

  1. Synchronise work. Make sure everyone knows what is happening
  2. Surface blockers. Catch problems early
  3. Enable collaboration. "I need help with X" meets "I can help with X"
  4. Build cohesion. Daily face time builds trust
  5. Maintain momentum. Keep the team moving forward
  6. Create accountability. Public commitment to daily goals

Where Standups Come From

Origins in Agile and Scrum (1990s to 2000s)

  • Born from the Scrum framework
  • Designed to replace long status meetings
  • "Inspect and adapt" applied daily
  • Originally for co-located software teams

Evolution

Early 2000s   Standups spread beyond Scrum
2010s         Adapted for remote teams
2020s         Async standups become common

The core principles stay the same. Implementation varies wildly.

Core Principles

1. Self-Organisation Over Command-and-Control

The team runs the standup. A manager does not dictate orders.

Bad:

Manager: "John, what did you do yesterday?"
John:    "I worked on the login feature."
Manager: "Good. Next."

Good:

John:  "I finished the login API. Sarah, ready for you whenever
        you want to start the frontend."
Sarah: "Perfect timing. I'll start this afternoon."

2. Collaboration Over Reporting

If information only flows in one direction (team to manager), it is a report, not a standup.

Reporting mindset:

  • "I need to tell my boss what I did"
  • One person at a time, no interaction
  • Focus on justifying time spent

Collaboration mindset:

  • "How can I help my teammates succeed?"
  • Natural conversation and questions
  • Focus on moving work forward

3. Problems Over Progress

A standup where everything is "fine" and "on track" is a missed opportunity.

Surface these:

  • Blockers (cannot proceed without X)
  • Risks (might become blockers soon)
  • Confusion (not sure how to approach Y)
  • Dependencies (waiting on another team)

The best standups have problems in them. That is the point.

4. Team Over Individual

Talk about the work, not yourself.

Bad: "I worked on tickets, had meetings, reviewed PRs."

Good: "Ticket 456 is ready for QA. Ticket 789 is blocked on the API team."

5. Continuous Improvement

If your standups are not evolving, they are dying.

  • Try new formats
  • Ask for feedback
  • Drop what does not work
  • Keep what does

The Standup Triangle

Every standup balances three forces:

        EFFICIENCY
            /\
           /  \
          /    \
         /      \
   DEPTH ◁━━━━━━▷ CONNECTION
  • Efficiency. Keeping it short and focused
  • Depth. Understanding problems fully
  • Connection. Building team relationships

You cannot maximise all three at once. Choose based on context:

  • New team? Prioritise connection and depth
  • Crisis mode? Prioritise efficiency
  • Mature team? Balance all three

Types of Standups

1. Classic Round-Robin

Each person answers the three questions in turn.

Pros: Simple, predictable, everyone speaks. Cons: Can feel mechanical. People tune out until their turn. Best for: New teams, small teams (3 to 7 people).

2. Walk the Board

Go through work items on the board (Kanban, Jira, etc.) from right to left (done to to-do).

Pros: Focus on work, not people. Surfaces bottlenecks. Cons: Needs a visual board. People-based blockers are less visible. Best for: Kanban teams. Visual thinkers.

3. Yesterday's Commitments

Review what was committed to yesterday, then commit to today.

Pros: Strong accountability. Clear progress tracking. Cons: Can feel judgmental. Hard with high uncertainty. Best for: Teams with predictable work.

4. Blockers First

Start with "Who is blocked?" and address those first.

Pros: Urgent items get attention. Very fast when nothing is blocked. Cons: Can skip important updates. Harder to track overall progress. Best for: Mature teams. Crisis situations.

5. Async / Written

Everyone posts updates in Slack or Notion before standup time.

Pros: Flexible timing. Written record. Works across timezones. Cons: Less connection. Easy to skip. Harder to have dialogue. Best for: Distributed teams. Maker-schedule teams.

Each format gets its own treatment in Chapter 2.

When Standups Make Sense

Good Fit

  • Team working on interdependent tasks
  • Fast-changing priorities or context
  • Need for daily coordination
  • Complex problem-solving work
  • Remote teams that need connection
  • Multiple parallel workstreams

Poor Fit

  • Independent work with no collaboration
  • Unchanging, predictable work
  • Team meets naturally throughout the day
  • Already too many meetings
  • No shared goals or outcomes

If your team does not need a daily sync, do not have one. Try a weekly check-in instead.

The Standup Mindset

As a Participant

Your job is to:

  • Help the team succeed
  • Surface problems early
  • Be honest about challenges
  • Ask for help when needed
  • Offer help to others
  • Keep it concise

Your job is NOT to:

  • Impress your manager
  • Justify every hour worked
  • Solve problems in the standup
  • Dominate the conversation
  • Hide struggles or blockers

As a Facilitator

Your job is to:

  • Keep time and energy
  • Make sure everyone speaks
  • Park deep discussions
  • Follow up on action items
  • Protect psychological safety

Your job is NOT to:

  • Give status reports to management
  • Solve every problem raised
  • Judge people's productivity
  • Assign work
  • Make all decisions

Common Misconceptions

Myth 1: "Standups are for managers to track work"

If managers need status updates, there are better tools (dashboards, written updates). Standups are for the team.

Myth 2: "Standing up makes it better"

Standing helps keep it short. Sitting is fine if the team stays focused. Remote teams cannot stand together anyway.

Myth 3: "Everyone must speak every day"

If someone has nothing to add, "Nothing from me today" is perfectly valid. Forced participation wastes time.

Myth 4: "We must use the three questions"

The three questions are training wheels. Mature teams often outgrow them.

Myth 5: "15 minutes is the rule"

15 minutes is a maximum. Many teams run effective 5 to 7 minute standups. Shorter is often better.

Myth 6: "Standups must be synchronous"

Async standups work well for distributed teams across time zones.

The Standup Maturity Model

Level 1: Status Theatre

  • Manager asks each person for updates
  • Team members report activities
  • No interaction between team members
  • Focus on looking busy
  • Outcome: Waste of time

Level 2: Mechanical Ritual

  • Team follows the format religiously
  • Everyone answers three questions
  • Minimal interaction or questions
  • Information goes out
  • Outcome: Mildly useful

Level 3: Team Sync

  • Team discusses work collaboratively
  • Problems get surfaced and assigned
  • Natural conversation within structure
  • People help each other
  • Outcome: Actually valuable

Level 4: Self-Optimising

  • Team adapts the format to its needs
  • Psychological safety enables honesty
  • Proactive problem-solving
  • Continuous improvement
  • Outcome: Force multiplier

Most teams get stuck at Level 2. This guide aims to get you to Level 4.

Red Flags

Watch for these warning signs:

  • People arrive late regularly. Standup is not valuable enough
  • It runs longer than 15 minutes. No focus or facilitation
  • Only managers ask questions. Team is not engaged
  • Same blockers every day. Nothing gets resolved
  • People multitask during standup. Not worth their attention
  • Detailed technical discussions. Conversations are not being parked
  • Team members do not know what others are doing. Not listening
  • No one ever asks for help. No psychological safety

Measuring Success

Quantitative Signals

  • Standup duration (shorter is often better)
  • Attendance rate (should be above 90%)
  • Blockers surfaced per week
  • Time to resolve blockers
  • Number of follow-up conversations

Qualitative Signals

  • Team members arrive prepared and on time
  • Energy during standup
  • Quality of collaboration after standup
  • Team's ability to self-organise
  • Psychological safety (people share struggles)

The Ultimate Test

If your standup were cancelled tomorrow, would the team miss it?

If the answer is "No" or "We would be relieved," your standup needs work.

Key Takeaways

  1. Standups exist to help the team collaborate, not to report to managers
  2. The best standups surface problems early so they can be solved
  3. Different teams need different standup formats
  4. Shorter is almost always better than longer
  5. Psychological safety is essential for effective standups
  6. If you do not need daily sync, do not run a daily standup
  7. Standups should evolve as your team matures

Next Steps

Continue to 02-structure.md for the formats, timing, and organisation of effective standups.