• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!


The Daily Scrum is For the ScrumMaster

Page history last edited by PBworks 16 years, 1 month ago

The Daily Scrum is for the ScrumMaster



The Daily Scrum feels like it is a status update from the team members to the ScrumMaster. 





Sometimes the daily Scrum begins to feel as though it exist solely for the ScrumMaster. You’ll see the ScrumMaster furiously scrawling notes about who committed to what work and why some other task wasn’t completed. Daily meetings like this take on the feeling of the status meetings of other development processes.
There are two main purposes of the daily Scrum and neither is to provide status information to the ScrumMaster. The first purpose of the daily Scrum is to provide a coordination mechanism for everyone on the project. Once a day it can be very useful for everyone to hear where everyone else is. Ideally there are many hallway or random conversations throughout the day but those don’t usually include the full team. During the daily Scrum everyone gets a sense of where everyone else is.
The second purpose of the daily Scrum is for each team member to make commitments in front of his or her peers. When a developer answers the “What are you going to do today?” question she is making a commitment to her peers, not to the ScrumMaster. At the next meeting if that commitment has not been fulfilled it is not the ScrumMaster’s role to say, “Tsk, tsk, Lucy, yesterday you told us you’d be done.” If Lucy said she’d be done and isn’t she probably feels bad enough. She knows what she told her peers and she knows if she didn’t finish because of random bad luck, a lack of effort, misunderstanding the size of complexity of the task, or any of a myriad other reasons.




Credit: this is based on material from Toward A Catalog Of Scrum Smells by Mike Cohn.

Comments (0)

You don't have permission to comment on this page.