Pod Insights The Agile Daily Standup - AgileDad Why Is Your Team Skipping Daily Standups? About this episode Why Is Your Team Skipping Daily Standups? Standups have become a way of life — not only for software teams but everyone else — they are the checkpoint on the day as to how we are doing, what’s working and what we need to do. If ever there was a meeting to attend, to get the pulse of what is happening in your team, it would be this meeting, and yet people skip them when other meetings conflict, or they have appointments during that time, or they simply opt out of them because they are too busy. Perhaps the reason you are busy is because you have too much on your plate and you need help clearing it off. How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/
Transcript 0:16 Speaker 00 So in Agile, stand-up meetings have become a way of life. Whether you call it a daily scrum or a daily stand-up, I always tell people a daily scrum is a meeting, a daily stand-up is a podcast. Anyway, so now that we know that we do this, it's becoming more prevalent in interesting places. Let me explain what I mean by that. So just a couple of weeks ago, I mentioned that I was at Walmart and I saw a group of people at the front of the store and they were having, they were all in a circle and they were having a stand-up meeting. I saw the same thing at a local Kroger affiliate and again at Lowe's. So what I'm starting to recognize is that this whole intent of a daily scrum or a daily stand-up isn't just for software teams.
0:58 Speaker 00 It tends to start leaning in and being for everybody else. This is their checkpoint, so to speak, just to see how things are going, what's working, is there anything else we need to do? So what I'm sensing and what I'm seeing is that this is quickly becoming an accountability meeting, which is what it should have been all along, but that it's becoming easier for non-technical teams to do these. And I can tell you, Ken was very passionate about this when I took my training from him way back in the day. He even went as far as to say, if there's ever one single meeting you need to attend, make it the daily scrum. It gives you the pulse of what's happening within the team, it gives you the pulse of what's happening within the organization, and it's delivered in a very quick, rapid-fire format.
1:42 Speaker 00 So, people, for whatever reason, despise this meeting. And I guess that's what I'm trying to get to the bottom of. Why do people always want to skip this when anything else conflicts? Or if they have an appointment during that time? Or if they opt out because they're just too busy? It's incredible to me to think that the meeting that's supposed to be pulling us all together is the one that they're most likely to skip. So, I think part of it is just that the meetings have become so... I don't want to say it, they've just become so monotonous. We want to have exciting meetings. We want to get something out of it. We want to feel like we're doing it
2:22 Speaker 00 to achieve a goal. If not, then we might as well skip it. I mean, everyone who attends to stand up should be getting something out of it. If not, then they're just sitting there idle, asking why are they even there?
2:36 Speaker 00 For some groups, that means maybe you need more structure. For some groups, maybe less. For some groups, maybe the issues being discussed really don't matter because they're not relevant to everyone else and they need to be resolved separately. Or other times, maybe it's because we're not resolving the issues in the meeting. So, the question becomes, is this where we start today? Is this where our purpose is set and achieved?
3:01 Speaker 00 If you don't know the purpose or the value of why you're doing this, how do you expect others to understand why they're being asked to do it? And how do you help them reconcile spending that amount of time doing this meeting? That's a good question. If you want to get people to understand the importance of the daily scrum, you need to put it out there in a universe that if they have conflicting meetings, this one always wins. It's not a discussion. It's not an option. The reason many of us don't do that is because we have to show why then this meeting, the daily scrum, is more important than XYZ meeting. And you want your team to reach back to the other person and say, hey, I can't. That's right at the time of my standup and I explicitly need to be there. Can we meet before or after?
3:44 Speaker 00 When one person starts making this sound really important, and they all will, and when they all start saying it, the rest of the years of the company will pick up on it. That the meeting is respected, that the meeting is golden, that the meeting is a boundary, that the meeting is something that they all need to be a part of. So if we can get it to the level where people respect the fact that we're having a meeting and they understand why, then we need to ask ourselves, when we do this meeting, okay, now that we've got everyone to understand it's important when we do the meeting, are people actually engaged? Are they keying in on what others are saying? Do they care? Are they just there for the free donuts? I mean, I don't know.
4:28 Speaker 00 I'm just throwing it out there. If you have a really large roster of people, the problem might be that you have groups that don't necessarily intertwine or understand what the other group's doing and spending 15 minutes listening to people talk about work that doesn't affect them. That's a hard way to start your day, right? If what you're doing is talking about, if what you're doing or talking about is completely irrelevant to everyone else, you need to ask yourself, why am I in this meeting? What benefit am I providing for others? Or what benefit am I receiving from being in this meeting? And I think that's the key right there. Am I receiving benefit? Or am I providing benefit to others? As the leader of the meeting, and I don't want to call it a leader, I guess a leader's
5:11 Speaker 00 a bad word, as the person who is rallying the troops for this meeting, there we go, it is your role to ensure, whether you're an agile coach or a Scrum Master, that the team knows the value of their input and their contributions and what's being worked on and making tough decisions to break it up if needs be. It isn't a bad thing. This is a very smart thing in a way, because the end result might be that you don't have a giant 30-minute stand-up or whatever, but you end up with two or three more effective eight-minute stand-ups, where people care about what each other is saying and you've broken it down in such a way that everyone's got something consumable. So you need to make sure that you understand exactly what's going on and whether it makes sense to split it up into smaller pieces.
5:54 Speaker 00 And I know what you're thinking, oh my goodness, that means more meetings. Actually, it winds up being less meetings over time, because not everyone has to be in all of those meetings. In fact, that's the whole purpose or intent behind a meeting called the Scrum of Scrums, where you get one representative from each of those meetings to meet later, to make sure everyone's on the same page only if and when necessary. So there is a way to get that cross collaboration piece in there. So if you...
6:22 Speaker 00 Are having this meeting and you feel like it's not being effective. You need to figure out what you need to change. You need to figure out how you need to change things up. I mean, let me give you a different example. When you're driving and it starts to snow. You find yourself staying in the ruts of the driver in front of you. The other lane beside you looks pretty attractive. But you're gonna have to pull out of that rut and it can be an uncomfortable space for a bit before you're in the next lane in that rut. The truth is.
6:50 Speaker 00 People look at the stand up meeting as a rut. Uh, you run them daily at the same time. You see the same people, same way at the same time every day. And then you may need to change things up. You may need to switch lanes. You might need to change things up just a little bit, just enough to disrupt it. To make it something worth, worth it. Uh, some teams I've seen do something silly like ask. Uh, like a question of the day. Or rotate someone different to start the meeting within each group. And have them tell something interesting about themselves or whatever you do. Just don't do the same thing day after day, week after week, month after month, year after year. No one wants to watch the same episode of Friends over and over again. So why would you force people to do it in a stand up?
7:34 Speaker 00 If your stand up is in the morning, be mindful that this is people starting their day. Give them a reason to start off on the right foot. Give them a reason to be there. I mean, we all know that running a daily scrum just, it's not easy. It's tough. It's a recurring task. And I can tell you, I've done this for years at a time with teams, years. And there are days that I've even felt like, oh, I just don't, I don't have it in me today. I just want to cancel. I just want to get rid of it. But I didn't. Because if you think back to the purpose of the stand up. It's to get everyone started. On what they're doing to start fresh. It's to identify what we don't know and what we do know. And to help find a path forward together. Put that way, no one should ever skip the stand up.
8:19 Speaker 00 If it's able to provide value, but over time. We need to remind people that the value still exists by keeping people engaged and wanting to be there. So if we can make the stand up meeting, something that provides value, something that has a clear purpose. And something that happens quickly. So people can return back to doing the work that they need to do.
8:40 Speaker 00 Keep the group small, keep the group focused, get in, get out. And the most important thing that I didn't discuss is make sure you remember that this isn't an interview. This isn't an opportunity for the Scrum Master to come in with their glitter microphone and their dazzled jacket. Hey, it's time for the stand up. Let's ask Johnny, Johnny, what did you work on yesterday? And what are you working on today? Do you have any impediments? Our next guest is Margaret. You know, my goodness, that's, that's the last meeting people want to be in. What needs to happen in this meeting is the team needs to take control. It needs to be a let's get started and someone in a meeting says, I'll start. And that's how the meeting begins. So no one's going to interview you and ask you the questions. You need to be prepared to present materials that are relevant about what's going on today,
9:26 Speaker 00 about what things you need to do to stay on track. And maybe, maybe it's yesterday I committed to do these things, but I didn't get to do it. And here's why, or maybe it's yesterday I committed to these things and I got them done. Today, this is what I committed to do. Those are the types of things that you want to focus on so that everyone can be on track, on task, and understand what's happening around them so that they can work most effectively with you. And most importantly, so that you can be effective and understand that this is helping everyone make progress. So that's going to do it. I hope that you enjoyed this episode. If you also have a topic you want us to talk about, learn more at agiledad.com is where you want to go. We will be happy to talk about whatever topic you have. But until then, we ask you to stay healthy, stay well, and stay agile, my friends. Until next time, do take care. Bye now.
Previous The 1-Minute Introduction That Makes People Remember You Forever Next Are You Chasing ScrummerFalls? Page updated November 6, 2026 · transcript and summary are machine-generated