Skip to main content

Daily Standup

The Daily Standup synchronizes the team, surfaces blockers early, and enables rapid course correction.

Overview​

Daily Standup is a 15-minute timeboxed meeting where the team synchronizes on progress, plans for the day, and identifies blockers. The ceremony addresses a fundamental challenge of software development: individual developers working on interconnected code need frequent synchronization to avoid conflicts, duplication, and misalignment.

Without daily standup, developers operate in silos - only discovering integration issues, blocked progress, or conflicting approaches when it's expensive to fix. The daily cadence creates a forcing function for early detection and rapid course correction. Fifteen minutes of synchronization prevents hours or days of wasted effort.

Standup Purpose

Standup is not a status report to management. It's a synchronization point for the team to help each other succeed. The team talks to each other, not to the Scrum Master. If developers find themselves facing the Scrum Master while reporting progress, the standup has devolved into theater rather than teamwork. Focus on collaboration, not reporting.

Core Principles​

  • Timeboxed: Strict 15-minute limit
  • Daily: Same time every day for consistency
  • Team-Focused: Team members talk to each other, not to Scrum Master
  • Action-Oriented: Identify and resolve blockers quickly
  • Stand-Up: Physical standing keeps meetings short (optional for remote)

Standup Format​

Standard Three Questions​

Each team member answers:

  1. What did I complete yesterday?

    • Focus on completed work towards sprint goal
    • Mention specific stories/tasks
    • Highlight achievements

  2. What will I work on today?

    • State planned work aligned with sprint goal
    • Identify which stories/tasks
    • Flag any changes in priority

  3. Are there any blockers?

    • Technical blockers
    • Waiting on others
    • Unclear requirements
    • External dependencies

Example Updates​

Good Update:

Yesterday:
- Completed payment API endpoint (PAYMENT-123)
- Finished unit tests with 95% coverage
- Code review completed and merged

Today:
- Start integration tests for payment API
- Update OpenAPI specification
- Review Sarah's PR for validation logic

Blockers:
- Waiting on DevOps for staging database access (escalated to Slack)

Poor Update:

Yesterday: Worked on stuff
Today: Continue working on same thing
Blockers: None

(Too vague, not actionable)

Standup Structure​

Timing (15 minutes total)​

Minutes 0-12:  Team member updates (1-2 min each)
Minutes 12-14: Blocker discussion and next steps
Minute 14-15:  Parking lot items for follow-up

Facilitation​

Scrum Master Role:

  • Timekeeping (use visible timer)
  • Keep discussion on track
  • Note blockers for follow-up
  • Defer detailed discussions

Speaking Order:

  • Rotate daily (prevents routine)
  • Options: alphabetical, random, walking the board
  • Person who spoke last picks next speaker

Handling Blockers​

Blocker identification is the most critical function of daily standup. A blocker identified on day 2 of the sprint can be resolved with minimal impact. The same blocker hidden until day 8 becomes a sprint failure. The daily cadence creates accountability - team members know they'll face the team tomorrow, making it psychologically difficult to hide problems.

Blocker Categories​

Understanding blocker types helps teams route them to appropriate resolution mechanisms:

1. Technical Blockers (knowledge or skill gaps):

  • Unclear requirements -> Schedule refinement with Product Owner immediately, don't guess
  • Technical unknowns -> Pair programming session with experienced developer, or time-boxed spike
  • Infrastructure issues -> Escalate to DevOps/Platform team with clear request and urgency

2. Dependency Blockers (waiting on others):

  • Waiting on another team -> Follow up immediately after standup with specific ask and deadline
  • Waiting on stakeholder -> Scrum Master escalates with business impact context
  • Waiting on code review -> Assign reviewers in standup, set expectation for same-day review

3. Personal Blockers (individual challenges):

  • Unfamiliar technology -> Pair with experienced team member, don't suffer alone
  • Stuck on problem -> Schedule knowledge sharing session, or ask for fresh eyes on the problem

The key insight: blockers are normal and expected. High-performing teams surface blockers early and resolve them quickly. Low-performing teams hide blockers until they explode into crisis.

Blocker Resolution Process​

Immediate Actions:

  • Assign owner to each blocker
  • Set deadline for resolution
  • Escalate if needed
  • Follow up outside standup

