Daily standup meetings are a popular agile ceremony, especially for engineering and development teams. This daily habit helps align a team and share progress, stay accountable, and resolve potential problems quickly.
The purpose of this post is to share everything you need to know about this cadence. If you are new to this meeting or want to improve an existing standup routine, you've found the right place.
In this guide we will cover the following:
The origin story of the daily standup meeting (also known as a daily scrum) is described by Jeff Sutherland in this post. Specifically, they started investigating how the high-performing engineering organizations did their work and stumbled across this paper.
In this study, a team of eight engineers wrote one million lines of cover over thirty-one months (each person wrote 1k lines of code every week). One of their success factors was a daily meeting where they'd sync up on the project.
Here's specifically what the paper said:
"The core architecture team met daily to hammer out C++ class interfaces, to discuss overall algorithms and approaches, and to develop the basic underlying mechanisms on which the system would be built. These daily meetings were several hours in duration; from what I heard, the project was made more of meetings than anything else. Everyone's external interfaces were globally visible, and were globally discussed. The product structure was built on the domain expertise brought to the table by domain experts, but it was socialized and tempered by the needs of the product as a whole"
As Jeff writes in his post, they adapted this idea, reduced the meeting time and formalized this as a key operating process that happens every day.
If you think about the average work day, there's two major modes of work, especially for engineering teams:
Engineering teams require more coordination than other functions like marketing or sales. A sales rep could operate autonomously most of the time. If you have eight engineers working on a single codebase, the probability that people will step on each other's toes is high.
To use a sports analogy, engineering is a bit more like football, while other departments are more like running a race by yourself. These meeting are less about status reporting to external stakeholders, and more about internal coordination.
Technically, a daily scrum meeting is meant only for the development team, led by the Scrum master, and follows exactly with Scrum methodology, such as a 15 minute time boxing. It also outlines the tasks for the day.
Daily standup meetings are more informal, and includes more stakeholders such as the product owner. The development team may also be involved, or only a team leader, Scrum master, or a senior engineering manager. This meeting also identifies more blockers and resource allocation compared to the daily scrum meeting.
Many teams use the meetings interchangeably.
The point of the daily standup meeting is to aid team coordination. This fast feedback loop helps teams align and stay on track, which is similar to a huddle in football. If an issue pops up, you can address it quickly and keep projects on track.
Without a quick feedback loop, one person may be stepping on another's toes. It's possible they may be working on the wrong task. It's possible they may need help on a problem.
The daily standup makes the assumption that these potential problems are normal and seeks a way to address them from a procedural (or structural level).
In his post, Sutherland addressed three key points that every standup meeting should include:
1. The meeting must be held every day at the same time, and everyone on the team must be present.
2. The daily standup meeting can't last more than 15 minutes.
3. Everyone must participate in the meeting and actively listen
In the daily standup meeting, the goal is to answer the three questions shown below:
Let's break them down.
The purpose of this question is to relay information and share recent accomplishments. This helps give teams a sense of progress. To use the sports analogy, the answer to this question helps give you awareness of where others are on the field.
The point of this question is to show where you are going today. This serves two purposes:
If you aren't thoughtful with discussion around this question, a daily standup can turn into a status update meeting, which is an epic waste of time.
This might be the most important question and also the most difficult to surface. This question is important because you don't want people on your team to sit around waiting for someone else.
The goal is for each person to move in their own "swim lane", with as few impediments as possible.
The issue with this question is that people can hesitate to share that someone else is blocking them. It doesn't really look that great to be that person who's blocking someone else.
If you are a team leader, facilitating a daily standup meeting isn't rocket science. Here's some tips and best practices below:
The short answer is yes, it's possible to have a daily stand up meeting with a remote team. We'll analyze the two different ways below.
I've worked remotely for several years and participated and lead hundreds of real-time daily standups. If you are part of a remote team standup, I'd recommend focusing on the following additional variables:
Do everything you can to avoid letting the meeting drag on. It's very easy for someone to want to unpack what someone just said in the middle of the daily standup. Most of the time, this discussion should happen outside of the meeting, as most of the time it's only relevant to a few of the individuals and not the broader group.
For example, if two engineers are working on a billing system, while the other three engineers are working on another project, spending time to talk about the billing system may not be relevant to the three engineers who aren't involved.
Additionally, don't be late. If you are five minutes late for a meeting and there are four team members that are waiting for you, that's twenty minutes of collective time that's wasted (4 people x 5 minutes each).
Many remote teams will share this information asynchronously instead of holding a real-time meeting. This is primarily a result of having various team members in different locations. When you are remote, the cost of coordination tends to be higher. Additionally, many remote teams try to create a flexible work environment, which means reducing the number of meetings people have on a regular basis.
At Friday, we are huge fans of async daily standups that either replace or complement the meeting and make it more efficient. You can setup a cadence with our product in a few minutes for free.
The reasoning is simple. If you get the information-sharing done before the meeting starts, you can focus more time on resolving blockers and spend more time building relationships.
Let's wrap up this guide by discussing how you can optimize the efficiency of these meetings in the next section.
Here are a few final tips to make the most of these meetings, especially if you run them asynchronously:
The final point is to consider external stakeholders. If you have a report available, you can easily share progress without dragging external stakeholders into meetings (which no one likes).
To wrap things up, daily standups are a wonderful way to stay on the same page, but make sure to keep them efficient! A simple fifteen meeting every day can cost thousands of dollars in time cost.