Scrum Events : Daily Scrum

Also known as the stand-up, this meeting is where the Scrum framework derives its name.

The Daily Scrum is where the Development team Inspects and Adapts their approach, and continuously Plans their sprint work as they do it

The daily scrum happens every day, same place, same time. 

  • The meeting provides opportunities for the natural evolution of self-organisation and collaboration
  • It is also one of several inspection and adaption points provided by the scrum framework, and is done in the open, enhancing transparency (The three pillars of agile are Inspection, Adaption and Transparency)
  • Collaborative planning maturally emerges as the Development team works through the three questions of Scrum
  • 15 minute time-box irrespective of team size or sprint duration

The Three Questions of Scrum

Original scrum emphasised three questions to be answered at the daily scrum

  • What did I do yesterday
  • What will I do today
  • What are my impediments

There is a problem with this approach because questions are often reported as activities, and impediments are often reported as issues, commonly referred to as ‘blockers’.  To address that, our recommended questions are slightly different, in order to have deliverables focused approach to reporting, and an inclusion of risks as well as issues

  • What did I complete yesterday
  • What will I complete today
  • What are my risks and issues

The scrum daily is time-boxed to 15 minutes, to avoid getting off topic. Sidebars are noted for discussion outside the meeting. Risks and issues that cannot be handled by the team are escalated to the scrum master.

Key rule: Only Development Team members have speaking rights at the daily scrum, although the Product Owner may be available to provide clarification or follow up on sidebars afterwards.  Teams that do not adhere to this rule soon devolve into Product owners acting as Team managers, with negative effects on self-organisation within the team.

Checkpoint: After the updates the Development Team members visually confirm to each other their continuing commitment to the sprint goal. We recommend Roman Voting (Thumbs up, sideways, down)



 The Three Questions | One person speaks at a time, answering all the three questions, and then passing speaking rights to the next person
 Team Collaboration | The development team reports to each other, not to a scrum master, product owner or manager
 Risks and Issues  | Risks and Issues that cannot be immediately addressed are sidebarred for later resolution
 Recommit to Sprint Goal  |  Development Team have individually signalled continuing commitment to sprint goal