Dangers of a Status Meeting

• End up with a project manager type role and people reporting updates. This is normally the PO or scrum master

• Loses meaning - inspection and adaption becomes monitoring and being told what to do

Why do the daily Scrum?

“Daily Scrum optimizes team collaboration and performance by inspecting the work since the last Daily Scrum and forecasting upcoming Sprint work”

Scrum Guide

What is the daily Scrum For?

“The Development Team uses the Daily Scrum to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog. The Daily Scrum optimizes the probability that the Development Team will meet the Sprint Goal.”

Scrum Guide

Sprint Goal

Once the sprint goal is set, nothing is done to endanger it. Once the sprint begins, no one, no one tells the development team what to do. What the product owner can do however is clarify and re-negotiate the scope as more is learnt.

The suggested questions in the Scrum guide for the daily scrum are orientated around the sprint goal

• What did I do yesterday that helped the Development Team meet the Sprint Goal?

• What will I do today to help the Development Team meet the Sprint Goal?

• Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?

A lot of teams will explore this further and include things such as

• Avalaibitly to help with pairing with other team members

• Support/monitoring updates

• Inspecting and adapting the sprint plan - e.g. changes to who is doing what or picking up the next ticket from

• If people are stuck, need help or advice

• Chasing code reviews

• Informing other team members they have questions e.g. need to check how the UI will work or I need to ask the PO questions to further clarify the requirements