Pod Insights The Agile Daily Standup - AgileDad Story Point Estimations are failing your Team! - Here We Go Again... About this episode Story Point Estimations are failing your Team! - Here We Go Again...
Story Pointing wasn’t a completely novel idea. It evolved out of the Delphi method — a research technique that helped drive consensus and forecasting built on collective wisdom. In 1950s, RAND Corporation https://www.rand.org/topics/delphi-method.html began using it as a way to forecast the effect of technology on warfare.
So, it wasn’t just an idea dreamed up by someone in the Agile community randomly — no. It’s actually based on a scientific approach. Something that’s been applied and true in other disciplines for many, many years.
And, when Scrum needed a prescriptive technique to help the Teams estimate and measure the amount of work the Team could consistently deliver Sprint after Sprint, this became a recommended approach.
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:16 Speaker 00 This conversation certainly comes up at least every once, every four or five months. So I thought, why not have the conversation again? Because you know, it's likely time, let's get the microphone in here. So it's likely time for us to have a conversation again. So let's do it, let's not delay.
0:31 Speaker 00 An article was recently published and it reads, quote, "Story point estimations are failing your team."
0:40 Speaker 00 Right out of the gate, before I read any further, I'm just going to give you a quick opinion. If you leverage story points the wrong way, they'll never work. If you understand how to best leverage story points and how to apply them correctly, they work flawlessly. So let's, let's get into this and let's see where this review of this article is taking us. "Story pointing is not actually a completely novel idea. It evolved out of the Delphi method, which is a fact. A research techniques to help drive consensus and forecasting built on collective wisdom. In the 1950s, Rand Corporation began using it as a way to forecast the effect of technology on warfare." Let's stop. Well-known facts, I'm proud that they brought this up.
1:22 Speaker 00 So many organizations and people don't even want to talk about this part of it. That it really was something and it came from somewhere, that it's not something that's somebody made up. There's actually science behind why we do this. He goes on to say, "So it wasn't just an idea dreamed up by someone in the agile community. It's actually based on a scientific approach."
1:41 Speaker 00 Something that's been applied and true for disciplines for many, many years. And when Scrum needed a prescriptive technique to help teams estimate and measure the amount of work the team could consistently deliver sprint after sprint. This became a recommended approach, built on the concept of yesterday's weather. If we're able to complete X things yesterday, we're highly likely to complete the same amount today. Story pointing made it easy to count volume of work completed via velocity and use that to project future plans." I want to give this person a compliment. This is the first time I've ever heard someone talk about velocity being a volume of work. Every time I explain velocity, I always use containers like a water jug or a soda can. Or water bottle. And I explain that even though these containers are all different sizes,
2:26 Speaker 00 it doesn't mean each of these containers could have enough servings to fill three cups, or five cups, or six cups for the number of developers on the team. Some of those people are expert drinkers and they can consume more. Others don't consume as much and they drink much more slowly. It doesn't mean that one's wrong or right. It just means based on skill sets, tools, other things regarding aptitude, that certain individuals can consume certain things faster. And if you tried to do this based on an individual person, you're going to find that maybe this round, that person might be the lowest or slowest person. But the next round, they're working on something they're really familiar with and they become the fastest. So what I'm trying to say is, number one, velocity should never be measured by individual. And number two, team velocity will stay consistent,
3:11 Speaker 00 but the players who are doing the most more or less work could change over time. And I think, I think that's where we're going and that's why we measure volume. But let's continue. Today, however, we find lots of teams being very frustrated and disappointed with this technique. We see velocity to be misused by senior leadership and many teams aborting story points in favor of other estimation forecasting techniques or no estimation at all. Let's pause. I think the question now is, is story points still valid? Does it really work? Or should teams consider moving to something else? Here's what I know.
3:44 Speaker 00 I personally, going through and coaching at many large organizations, have not seen teams and organizations going away from story points. What I've seen is the need for someone to help explain how story points really work, so that it makes sense to them, so that they could end up using those story points and leveraging them. Does it work? Anyone who's been in a software development realm since the early 90s, late 90s, early 2000s, you've seen story pointing work well. The key here is to separate it from time. It was a huge improvement when it first came out over the, let's just stick our finger in the air and feel for the wind or roll the magic eight ball, right? But you know, since then, many things have gone wrong too.
4:26 Speaker 00 And I found that if you misuse story points, they never work. So story points will never work if the teams never established a baseline for what a small or large story is. And what I mean by that is, I often say, As part of release planning, like rapid release planning, or some people might call it PI planning, or big room planning. One of the exercises you should do is have all of the different teams working together, identify one item from the batch that they're going to review for that release, that they feel is small, or size and scope, or large. The reason why small or large, if somebody started with an extra small, what if you find something smaller? If you started with an extra large, what if you find something larger? If you try to start with a medium, it's just too arbitrary and it's hard to pick something that's in the middle.
5:11 Speaker 00 So usually starting with a small, starting with a large is a good way to go, and it gives you room to grow in either direction. That should be your baseline. And I think that if you do have a baseline, you're going to be successful. But notice I said the baseline based on t-shirt sizes, not on numbers. One of the things that we have a habit of doing is when we say something is three points or five points, immediately, someone in leadership has to, you know, anyone with an MBA has to tie this back to some value. Is it $5, $5,000, $50,000, $55,000, $5 million, $5 teams, 5 weeks, 5 oranges, 5 strawberries? They just have to tie the number to a value. And I think that's what's, that's what's preventing a lot of people from using these correctly.
5:53 Speaker 00 I think if you just look at the job and say, is this job bigger or smaller than a previous job? You're going to wind up with much more accuracy. So you're going to end up with high accuracy and low precision. The job isn't to make it perfectly precise. If the job was to make it perfectly precise, we'd all be wrong, because each individual does things different. But if our job is to make it as accurate as possible, we can do that without having to deviate too far from our story point formula. All right, let's go to number 2. So, one more time, the topic, story points will never work if, voting in the open.
6:26 Speaker 00 This is an interesting one. Let me explain what they mean by this. I get what they're trying to say, I just read it. And the point they're trying to make is correct. But the way that they're displaying it's not. So they call it story poker or planning poker for a reason. It's called poker. People should hide their hand and reveal at the same time. Okay, let's pause. Here's what I know. The reason it's called planning poker is because initially, most of the tools, whether you're using, whether you're using Azure DevOps or Jira, whatever tool you're using, pick your poison. They all have two fields for estimate. They have an initial estimate and then they have estimate. The initial estimate was supposed to be a swag of some kind. It was just supposed to be an initial guess, a swag, that the product owner could consult with a technical analyst and come up with.
7:09 Speaker 00 And then they can leverage that as a T-shirt size and hide it. The reason they hide it is exactly what you're saying here. So at release planning, we could let the teams collaborate and talk about what they think the size is. And then compare the team size to the initial size via estimate versus initial estimate. But most people didn't know how initial estimates to be used inside of those tools. So most organizations wound up turning it off instead of trying to figure out why it's there. The secret is if you get the initial estimate and then you get the team's estimate, the team's estimate doesn't have to be closed door, but the initial estimate should be. And what that means is you'll have some validation across platform. So that way either A, the product owner clearly understands or the team understands what's going on and we're good to go.
7:50 Speaker 00 Or B, the product owner is way off and they don't understand the scope of what's required in order to build something. Or C, the team doesn't understand the small scope the product owner is asking for and think that they're asking for something much bigger. But nonetheless, you still have to have something open in order to be able to see it. So when they say voting in the open is bad, I'm going to argue and say that's false. I think that allowing people to see the initial estimate versus a regular estimate is bad. But voting out in the open with the whole team is actually a good thing because then it opens up lines of communication. Let's go to number three. They labeled it overpowering. The team starts throwing around numbers and the conversation goes like this. Scrum master, so how many points do you think it is? Developer, at least five. Product owner, why five? Because it feels bigger than three and I don't want to be the one who says thirteen.
8:36 Speaker 00 Putting pressure on teammates to lower their number is indeed a balancing act. Um, I, I think that, you know, if we understand why they said it was 13, we're fine. But for me, I say 12358 is extra small, small, medium, large and extra large. Then when you get to the 13, 21, 40 and 100, that's small epic, medium epic, large epic and extra large epic. That still need to be broken down on a smaller pieces. So I, I'm looking at it from that perspective. Number three, it says story points will never work if uh, there's a lack of believers. Okay. A lack of believers. And what that means is when organizations have people joining teams and the team says, you know, I don't know. Um, I, I don't know about that or I don't understand it.
9:22 Speaker 00 If there's no common ground, if the team doesn't want to establish common ground on rules, policies, belief systems, the way they're going to do this. They're, they're going to struggle with agile because agile in fact is a discipline. It is a mental way to process information so that you can achieve a, a, a great result. But I think that so many organizations don't look at it that way. And yeah, it just winds up being a nightmare. Uh, story point doesn't work when grooming is painful and I'm going to call it refinement instead of grooming. When all a team does to meet a time box of, of one hour every two weeks is prioritize and story point the work and that's it. They're done. Only barely to scratch the top of the backlog. It's obvious that everything else is going to fail.
10:04 Speaker 00 Uh, rush teams will agree to rush on anything. After all, uh, software developers don't love to talk. They love to code and love to do their other things. They want to get out of that meeting as soon as possible. But if you give them everything that they need and they come prepared for backlog refinement meeting, you can usually get great value out of that and it's going to help you be way more accurate in your forecasting. Okay. Uh, story points don't work when, when your velocity metric is being abused or used incorrectly.
10:35 Speaker 00 So you can't use velocity as a performance indicator. No one ever said velocity was a performance metric. Velocity is a metric that measures volume. The volume of work a team can do in a day, a week, two weeks, et cetera. And that's how it's supposed to be used. But there are too many other people who don't understand that. And they try to pop additional information out in the form of reports and it just doesn't work. You need to really understand velocity. I think the key here is just that story points themselves aren't broken, but people's understanding of story points are. And if you're not using it as like a T-shirt size or using it as something that's easy to get your head around, you're destined to set yourself up for failure.
11:18 Speaker 00 So my advice is try, try to choose T-shirt sizes and nothing else. If people don't want to use T-shirt sizes, use a dog size. If they don't want to use a dog size, use a dinosaur size. You'll find something that they have in common. Use that and make sure you capture an initial estimate from a product owner who's consulting with a technical analyst. And then make sure you capture the actual, the actual T-shirt size from the team. So you can make a valid comparison. And then if necessary, have a conversation around each one of those, a time box conversation for a few minutes to clarify and say, well, product owner, you said this was medium team. You said it was extra large. What did you see? And that way the team can get their information that they need to make a conscious decision. Yes. Okay, 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 Hesitant.com.
12:03 Speaker 00 We'd love to have you. And as always, we encourage you to stay healthy, stay well and stay healthy, my friends. Until next time, do take care.
Previous What Makes a Great Scrum Master? Next Using AI to Go From User Insight to Better Backlogs - Mike Cohn Page updated November 6, 2026 · transcript and summary are machine-generated