Pod Insights The Agile Daily Standup - AgileDad Sprint Planning or Sprint Guessing? About this episode Sprint Planning or Sprint Guessing?
Welcome to sprint planning — that magical 90-minute meeting (that always becomes 3 hours) where:
Developers turn into psychicsProduct managers become game show hostsProduct owners stare into a backlog like it’s a crystal ballSound familiar?
For many Agile teams, sprint planning isn’t the crisp, focused ritual described in books. It’s often more ambiguous, chaotic, and filled with guessing than anyone wants to admit.
So… are you really planning? Or just giving your best estimate in a business suit?
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 Welcome to sprint planning, the magical 90 minute meeting that always becomes three hours. In case you haven't figured it out, I've been kind of in a humorous mood lately, you know, kind of poking fun at some of the agile things. But you know, this meeting where developers turn into physics and, and you know, that doesn't make any sense. This, this is an article. So this article is titled, oh, that's why it doesn't make any sense. This article is titled sprint planning or sprint guessing. And it says developers turn into psychics. That's a lot better than physics. Product managers become game show hosts. Product owners stare into a backlog like it's a crystal ball.
0:57 Speaker 00 Does any of that sound familiar? I can tell you from my experience it does. I've seen this. For many agile teams, sprint planning isn't the crisp focus ritual described in the books. It's often a more ambiguous, chaotic and filled with guessing more than anyone would like to admit. So are you really planning or just giving your best estimate in a business suit? Well, let's unpack this with a little bit of humor and a lot of honesty. So what should sprint planning really be like? Well, in a perfect agile universe with unicorns, rainbows, and perfect burn down charts, sprint planning is a focused collaborative session where the team picks the most valuable work from the backlog.
1:39 Speaker 00 Stories are clear, well-defined and appropriately sized. Team members feel confident and aligned and have no questions. Everyone leaves knowing exactly what's coming and exactly what to expect. And sprint planning is supposed to be the bridge. It bridges the product vision and real deliverable work. It should answer questions like, what are we doing this sprint? Why does what we're doing matter? How we approach it and who's going to be impacted? But oftentimes instead you get agile charades in action. Let's be honest, here's what it often looks like. Wait, what's this story even about? Or can someone explain that acceptance criteria? It doesn't make any sense.
2:23 Speaker 00 Is this a three or an eight? Feels like a five, maybe. Let's just add in, if we finish early, we'll do it. Famous last words, right? By the end of the session, there's a vague plan, some cross fingers, and a silent hope that nobody gets a Slack DM at 2:00 AM.
2:41 Speaker 00 But there has to be some logic behind why sprint planning goes off the rails. Why does, and why does planning sessions always feel like chaos with a Jira tab open? Right? Why does it feel this way? Well, vague user stories. When you start saying things like, "Build a login page." That's cool, but for who? With what? Is there Xero, 2FA, a magic link? What are we trying to do, right? What about overloaded backlogs? Your backlog is 246 stories deep, most of which haven't been touched since Q3 of last year, and nobody knows whether or not it's even relevant anymore, or what we should be doing, and why. How about radio silence?
3:24 Speaker 00 If your team isn't asking questions, they're either confused, bored, or planning lunch. None of that equals clarity, but planning lunch sounds good right about now. I'm starting to get hungry. How about four? Planning point poker gone wild. Each developer has a different internal compass. For developer A, a 3 is a cakewalk. For developer B, 3 means 2 Red Bulls and a weekend out of my reach. Yeah, and that happens, because you're trying to tie back the time, but that's a whole nother conversation. And then coming in at five, no real definition of done. Does done mean coded, tested, reviewed, documented, deployed, delivered, released? No one knows, but everyone just shakes their head and says, "Sure." Absolutely, right? This is what I see.
4:09 Speaker 00 You know what we shouldn't be doing? I'll tell you what we shouldn't be doing. We shouldn't be writing user stories like vague tweets, ignoring bugs and technical debt, because they will come back to haunt you. Have a technical debt sprint and get them solved. We shouldn't assume silence equals understanding. When people are quiet, sometimes not because they understand, it's because they're bewildered or lost, or stop over committing with stretch goals. Figure out what you can do in a sprint, back an item out and become predictable. Go figure and leadership loves predictability. Why are we so afraid of it? Jeez. And stop estimating stories in a vacuum, right? Get the whole team together and figure it out. Sprint planning isn't just a performance. It's a prep for the real show, which the real show should be the sprint itself.
4:51 Speaker 00 So I thought I'd throw down seven practical tips that actually work now. Uh, this is based on what's found in the article, so let's give you my notes. Number one, make sure you have a definition for ready and for done. I know there's big controversy about that, but you need to do it. You need to talk to each other. You need to figure these things out and ready means there needs to be some intake mechanism for the work. And done means we have to have some way to qualify that the work is actually finished. It's as easy as that. What makes a story ready to be planned? What makes the story done for real? Uh, coming in at number two, groom your backlog religiously, regularly, every single week. You should be having a backlog refinement meeting. It's not glamorous, but it's essential. It should be one hour a week between a product owner and team.
5:35 Speaker 00 And, uh, just like flossing, but with fewer cavities, a lot more sanity. All right, let's go to number three. When you do estimation, you should do it in an open release planning session where you estimate as a team. Use T-shirt sizes. Don't try to make points perfection. Try to use T-shirt sizes as a method to say the size of the wall that you're trying to paint. The size of the effort of what you're trying to do. And if you can focus on sizes, it's going to bring us to agreement faster. Because, uh, clarity lives in a place where everyone is confused over time. Speaking of time, here's where you do want to apply time. Instead of trying to apply time to points, apply time to time boxes.
6:17 Speaker 00 Set time boxes for story discussion. Set time boxes like a countdown clock for, um, Meeting timers and for anything that you can time box because things that are time boxed actually stay on track. At least that's what I found. How about number five? Leave breathing room. This is what I was just always saying, and it's not because stuff always comes up. I want to be clear. The reason you want to leave breathing room is because you want to make sure you successfully finish everything you can in a sprint and you have an opportunity to get a head start on the first item and the next sprint. It's better to do that than it is to carry something over every single sprint. Because as a leader, if you're predictable, even if it's for a smaller amount of points, that means more to me than you constantly carrying things over from one sprint to another. If you're that person that carries things over from one
7:02 Speaker 00 sprint to the next, to the next, to the next, what that tells me is that you're disconnected. And what it tells me is that you're not predictable and that you can't get things done and that we need to make adjustments. That's what that tells me. Prioritize ruthlessly. Try using the Po Bafata method. Use objective stack ranking. Balance things like Moscow priority and technical size, right? Use those things together to get some type of prioritization and then tweak or fine tune that prioritization as you need. And finally, number seven, bring snacks. Sounds funny, but nobody ever makes good choices if they're hangry, whether it's coffees, cookies, leftover birthday cake. It's, it's just, you know, even if you're doing it from home, bring snacks, bring
7:46 Speaker 00 them back. In my drawer right now, I have a bag of chips. It's just the way you do business.
7:51 Speaker 00 If you can do this, morale will improve. I know it sounds silly, but you just want to keep everybody on the same page. So agile on paper, simple. In practice, messy. It's human, sometimes funny, most of the time in a tragic way, but sprint planning doesn't have to be painful. If it's painful, it's because you made it painful. It just takes some practice, good communication, and courage to call out nonsense when it happens. So next time you're sitting in a planning meeting, whether it's online or in person, and you're wondering if this is agile or improv comedy, just remember that you're not alone. Every team fumbles at some point, and the goal is progress, not perfection. Now, go forth and plan better. You've got this. You can do it. That's going to do it for this episode. I hope you enjoyed it. If you have a topic you want us to discuss,
8:36 Speaker 00 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.
Previous The Light on Maple Street — A Holiday Story About Small Acts That Become Everything Next 4 Steps to Building a Product Strategy Page updated November 6, 2026 · transcript and summary are machine-generated