Daily Scrum Explained: Purpose, Format and Scrum Master Role

The Daily Scrum is a short daily event where Developers inspect progress toward the Sprint Goal and adapt their plan when necessary.

It is often misunderstood as a status meeting. It is actually a planning and inspection event for the Developers.

Purpose of the Daily Scrum

The main purpose is to answer one important question:

Are we making good progress toward the Sprint Goal, and what should we change?

Who Participates?

The Daily Scrum is an event for the Developers of the Scrum Team.

If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers.

How Long Is It?

The Daily Scrum is limited to 15 minutes.

The Developers can decide the format and techniques they use, provided the event focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work.

Does It Have to Use Three Questions?

No.

The Scrum Guide does not prescribe the traditional "What did I do yesterday?", "What will I do today?", and "What are my impediments?" format.

Teams can use those questions, but they can also use another format that achieves the purpose of the Daily Scrum.

Example

Suppose the Sprint Goal is:

Improve the checkout experience for customers.

During the Daily Scrum, the Developers discover that an important payment integration is delayed.

Instead of simply reporting the problem, they discuss how the Sprint Backlog should be adapted and agree on the next steps.

What Makes a Good Daily Scrum?

  • Focuses on the Sprint Goal.
  • Discusses progress and emerging problems.
  • Results in an actionable plan.
  • Encourages collaboration between Developers.
  • Stays within 15 minutes.

Common Mistakes

Status Meeting Reporting to a manager instead of planning the work.
Long Discussions Turning the Daily Scrum into a detailed problem-solving meeting.
Task Reporting Focusing on individual activities instead of the Sprint Goal.
Scrum Master Control Making the Scrum Master run the event every day.

What Is the Scrum Master's Role?

The Scrum Master helps the team understand the purpose of the Daily Scrum and supports an environment where Developers can conduct it effectively.

The Scrum Master does not need to stand in front of the team and ask each person for a status update.

If a detailed technical discussion is needed, the people involved can continue that discussion after the Daily Scrum.

Remember:

The Daily Scrum is not: "What did everyone do?"

It is about: "How are we progressing toward the Sprint Goal, and what should we do next?"

Key Takeaway

A successful Daily Scrum helps Developers inspect progress, adapt their plan and coordinate their work.

The format can vary, but the purpose should remain clear.

What Comes Next?

After the Daily Scrum, the next major Scrum event we will explore is the Sprint Review.