DZone
Agile Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > Agile Zone > The 2 Things You Need to Do in Daily Scrums to End Complaints

The 2 Things You Need to Do in Daily Scrums to End Complaints

Are your Daily Scrums running too long? Well, that's an easy fix. Read on to get the advice of Scrum Master who has dealt with this same issue.

Mike Cohn user avatar by
Mike Cohn
·
Jun. 27, 17 · Agile Zone · Opinion
Like (4)
Save
Tweet
2.96K Views

Join the DZone community and get the full member experience.

Join For Free

You have undoubtedly had team members complain at some point about the length of your Daily Scrums. Join the club.

I want to share two extremely simple things you can do to put an end to most of those complaints (I can’t promise they'll get rid of all complaints—some people will always complain).

Since the Scrum guideline says that a Daily Scrum is not to be used for problem-solving, many Scrum Masters will note the problem during the Daily Scrum and then discuss it immediately afterward.

For example, if two hot issues are mentioned during the Daily Scrum, the Scrum Master might stop discussion of those topics. The Scrum Master will then bring the two topics back up after everyone has first had a chance to address the three questions of the Daily Scrum.

This leads to the team being there for longer than the standard timebox of 15 minutes for a Daily Scrum.

The first thing you should do is to end every Daily Scrum by announcing how long the meeting took. Do this right after everyone has addressed the three questions and before switching into problem-solving mode.

You might, for example, announce, “Thanks, everyone. That took twelve minutes.”

But then, remind everyone of any problems or issues that were brought up. Suggest that those who are needed stay to discuss or resolve them. If possible, facilitate the team splitting into more than one subgroup if more than one issue needs to be discussed.

Then, do the second thing that helps end complaints about the length of the Daily Scrum: announce that those who are not needed to resolve any of the issues being discussed can leave.

By taking these two actions:

1. Calling the Daily Scrum officially over and announcing how many minutes it took.

2. Telling team members who are not needed for further discussions that they can leave.

You will help team members from feeling that the Daily Scrum is exceeding its 15-minute timebox.

What Do You Think?

What have you done to eliminate complaints about the Daily Scrum? How have you helped your team see the value of this meeting? Please share your thoughts in the comments below.

scrum

Published at DZone with permission of Mike Cohn. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Password Authentication: How to Correctly Do It
  • How to Generate Fake Test Data
  • Don't Underestimate Documentation
  • DZone's Article Submission Guidelines

Comments

Agile Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo