The Daily Scrum Defined

May 8th 2014 (updated Apr 3rd 2023)

agilescrum

The Daily Scrum is a synchronization, inspection, and adaptive planning activity that a development team performs each day.

Defined

A synchronisation, inspection, and adaptive planning activity that a development team performs each day.

The "Rules" according to Scrum

  • Maximum of 15 Minutes long
  • Occur at the same time & place
  • Covers the following:
    • What has been accomplished
    • What will be done
    • What obstacles
  • Conducted by those actively doing the work
  • Only for those doing the work (not for other stakeholders)
  • Not a status reporting meeting to other stakeholders/management

Expected Characteristics of the Daily Scrum

  • Occur first thing (as soon as the development is together)
  • Focused - the daily scrum should be focused on the work completed, impediments and work to be done in between the daily meetings.
  • High level - 15 minutes is not enough time for in depth discussions
  • Not a problem solving meeting - There is not enough time to get into the detail of the majority of issues, talk about a plan for solving a problem (such as a follow-up meeting) rather than trying to formulate a solution there and then
  • Impediment gathering - One of the outcomes of the Daily Scrum is a list of issues (e.g. on whiteboard) that require immediate attention
  • Not a management status report - The is not for updating stakeholders, it is for planning how the day's work will be completed
  • Stakeholders can observe - Anyone is allowed to attend the Daily Scrum providing they abide by the scrum rules and are only there as observers
  • Stand-up - The team should stand up during the meeting to encourage the expediency & focus of the meeting (the daily stand-up)
  • Prompt - starts at the same time each day to reduce any confusion, regardless and lateness is not tolerated
  • Have follow-up meetings - it's not unusual for a Daily Scrums to organise a follow up meeting if needed, providing the opportunity to discuss issues raised in more depth, these will typically be immediately after the daily scrum
  • Motivate/Good start - Since the Daily Scrum occurs as soon as the Development Team is together, it is the perfect opportunity to start the day in positive way

References

  1. Kenneth S. Rubin (2012). Essential Scrum. Addison-Wesley Professional.
  2. Schwaber, Ken, and Jeff Sutherland (2011), 'The Scrum Guide'. [Online] Available from: www.scrum.org [Accessed 26 January 2014]
  3. CollabNet, How To Have An Effective Daily Scrum. When The 15 Minute Meeting Takes Longer Than 15 minutes. [Online] Available from: http://blogs.collab.net/agile/how-to-have-an-effective-daily-scrum-when-the-15-minute-meeting-takes-longer-than-15-minutes [Accessed 7 March 2014].
  4. Base36, How to Run an Effective Scrum Meeting. [Online] Available from: http://www.base36.com/2013/03/how-to-run-an-effective-scrum-meeting/ [Accessed 7 March 2014].
  5. Mountain Goat Software, Daily Scrum Meeting. [Online] Available from: http://www.mountaingoatsoftware.com/agile/scrum/daily-scrum [Accessed 7 March 2014].
  6. Agile Alliance, Daily Meeting. [Online] Available from: http://guide.agilealliance.org/guide/daily.html [Accessed 7 March 2014]
  7. MSDN, Daily Scrum Meeting. [Online] Available from: http://msdn.microsoft.com/en-us/library/ee191590(v=vs.100).aspx [Accessed 7 March 2014].