Monthly Archives: December 2015

Avoiding Boredom During the Daily Scrum

All too often, a well-meaning Scrum Master voices the following concern:

“People are getting bored in the daily Scrum. We need to do something to keep them interested!”

Before trying to fix something, though, we need to understand its purpose. Let’s go back to the Scrum Guide for a quick definition of the daily Scrum:

“The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours.”

Synchronize activities and create a plan: that’s what the Development Team should be doing in the daily Scrum. When the plan is created, the Scrum is over — so how are people hanging around long enough to get bored?

Often, this arises from a misconception of what the daily Scrum is supposed to achieve. Team members are led to believe that this is a “report to management” meeting, where they have to rattle off a detailed account of what they’ve been doing so nobody looks bad. This is a sure sign that the team feels that they are being judged on some standard other than delivery of a good product.

Remember what matters. Make the Scrum about the Development Team; it’s not about pleasing the stakeholders, the Product Owner, bosses, or even the Scrum Master. The daily Scrum exists for the sole purpose of creating a plan for the day — and each day’s plan should move the team toward the Sprint Goal.