Pod Insights The Agile Daily Standup - AgileDad Work Spilling Over? How to Know if You’ve Got a Rollover Habit - Mike Cohn About this episode A key agile principle is the value of getting work done by the end of each iteration. Yet one of the biggest complaints I get from agile leaders is that teams never finish what they say they will during a sprint. Instead, teams consistently let the unfinished work spill over (AKA roll over or carry over) from sprint to sprint. Spillover is such a prevalent problem for agile teams that I want to devote several tips to talking about it. First, I’ll explain what spillover is and how to know if it’s a problem Next, I’ll describe why habitual spillover is so bad Third, I’ll give you some ideas for how to break your team’s rollover habit Finally, I’ll talk about what to do with unfinished work when spillover happens. After all, while spillover shouldn’t be a habit, every team will occasionally have unfinished work at the end of the sprint Team members were too optimistic and brought too much into the iteration The team was interrupted more often during the sprint than expected Some of the work took longer than expected Externally: A boss or important stakeholder can exert pressure by telling a team what must be done or by establishing unrealistic expectations. Internally: Some teams allow their optimism and high expectations of themselves to create pressure to do more than is reasonable. What Is Spillover? Why Does It Happen? Spillover is when a team arrives at the end of one sprint with some unfinished work that needs to be finished in a later sprint. It happens when a team overcommits to what they can achieve during the iteration timebox. This is usually because: Spillover is not a bad thing in and of itself. It’s unrealistic to expect a team to finish everything it starts, every sprint. In fact, it’s normal and desirable for a team to occasionally aim a little high for what they can accomplish in a sprint, and come up short. When Does Spillover Become a Problem? Habitual spillover, though, is different. Habitual spillover is when a team almost always commits to more than they can finish in the sprint. These teams rarely finish what they think they will. As a result, the end of the sprint becomes an arbitrary date, and work is just carried over into the next sprint as if it’s no big deal. It is a big deal. (I’ll talk more about why it is a big deal in next week’s tip). The most common reason teams develop a habit of taking on more work than they can finish is pressure. That pressure can originate: One Thing to Do This SprintOne thing you can do right away to help stop habitual spillover is to make the problem visible. At the next sprint end, make a note of how many items the team committed to versus how many were 100% done. Even better: look back and do this for a handful of prior sprints. Bring this information to the retrospective and ask the team why they think unfinished work has become a pattern for them. Then ask them for one thing they could try next sprint to prevent it from happening. Don’t forget to hold them accountable to trying that idea (whatever it is) during sprint planning and as the sprint progresses. While you’re doing that, I’ll be getting my next tip ready for you. Next week I’ll be writing about why spillover is such a bad habit to fall into and how breaking that habit can help you succeed with agile. 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 I recently received an email from my dear friend Mike Cohn. I love to read his emails. And this one has to do with work spilling over. It says, I don't know if you've got a rollover habit. Now, this is going to be interesting because, Mike, you know, I love you, but I think we may have a little bit of a difference of either opinion or a difference of definition here. I haven't quite decided which one it is. So I'm going to go through and read Mike's email and then as I progress, I'm going to stop, chime in, and then keep reading because I think that's the best way to handle this. So let's get started.
0:53 Speaker 00 He starts off, hey, Lee, a key agile principle is the value of getting work done by the end of each iteration. 100% agree fact, yet one of the biggest complaints I get from agile leaders is that teams never finish what they say they will do during a sprint. Instead, teams consistently let the unfinished work spill over, AKA rollover or carryover from one sprint to another. Okay, let's pause right there. I want to make sure we have clarity on a couple of definitions real quick.
1:25 Speaker 00 So let's go back to one of the biggest complaints I get from agile leaders is teams never finish what they say they will during a sprint. That is a fact, my friend, 100% fact. And part of it, though, I'm not going to blame the team. Let me explain. When you ask the team, what's one of the things they dislike the most about working in sprints or operating in that fashion? Is that work often gets swapped out or traded out? Or, oh, we said, we, you know, we said we would commit to do A, B, and C, and then we go back, look in our backlog, and they're asking us to do B, D, and E. But don't worry, because D and E are the same size as A and C. So swapping out was perfectly okay, right? The answer is no, that's not perfectly okay. So I think.
2:12 Speaker 00 The concept that I'm trying to say here is that there's a difference between splitting work to make sure it's right size, that it fits inside of a sprint and carryover. And I think that we're going to be on the same page for the most part, now that I read that line. But let's continue. Let's just see where this is going. Okay, so he continues. Spillover is such a prevalent problem for agile teams that I wanted to devote several tips to talking about it. First, we'll explain what's a spillover is and how enough to problem. Next, we'll describe why habitual spillover is so bad. And then third, I'll give you some ideas on how to break your team's rollover habits. Then finally, we'll talk about what
2:54 Speaker 00 to do with unfinished work when spillover happens. Okay, I'm good with that. But I will say this. In recent years, probably in the past three years, four years, I've never had a team, after I've worked with them for at least a couple of sprints, I've never had a team carry over work from one sprint to another. It's just, it's something my teams don't do. And I know you said early on that that can't be the expectation, but I'm going to argue it can be, and I have a way to do it. But let's see where you take it first. So, starting with what is spillover, why does it happen? Spillover is when a team arrives at the end of one sprint with some unfinished work that needs to be finished in the next sprint. It happens when a team overcommits to what they can achieve during
3:38 Speaker 00 the iteration time box. This is usually because team members are too optimistic and brought too much work into the iteration. The team is interrupted more often during a sprint than expected, or some of the work took longer than expected. I'm going to add another one. How about people ask the team to do different work during a sprint. Oh, don't worry about this, do this instead. Or how about this one? The team undercommits by a small amount, realizes they have some bandwidth left, and they go to the product and say, what should I do? And the product says, oh, pull one or two items in for the next sprint. Now you have work that you know you're not going to finish, that has been pulled over into your current sprint. And I see this happen all the time. So then what happens? The team says, oh, no big deal, it was work from the next sprint, so we'll
4:21 Speaker 00 just go ahead and split it. So they break it up into two stories, part of the work in the story I completed, for the remainder to work over here. And what does leadership look at? Every single sprint, they don't finish the things they committed to, because they look at that work that they pulled into the sprint as work that was committed to. So we need to make sure we have clarification about what we're talking about.
4:42 Speaker 00 It says spillover is not a bad thing in and of itself. It's unrealistic to expect the team to finish everything it starts every sprint. See, this is where we disagree. I do want the team to finish everything they start. Or everything to commit to, I guess you say, let's reword that. You might be right here. Okay, I'm gonna reread this because you're right. Spillover is not a bad thing in itself. It's unrealistic to expect the team to finish everything it starts every sprint. That is true. One of the things I encourage teams to do. Often to finish what they've committed to and I say, hey, what should I do next? I'm like, go get a head start on the first item and the next sprint. It doesn't mean it's now part of this sprint's commitment.
5:23 Speaker 00 But it means that now we can get a head start on something from the next sprint. That's pretty genius, right? Because then if they don't finish, no harm, no foul. They just got a head start on the first item and the next sprint. If they do finish outstanding, they can pull that item in as a done item. Log those story points and move on. So I think that that's, I think we're talking about the same thing here. At first I was a little concerned, but now I think we're good. In fact, it is normal and desirable for a team to occasionally aim a little high for what they can accomplish during a sprint. And they'll occasionally come up short. I get that. I often tell my teams, aim high and then back off one item. That way they have that little bit of a buffer. But it's not so much of a buffer that the team's underperforming. Parkinson's Law isn't kicking in.
6:08 Speaker 00 So spillover is not a bad thing in and of itself. We need to make sure that the teams can, uh, aim a little high for what they can accomplish. When does spillover become a problem is the question. Habitual spillover though is different. Habitual spillover is when a team almost always commits to more than what they can finish during a sprint. And they rarely finish whatever they think they will do. Let's pause there for a second. There's two symptoms here. First, I don't know that the team is always trying to commit to more than what they can do. I mean, I've seen that before. Yeah, let's do 50 things. But I would argue that's the rarity. I think the majority of the time. The team finishes the work they've committed to. They go to the product owner and Scrum Master and say, hey, what should I do next?
6:52 Speaker 00 The product owner says, why don't you just grab another item from the backlog from the top or pull an item in for the next sprint? So what winds up happening is they add additional work to the sprint, late in the sprint, that they know they can't finish. And that is the problem right there. As a result, the end of the sprint becomes an arbitrary date. Work is carried over from one sprint to the next like it's no big deal. And that's when leadership loses their mind. It is a big deal. It is a huge deal, right? And we're gonna talk more about that in a minute, apparently. But the most common reasons teams develop a habit of taking on more work than they can finish is pressure. Pressure can originate externally from a boss or important stakeholder that exerts pressure by telling a team what must be done,
7:38 Speaker 00 or establishing an unrealistic expectation. Or internally, some team members allow their optimism and high expectations on themselves to create pressure to do more than what's reasonable. Like I said, though, you know what? I put my flag in the ground here. I really believe this is symptomatic. And Mike, I'm begging you, I know you listen. Please call me out if I'm wrong. Please call me out if you have a different opinion. I'd love to hear your feedback. What I'm saying is, I think more times than not, work carries over because people are letting things come into the sprint late. They're not locking down what's in the sprint.
8:17 Speaker 00 And I know, oh, we welcome changes even late. Yeah, I get it, but welcome changes is one thing, changing items is another thing, right?
8:26 Speaker 00 One thing you can do right away to help stop habitual spillover is make the problem extremely visible. At the next sprint and make a note of how many items the team's committed to versus how many were 100% done. Even better, look back and do this for a handful of prior sprints. Bring this information into the retrospective and ask the team why they think unfinished work's become a pattern for them. Then ask them for one thing they could try next sprint to prevent it from happening. Don't forget to hold them accountable to trying that idea, whatever they come up with, during sprint planning and as the sprint progresses. So I think that's a great idea. I think that that's gonna help you. Discovered the root cause of what's really happening.
9:05 Speaker 00 Uh, while you're doing that, we will be preparing the next tip to help you do agile better. Um, and Mike promises next week, we'll be writing about why spillover such a bad habit to fall into, and how breaking that habit can help you succeed with agile.
9:22 Speaker 00 Mike, I love your emails. I love it to death. I hope that maybe that I, since I've, since I've given this review of this email, that you will, um, consider, just consider putting together one that talks about allowing inbound work into the sprint once the team has already committed, and the impact that has on the team's ability to perform. There's nothing more disheartening or discouraging to me, a team member and seeing new work being added that's out of your control. The product owner has agreed to because some C-level hippo, highest paid person's opinion, has said, hey, we need to change scope of what we're working on. And I'm not saying they shouldn't be able to do that. What I'm saying is that this becomes habitual and it starts happening over and over again.
10:05 Speaker 00 You break down team morale, teams are able to do less work. Uh, they get frustrated, leadership's frustrated, agile doesn't work. Let's do safe. I, I think you see the pattern here. Yes. So it's just, it's one of those patterns. So let's make sure we're identifying those patterns and kicking them in the butt. Because we don't want to wind up being on that, uh, on that hill. That's it. I hope you enjoyed this episode. If you have a talk you want us to discuss, learn more at agiledad.com. We'd love to hear from you. And thanks again, Mike, for that wonderful email. As always, we encourage you to stay healthy, stay well, and stay agile, my friends. Do take care.
Previous Why ‘Better’ Products Fail Next Hold Your Team Accountable Without Being a Helicopter Manager Page updated November 7, 2026 · transcript and summary are machine-generated