Too long, didn’t read?

The Scrum Guide is short, concise and informative. I encourge you to read it. But if it’s too long to you, or you need to onboard a busy team, follow me on my new blog series 2-Minute Scrum for Busy Teams — a bite-size, per-chapter, bullet-point summary of The Scrum Guide.

Daily Scrum

Daily Scrum is:

  • a key inspect and adapt meeting
  • 15-minute time-boxed event
  • an internal meeting for Development Team
  • held every day of the Sprint
  • held at the same time and place each day to reduce complexity

Daily Scrum:

  • focuses on the progress toward the Sprint Goal
  • inspects - the work since the last Daily Scrum
  • adapts - upcoming Sprint work

  • optimizes team performance and the probability to meet the Sprint Goal
  • can be structured differently by Development Team (e.g. asking questions, or discussion based)

Development Team:

  • plans work for next 24 hours
  • inspects progress toward the Sprint Goal and completing the work in Sprint Backlog
  • often meet after Daily Scrum for detailed discussions, or to adapt or replan the rest of the Sprint’s work

Scrum Master:

  • ensures Development Team has the meeting, but Development Team is responsible for conducting
  • teaches Development Team to keep the 15-minute time-box
  • ensures others do not disrupt the meeting, if they are present

Why Daily Scrum?

  • improves communications and eliminates other meetings
  • identify impediments to development for removal
  • highlight and promote quick decision-making
  • improve Development Team’s level of knowledge

Read the full text in The Scrum Guide.

In 2-Minute Scrum for Busy Teams series