September 15, 2023
I recently wrote about how to improve your Daily Scrum meeting. Now I think that we should just cancel the Daily Scrum altogether.
To be fair, some people are using the daily Scrum meeting effectively. Team members start the meeting themselves and use the time to collaborate and replan their work to achieve their sprint goal.
More commonly, I find that people are abusing the Daily Scrum and for them, I recommend that they stop the Daily Scrum meeting.
One of my agile coaching colleagues, Tom Cagley, shared with me similar experiences and frustrations. It was our discussion that inspired me to write this post.
The most common abuses of the Daily Scrum include:
Fake Scrum Teams – Sometimes the daily Scrum is made irrelevant because there is no need to communicate during the sprint. Some so-called ‘teams’ are actually just a collection of people doing individual work. They go through the motions of sprint planning but they just each plan their own work and pre-assign work to themselves. There is no shared sprint goal – each person has a story or two and that is their focus for the sprint. If this is the case, why bother with a Daily Scrum? Pre-assigning work obviates the need for collaboration and teamwork. Stop doing the daily scrum meeting!
Most of the issues above have nothing to do with the daily Scrum and everything to do with a lack of understanding of how to use Scrum.
Here is what the Scrum Guide says about the Daily Scrum:
The Daily Scrum is a 15-minute time-boxed event for the Development Team.
Every day, the Development Team should understand how it intends to work together as a self-organizing team to accomplish the Spring Goal and create the anticipated increment at the end of the Sprint.
The structure of the meeting is set by the Development Team and can be conducted in different ways if it focuses on progress toward the Sprint Goal.
Daily Scrums improve communications, eliminate other meetings, identify impediments to development for removal, highlight and promote quick decision-making, and improve the Development Team’s level of knowledge. This is a key inspect and adapt meeting.
Note: The quotes above were actually taken from The Scrum Guide Reordered, a topic-centric rewrite of the Scrum Guide by Stefan Wolpers. Wolpers created the reordered guide to help him prepare for the PSM III certification. You can download your copy by registering for the Age of Product newsletter.
Here is a shortlist of the savings you can expect when you stop wasting time in the Daily Scrum.
Team member time = $50-$100K per year
The biggest cost savings will be time spent by your Dev Team members in the Daily Scrum. Depending on how long you currently spend (waste) each day on the daily Scrum, you can save at least 75 minutes a week (5X15) per person, or even more. An average team of 7 developers will save about $1,000 a week at a minimum which is $50K a year. Those who are doing 30-minute daily scrum meetings can save $100K which is probably enough to pay for another full-time equivalent. In other words, rather than meet daily, use the money to hire one more developer per team.
Other’s People’s Time = $5,000 per person per year
If others attend your daily scrum meetings, that will save their time as well. This could be the Scrum Master, Product Owner, Project Manager, Dept. Manager, and any other interested parties. For the well-run Daily Scrums (those kept to 15 minutes), that is a savings of 75 minutes per week or 60 hours a year. That is likely to be at least a savings of $5,000 per person or more.
Scrum Master / PM Admin Time = $5,000 per year
If you have a Scrum Master acting as the team administrator they will save the time to attend and then capture the notes and email them out. In addition, team members don’t have to manually delete the email that they receive with the notes from the daily standup. And managers won’t receive, read and react (or overreact) to the notes from the daily scrum. Team members won’t waste time getting pulled into meetings with managers to clarify things or answer questions about things managers read in the notes that came out of the daily scrum.
Or if the Scrum Master is also the Jira Lackey, they can save the time that they are moving stories or subtasks in the tool. Though my guess is that your tool jockey will continue to do this activity anyway, even though they aren’t having a Daily Scrum.
Increased Morale and Engagement
Most developers dislike meetings, especially those where they are going to be talked down to or berated. Imagine how much better developers will feel if they aren’t told what to do or if they actually feel empowered to self-organize.
Are there other possible savings from eliminating a poorly run Daily Scrum?