The daily scrum
The daily scrum is a meeting for the development team to create a plan for the day. It is not a status update for stakeholders! The product owner has no role in the daily scrum and the scrum master’s accountability is to ensure it happens, only the development team speak and the time-box is respected.
Upcoming FAQs LIVE events
Free interactive learning
13th January 2021
FAQs LIVE Special: How can you make processes and tools support individuals and interactions? In partnership with Targetprocess
20th January 2021
What are the roles in SAFe?
26th January 2021
What are the requirements in SAFe?
Visit our FAQs LIVE page for our full schedule of free webinars!
The development team inspect how they are progressing toward the sprint goal and to inspect how progress is trending toward completing the work in the sprint backlog using the three questions as a guide:
- 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?
Scrum does not specify which order to talk in and who should go first. As a self-organising unit, the development team should decide this. It is an anti-pattern for the scrum master to dictate the pattern of play during the daily scrum.
Scrum does not define when and where the daily scrum should occur. Many teams find that having a consistent time and place where they can see the sprint plan is beneficial.
The scrum master can help encourage autonomy by discouraging team members from talking directly at them, status update style.
The daily stand-up
The daily stand-up is a similar meeting to the daily scrum, without the restrictions & guidance of the Scrum guide. Similarly, the daily stand-up is to check in to see how things are progressing and if anyone needs any help. On an extreme programming team, it can be used to agree on pairing arrangements for the day.
The daily stand-up does not need to enforce the 15-minute time-box although brevity is encouraged by forcing all participants to stand up.
Finally, it does not need to limit participation to just the development team and may include others such as the product owner talking about their activities for the day to raise transparency and openness.
Recommended Training Courses
- Check out our public training course schedule
- Learn more about our Certified Professional Scrum Master
- Learn more about our Advanced Certified Scrum Master courses