Pod Insights The Agile Daily Standup - AgileDad The Sprint That Never Delivered About this episode The Sprint That Never Delivered
Three sprints in a row. Less than half of what the team committed — delivered.
As a Scrum Master, that’s the kind of pattern that keeps you up at night. Not because of the numbers themselves, but because of what comes next: the questions from management, the looks in the retrospective, the slow erosion of the team’s belief in themselves.
This was Team A. And they were trying. That much was clear.
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 How many times have you been in that situation where someone says, "I've had it. Three sprints in a row, less than half of what the team committed was delivered." As a scrum master, that's the kind of pattern that keeps you up at night. Not because of the numbers themselves, but because of the conversation that comes next. The questions from management, the looks in the retrospective, the slow erosion of the team's belief in themselves. "This was Team A, and they were trying," that much was clear. The easy answer, and why it was wrong. My first instinct was the same as everyone else's. "The team is overcommitting. They're being too optimistic in planning, tightening estimates, problem solved." But when I sat down with them, and we actually went through the user story, something else
0:59 Speaker 00 emerged. The estimates weren't wrong because the team was careless. They were wrong because the moment anyone opened the code base and started working, the complexity multiplied threefold. What looked like a two-point story on the surface had roots that ran deep. Dependencies no one mapped, legacy code that no one documented. They weren't overcommitting, they were under-informed. I proposed we do one change. Spend more time in refinement, actually looking at the code, and not just what the description is of what was being requested. It sounded super obvious in retrospect. Most good solutions usually do. The team started pulling up the relevant code during their refinement sessions. Asking questions before the sprint, not during.
1:43 Speaker 00 Surfaceing the unknowns early, when there was still time to adjust. Within two sprints, the pattern broke. Commitments became more accurate, delivery followed. Scrums empirical process actually works, but only if you're inspecting the right things.
2:00 Speaker 00 We were inspecting story points. We should have been inspecting complexity. The retrospective is the only place for inspection. Well, no, it's not. The retrospective is never the only place for inspection. Sometimes inspection happens in our refinement meeting or daily scrum. You need to learn to slow down to speed up. Time spent understanding where before the sprint saves far more time than during it. Inspect what actually causes the variance. Velocity is a symptom. Look for the cause. The team already knew. They just needed space that was safe, to say it out loud. I think that when you start inspecting story points and you start inspecting number of stories completed, when you start focusing on output instead of outcome,
2:43 Speaker 00 that's when this whole Lego castle starts to fall apart. That's when the dominoes start to fall. When you start treating the retrospective as the only place where you can have a conversation, that's where things start to go south. When you start looking for excuses instead of looking at the problem, the root cause, that's when problems start to stem. I think part of it is we just need to understand how to focus better on outcome and stop focusing on output and start remembering that doing less is actually doing more. If you can find a way to solve this problem, it would be so much easier for everyone involved. Have you ever had to fix a recurring problem only to realize the original diagnosis is completely wrong? If you did, what did you actually find when you look closer?
3:29 Speaker 00 I think these are the questions we're trying to answer and these are the things that we're trying to solve. If we can get to the root cause of the problem, I guarantee you, your sprints could be better and your team could be happier. Short and sweet today, that's going to do it. If you have a topic you want us to discuss, learn more at agiledad.com. We'd 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. Bye now.
Previous Sprint After Sprint After Sprint… When Did This Stop Feeling Like Progress? Next Why Estimating and Planning Still Matter - Mike Cohn Page updated November 6, 2026 · transcript and summary are machine-generated