Pod Insights The Agile Daily Standup - AgileDad What Is Scope Churn? About this episode What Is Scope Churn?
Businesses naturally want predictability from their software organizations. Promises have been made to customers, and there are business objectives to deliver as well. Often, those things have little to no wiggle room. The head of Marketing says “This must be completed on time, because we have a trade show on March 1st, and we have committed to present there.” The head of Product says “The only way we could save this angry customer was to promise that this would be completed on September 30th. If we don’t deliver, they will walk.”
How to connect with AgileDad:
- [website] https://www.agiledad.com/ https://www.agiledad.com/
- [instagram] https://www.instagram.com/agile_coach/ https://www.instagram.com/agile_coach/
- [facebook] https://www.facebook.com/RealAgileDad/ https://www.facebook.com/RealAgileDad/
- [Linkedin] https://www.linkedin.com/in/leehenson/ https://www.linkedin.com/in/leehenson/
Transcript 0:17 Speaker 00 Businesses naturally want predictability from their organizations. Promises have been made to customers and there are business objectives to deliver as well. Often, those things have little or no wiggle room. The head of marketing says, "This must be completed on time because we have a trade show on March 1st, and we've committed to be present there." The head of product says, "The only way we could save this angry customer was to promise that we could have everything completed by September 30th, and if we don't deliver, they will walk." What business leaders can't wrap their minds around is that reality can't be changed simply by sheer will. There's no infinity goal, although I wish there was, with a reality stone embedded for one of its knuckles.
1:00 Speaker 00 "Oh my goodness, we need an infinity stone." A reality stone, that would be awesome. And there's no shared crystal ball sitting on a pedestal somewhere owned by the engineering department or by whatever department it is. They can spend four weeks defining and estimating the full scope of the project, but there will always be some surprise that no one could have ever foreseen. It just happens. Business leaders naturally want to blame the people who are building the product, but they could just as easily blame themselves for not recognizing the risk and how risky it is to predict the future. In addition, these same business leaders often contribute to circumstances that almost guarantee that the date they're so concerned about will be missed. Every time someone screams and leadership forces everyone to drop what they're doing
1:44 Speaker 00 and pivot to whatever that person is screaming about, they are, without knowing it, asking for the schedule to slip. When priorities are constantly shifting, like tectonic plates in Ring of Fire, it's impossible to accurately predict delivery dates, and no amount of heroics are ever going to resolve that. When this happens, we call it "scope churn," because the sprint scope, which should be stable, is churning and shifting underneath the team. Teams and leaders are often oblivious to the impact of scope churn. The consensus can be that that's just the way things are. But things are that way because decision makers don't really prioritize team stability above other things. If you want to deliver in a predictable way, you must work to lower scope
2:29 Speaker 00 churn. When priorities shift, one of two things will happen. Something will be removed from the sprint to compensate that hasn't been started on, and then we can add the next most important item as the first item in the next sprint. And if the team has been within the end of the sprint and says, we completed all of our committed items, they can get a head start on the first item in the next sprint. Notice I didn't say pull it into this sprint because that's the right answer. They get a head start, that's the best way to do it. Nothing should be moved into the sprint. Nothing should be adjusted and you can't just move it in and push something out and split the points and oh my goodness, I've heard all these stories before. When you add new things
3:07 Speaker 00 to a team's bucket, something they planned is simply not going to be finished, period. And it doesn't matter whether you add it into this sprint or for a side of an expert. You can either decide proactively what will be, or you can wait and be surprised when a sprint ends. It's happening the same way either way. The wisest thing we can do is protect the plan as much as possible and do our best to not interrupt the team. If we keep them focused on their primary goal, they're going to be able to get a lot more done. So it's one of these things where the higher scope term percentage, the greater the impact on the team's productivity. Scope turn is defined as an is is an interruption. It impacts their ability to focus. A lack of focus means lack of delivery
3:52 Speaker 00 and it all just falls out that way. The other way to look at scope terms by focusing on raw numbers and looking at scope added and scope removed independently. And you could do that by focusing on total story points and you can look at the you can look at issue counts. You need to decide what makes the most sense for your team about how to handle inbound issues and how to handle inbound workflow. If you look at it this way, the primary, there's a primary goal and secondary goal. The primary goal is to shrink added scope as much as possible. Since added scopes will creates the significant inefficiency on its own. The secondary goal is to make added or remove counts as close together as possible.
4:34 Speaker 00 So that when you add scope, even in an next sprint, you're removing something from a current sprint to compensate so that it has the best chance of balancing out. That's the easiest way to figure out how to get things done without making the whole team in an uproar. Anytime you decide that you're going to add scope and you end up adding more scope than you actually remove, you're causing the team's total scope to increase over the course of two or three sprints. That means that you're asking work to be completed and putting a team in a position where they're very likely going to fail. This prevents them from becoming predictable and it's unfair to them and unfair to the business. You can't seem to get predictability you want by jiving your teams this way.
5:14 Speaker 00 If you can't seem to get focus, maybe it's time to start tracking scope turn and tracking cumulative flow to figure out where things are getting stuck. So that way you can treat the problem and not the symptom. Our ongoing theme this week has been treating symptoms and not treating problems. So I want to talk to you quickly and say that if you treat the problem in this case, which is limiting WIP and handling debt, then none of this is an issue, but the problem is most organizations don't take time to do that. So my advice to you is figure out a way to formulate exactly what the debt is, how the inbound flow works and adjust the amount of work you're taking on each sprint to make it marry together. So it makes sense. That's going to do it for this episode. I hope you enjoyed it.
5:57 Speaker 00 If you have a topic you want us to discuss, learn more at agiledad.com. We would love to hear from you and as always, we encourage you to stay healthy, stay well and stay agile. My friends, until next time, do take care.
Previous Agile Failed Us After 18 Months - Here we go... Next Why Soft Skills Outlast Technical Skills on Product Teams - Mike Cohn Page updated November 6, 2026 · transcript and summary are machine-generated