Pod Insights The Agile Daily Standup - AgileDad Sprint Goals DONT Work - Or Do They? About this episode Sprint Goals DON'T Work - Or Do They?
Sprint Goals sound beautifully simple.
Set a goal for the team, organize the work around it, track progress daily, and finish with success.
Sounds easy enough. And that’s exactly why it’s so hard.
Behind this deceptively simple concept hides one of the most difficult ideas in Agile. As the Scrum Guide says:
“Scrum is lightweight, simple to understand, difficult to master.”
Sprint Goals are the perfect example of that. Even when you think you’re doing them right, you’re probably not.
On the surface, Sprint Goals add a lot of value. And therefore, make a lot of sense. But do you really need them?
What if I told you, there is a better way?
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:15 Speaker 00 Someone recently tried to point out to me that sprinkles don't work. Well, I don't know if that's true. I mean, on the surface, sprinkles sound beautifully simple. It's an easy thing. Set a goal for the team, organize the work around it, track progress daily, and finish with success. Sounds easy enough, and that's exactly why it's so difficult. Behind this deceptively simple concept hides one of the most difficult ideas in Agile. The Scrum Guide says it this way. It says, "Scrum is lightweight, simple to understand, difficult to master." Sprinkles are a perfect example of that. Even when you think you're doing them right, you might not be.
0:58 Speaker 00 What if I told you that there could be a better way? When you're launching a new product, sprinkles feel natural. The product vision breaks down into features, and each feature becomes a clear target. That makes sense. That resonates in our minds. So, for example, deliver account summary notifications for these three user scenarios. So far, so good. Everything seems great. The team decomposes the goal into a number of backlog items, organize the work, and starts building a product. But then, reality hits. Bugs, support cases, production issues appear, all stealing precious time from the planned goal. The result? A partially completed goal that rolls into the next sprint. Kicking off the new sprint, the team adds the new goal to the old one, and suddenly,
1:42 Speaker 00 you've created a composite goal, a laundry list of everything the team hopes to finish Sunday. Before long, the sprinkle loses all its meaning, and they become glorified list of backlog items, or they disappear altogether in favor of chasing the velocity number, right? Because we all know the focus on output is so strong. All of a sudden, the clear focus and alignment to a common purpose is long gone, just like that. And often the teams don't even realize they drift away from the common purpose. Let's flip the scenario. What if the team does hit the sprint goal? But does so early, now what do they do? Do you start fixing bugs and paying down technical debt? Do you expand the goal to take on new work? And to sprint early and start a new one with a new goal?
2:27 Speaker 00 While there's no clear answer, there is some clear guidance that I can give you. Anytime a team finishes early, they should get a head start. On an item and an next sprint, what that means is they're not saying, oh, well, we'll go pull something in because that's deceptive. That's not cool. Because the team never committed to that original item and it leaves leadership with the impression if they don't finish it, that they're not finishing the work they committed to, when in actuality, that was not one of the original items that they did commit to. So the better set is let's go get a head start on a first item and an next sprint. And in doing so, we can, if we finish it, we can pull it in and take credit for it. If we don't finish it, it's no harm, no foul, because it was never part of our original sprint. And when product managers think only in terms of features and not goals,
3:12 Speaker 00 this problem magnifies, it becomes worse. Bugs and tech debt rarely ever have a home in any kind of feature-driven prioritization. That's why we do tech debt sprints. So teams either force them in and make a fake goal, or ignore them entirely and say, come back to buy them later, which is another reason why you make a tech debt sprint. We can talk about that separately. Now imagine your product grows, three teams, each with its own sprint goal. What happens when they depend on each other? Team A needs an API update from team B to complete its goal, but team B is busy chasing its goal. Who stops and who waits for who and who fails? You might say, we have feature teams that own their own vertical slices. Great, but who owns the quality across all the slices?
3:55 Speaker 00 If one team changes another piece, another person, another team's code, will they catch every regression? Probably not. Dependencies will still surface, just in less obvious ways.
4:08 Speaker 00 This is where your concept of the scrum of scrum should come in and save the day. And the coordination meeting of team leads or one individual from each scrum team. It helps, but it's also fragile. On a human element, we don't function that way. Constant communication and manual synchronization just aren't our thing. And when every team is chasing its own north star proverbially, collaboration turns into a competition for people. Too many goals equals too many missed targets equals too many opportunities. So sprinkles aren't just hard to get right. They work only in very specific conditions.
4:48 Speaker 00 Small, independent teams, working on new, isolated functionality with minimal dependencies, distractions from an outside world. Outside that context, they collapse under their own simplicity. Scrum has its limits, and if you question why, despite all best efforts, things still turn into, well, a crap show. And here's the answer, here's your answer to that. If you stop hiding behind a very easy and forever acceptable excuse that you're doing it wrong, and give some independent thought to what we observe, well, maybe, just, just maybe, we'll begin to realize why pure idealistic concepts like sprint goals and pure scrum still miss the mark.
5:31 Speaker 00 After all, do we even want to succeed? I mean, we try, we make things work, we follow advice over and over, but at some point, we have to stop perfecting the technique and start looking at our results. Instead of isolated sprinkles, create a list of centralized product goals. Product goals tend to give you better and more clear direction, and from what I've learned, and it's easier for you to grab on to, and it usually makes more sense. A product goal gives direction to everyone. One direction, one north star, everything's aligned, we're good to go. If something more urgent comes up, like a critical support issue, the priority naturally determines when it gets addressed. No need to rewrite the goal. The goal stays put.
6:13 Speaker 00 But naturally, it becomes delayed by making way for something that's much more critical. So you have to align how you're going to have inflow management of ticketing, of objections, of things that need to be fixed. There are going to be these things, and I'm not saying, no, I'll go away. They will happen. You just need to know how to deal with them. This also means if Team A is working on a highest priority item for the goal, Team B should do everything in their power to help do their part instead of attempting to reach their own independent goal before they lift their head to help. Imagine Team B, a quarterback responsible for throwing the perfect pass, and Team A running for a touchdown. Team B must throw the ball perfect, perfectly timed, and must be a complete pass no matter what. This comes with a new profound realization.
6:58 Speaker 00 Dependencies exist only in places where every team is siloed and serves itself above everything else. A well-written product goal also shifts focus from feature delivery to outcome delivery, from build this integration to increase user signups by 10%. That subtle change drives better collaboration and better decisions. Teams understand the why behind the what, not just the what and how we're going to do it, get it done. And because protocols are bound by arbitrary time box, or I'm sorry, because protocols are not bound by arbitrary time boxes. Quality no longer suffers for the sake of a deadline. You finish when the goal finishes, and it's supporting offense, and you're wholly truly done.
7:42 Speaker 00 It just makes sense. Sprinkles were meant to help teams focus. But practice shows they often help fragment teams and break them down. They don't scale across teams, they break under dependencies, and they lose meaning in the moment exceptions appear. Which in a real world could mean every single sprint. So instead of chasing these magic unicorns, give teams a single clear product goal to rally around. Uh, one direction, if you will, one purpose, one alignment, a foundation for strong continual flow, shared focus and progress that actually matters. That's better agile and that's the way that we're all going to become better human beings. That's going to do it. I hope you enjoyed this episode. If you have a topic you want us to discuss, learn more at agiledad.com. We'd love to hear from you.
8:25 Speaker 00 And as always, we encourage you to stay healthy, stay well and stay agile, my friends. Until next time, do take care.
Previous The Moment Everything Changed - A Shoutout To Humanity Next Agile Anti-Patterns That Are Impacting Your Velocity Page updated November 6, 2026 · transcript and summary are machine-generated