Remote Standup Best Practices​

Tools and Setup​

Video Conferencing:

  • Cameras on (builds connection)
  • Good lighting and audio
  • Minimize background noise
  • Use headphones

Virtual Board:

  • Screenshare Jira board
  • Walk through stories visually
  • Update status in real-time

Engagement Techniques​

Prevent Multitasking:

  • Use "raise hand" feature
  • Call on people randomly
  • Interactive board walking

Visual Aids:

  • Screenshare current sprint board
  • Use explicit status labels: On Track, At Risk, Blocked
  • Highlight blockers in red

Async Standup Alternative​

For distributed teams across time zones, synchronous daily meetings may be impractical or unfair (requiring some team members to join at unreasonable hours). Async standups sacrifice real-time collaboration but maintain visibility and accountability:

Written Updates (Slack/GitLab)​

Daily Update Format:

## Standup Update - 2025-01-28

**Yesterday**:
- [Good] PAYMENT-123: Completed payment API endpoint
- [Good] Code review for Sarah's validation PR

**Today**:
-  PAYMENT-124: Start integration tests
-  Update OpenAPI specification

**Blockers**:
-  Waiting on staging DB access from DevOps (escalated)

**Help Needed**:
- Need review on PR #456 (high priority)

Async Standup Guidelines​

Timing:

  • Post updates by 9 AM local time
  • Read all updates by 10 AM
  • Respond to blockers within 1 hour

Follow-Up:

  • Quick sync calls for complex blockers
  • Scrum Master monitors and escalates
  • Team members help each other async

When to Have Live Standup:

  • Beginning of sprint
  • Major blockers or risks
  • Team requests synchronous discussion
  • Weekly (even with async model)

Common Anti-Patterns​

Status Report to Manager​

Problem: Team members report to Scrum Master/manager instead of team Solution: Team members face each other, not the Scrum Master

Going Over Time​

Problem: Standup regularly exceeds 15 minutes Solution:

  • Strict timekeeping with visible timer
  • Defer detailed discussions to "parking lot"
  • Limit individual updates to 1-2 minutes

Solving Problems in Standup​

Problem: Team tries to solve complex problems during standup Solution:

  • Note problem
  • Assign follow-up discussion
  • Keep standup moving

Passive Listening​

Problem: Team members zone out during others' updates Solution:

  • Interactive board walking
  • Encourage questions and offers to help
  • Rotate facilitation

No Blockers Ever​

Problem: Team never raises blockers (fear of appearing stuck) Solution:

  • Create safe environment
  • Celebrate early blocker identification
  • Show blockers are normal and expected

Standup Checklist​

Preparation​

  • Jira board updated before standup
  • Previous day's work completed/updated
  • Today's work identified
  • Blockers documented

During Standup​

  • Started on time
  • All team members present (or async update)
  • Each person provided update (1-2 min)
  • Blockers identified
  • Blocker owners assigned
  • Parking lot items noted
  • Finished within 15 minutes

After Standup​

  • Blockers addressed immediately
  • Follow-up discussions scheduled
  • Escalations communicated
  • Board reflects current state

Measuring Standup Effectiveness​

Key Metrics​

Duration:

  • Target: <15 minutes
  • Track average over sprint
  • Identify patterns causing overruns

Blocker Resolution Time:

  • Target: <1 day
  • Track time from identification to resolution
  • Identify systemic issues

Attendance:

  • Target: >95% attendance
  • Track trends
  • Address consistent absences

Team Satisfaction:

  • Survey: "Is standup valuable?" (1-5 scale)
  • Target: >4.0 average
  • Collect feedback in retrospectives

Further Reading​

Summary​

Key Takeaways:

  1. Strict Timeboxing: 15 minutes maximum, use timer, defer detailed discussions
  2. Team Synchronization: Team talks to each other, not to Scrum Master
  3. Three Questions: What I did, what I'll do, blockers
  4. Immediate Action on Blockers: Assign owners, set deadlines, escalate if needed
  5. Consistent Schedule: Same time daily for predictability
  6. Async Alternative: Written updates for distributed teams with weekly sync
  7. Prevent Status Reporting: Focus on collaboration and helping each other
  8. Interactive Engagement: Walk the board, encourage questions and offers to help