Many of the pieces of Scrum are deceptively simple. In their simplicity, where many feel they have a clear understanding, the fact is that they really don’t. As Ken Schwaber has a habit of saying, “Scrum is simple, but really hard.” The daily scrum is a perfect example of this. Of all the events I have witnesses over the years, it is the Daily Scrum that is more often not just done wrong, but done completely wrong (in fact, here are some more tips about the Daily Scrum).

​The Daily Scrum is about communication (not status reporting for the ScrumMaster, as many teams believe). As a result of studies done many years ago that show that project success has as much, if not more, to do with communication amongst project team members as anything else (including team size).

The Daily Scrum is also about accountability. Did everyone do what they said they were going to do? If not, why not and what do we need to do as a team to get back on track? Daily Scrums keep the team accountable to one another and go along way toward eliminating unwanted surprises during the Sprint.

One of the best ways to make a Daily Scrum ineffective is to allow the event to be interrupted by conversations that are outside the scope of the questions being answered. For example, while answering the question, “What have I done since the last Daily Scrum to help my team achieve the Sprint Goal?” it would NOT be considered appropriate to begin discussing the all work that you did to diagnose and fix a problem. The reason this is true is because we’re asking our developers to listen to one another and try to create, in their minds, a view of what everyone is doing and if what they hear might indicate a problem. Too much detail, and we quickly lose track of what everyone on the team is trying to communicate. Also, because our team is cross-functional, discussing a particular issue in depth is probably going to leave a few developers standing there wasting time.

While the Daily Scrum is a great time to raise issues, it is a lousy time to discuss them. Many ScrumMasters have what they call the “sixteenth-minute,” a reference to the maximum 15-minute time box of a Daily Scrum. During the 16th minute, which can last fifteen or more as needed, the team discusses any issues raised during the Daily Scrum and decides what steps to take next.

FEATURED RESOURCE:

FEATURED RESOURCE:

Successful Event Planning Guide

Download Now!

Swipe this FREE DOWNLOAD to supercharge your work sessions.

Normally available ONLY to Artisan students, we’re offering this handy guide to you for a limited time!

More About #Productivity

Gearing a Team for Maximum Outcomes

Creating a maximum outcome team is every ScrumMaster’s goal, but you must first understand how great teams form and what YOU need to do to create a great team.

Simplify Your Work by Slicing

When slicing a backlog item, we're taking a complex problem and paring it down into smaller problems, which are easier to solve and build.

5 Ways to DOUBLE Team Performance

Here's 5 steps you can take as a manager or ScrumMaster to help DOUBLE your Development Team's performance (#5 is a shocker; it's easy but SUPER non-intuitive!)