Daily Standup (Daily Scrum)

Overview

The Daily Standup (also called Daily Scrum) is a brief, time-boxed meeting within agile methodologies where development teams synchronize their work, discuss progress, and identify any obstacles. It's a core practice in Scrum and other agile frameworks designed to foster collaboration and adaptability.

Key Characteristics

• Duration: Maximum 15 minutes (strictly time-boxed)
• Frequency: Every working day
• Timing: Same time and place each day
• Participants: Development team (mandatory), Scrum Master and Product Owner (optional)
• Format: Quick check-in, not detailed problem-solving
• Standing: Traditionally held standing up to keep it brief

Traditional Three Questions

Historically, each team member answered:

1. What did I do yesterday to help the team achieve the sprint goal?
2. What will I do today to help the team achieve the sprint goal?
3. What obstacles are keeping me or the team from reaching the sprint goal?

Note: The 2020 Scrum Guide removed these specific questions, emphasizing that teams should focus on progress toward the sprint goal in whatever way works best for them.

Modern Approach

Instead of rigid questions, teams now focus on:

• Progress toward sprint goal
• Planned work for the day
• Impediments and blockers
• Opportunities for collaboration
• Emerging risks or issues
• Adjustments needed to stay on track

Benefits

For Teams:

• Promotes daily collaboration and communication
• Increases transparency across team
• Identifies blockers quickly before they become major issues
• Fosters accountability and commitment
• Improves team coordination
• Builds team cohesion and trust
• Reduces need for other meetings

For Projects:

• Keeps everyone aligned on goals
• Enables rapid course correction
• Improves productivity through coordination
• Surfaces dependencies early
• Maintains sprint momentum
• Reduces risk of sprint failure

Best Practices

Timing and Structure:

• Hold at same time every day
• Keep strictly to 15 minutes
• Start on time even if people are late
• Use timer to enforce time limit
• Stand up (if in person) to encourage brevity
• Schedule at time that works for all team members

Participation:

• Development team speaks; others listen
• Focus on team progress, not individual reports
• Avoid solving problems in the standup
• Take detailed discussions offline
• Ensure everyone participates
• Create psychological safety for sharing blockers

Content:

• Focus on sprint goal achievement
• Keep updates brief and relevant
• Flag blockers but don't solve them now
• Coordinate handoffs and dependencies
• Avoid status reporting to manager
• Discuss work, not people

Common Mistakes

Anti-Patterns to Avoid:

• Exceeding 15-minute timebox
• Detailed problem-solving during standup
• Status reporting to manager instead of team sync
• Only talking to Scrum Master instead of team
• Skipping standups when "nothing changed"
• Using as performance review
• Letting one person dominate
• Not actually standing up (in person)
• Irregular scheduling

Warning Signs:

• Team members checking out
• Consistently going over time
• Focus on completed tasks not progress toward goal
• Lack of interaction between team members
• People arrive unprepared
• Blockers mentioned but not addressed
• Feels like burden rather than valuable

Variations

Format Variations:

• Walk the Board: Review work items on board instead of round-robin
• Asynchronous: Written updates in Slack/Teams for distributed teams
• Topic-Based: Focus on specific sprint goal areas
• Parking Lot: Use board to capture offline discussion topics

Remote Team Adaptations:

• Video conference with cameras on
• Use virtual backgrounds for fun
• Digital collaboration board
• Rotating facilitator
• More structured turn-taking
• Async standups via written updates

Facilitation Tips

For Scrum Masters:

• Arrive early and prepare
• Keep team focused on goal
• Protect from outside interruptions
• Note impediments for follow-up
• Enforce timebox gently but firmly
• Encourage team self-organization
• Model desired behaviors

Keeping It Engaging:

• Rotate who goes first
• Use visual board to focus discussion
• Celebrate small wins
• Keep energy positive
• Vary format occasionally
• Use icebreakers occasionally

Time of Day Considerations

Morning Standups:

• Set direction for the day
• Everyone shares plans while fresh
• Common choice for co-located teams

Mid-Morning:

• People have time to review work first
• Avoids very early scheduling conflicts
• Good for distributed teams across time zones

End of Day:

• Reflect on day's progress
• Plan for next day
• Less common but works for some teams

Connection to Other Practices

• Sprint Planning: Sets context for daily standups
• Sprint Review: Benefits from daily coordination
• Sprint Retrospective: Addresses standup effectiveness
• Backlog Refinement: Informed by standup discussions
• Pair Programming: Coordination happens in standup

Measuring Success

Indicators of Effective Standups:

• Team members look forward to it
• Consistently under 15 minutes
• Blockers get resolved quickly
• Team coordination improves
• Surprises at sprint review decrease
• Team self-organizes better
• Sprint goals achieved more consistently

For Different Frameworks

• Scrum: Core ceremony, called Daily Scrum
• Kanban: Daily standup optional but recommended
• XP: Daily standup standard practice
• SAFe: Team sync at multiple levels
• Non-Agile: Can adapt concept as daily team sync

Tools and Technology

• Video conferencing for remote teams
• Digital board (Jira, Trello, Azure DevOps)
• Timer/countdown clock
• Collaboration tools for async updates
• Virtual whiteboard for notes
• Meeting recording for absent team members