Pod Insights The Agile Daily Standup - AgileDad Velocity = The Most Abused Agile Metric Ever About this episode Velocity = The Most Abused Agile Metric Ever
Welcome to the dark side of velocity — the number that started as a planning aid and ended up as a weaponized performance metric, often wielded by people who’ve never touched a user story in their lives.
In this episode, we’ll break down:
What velocity is supposed to doHow it gets misunderstood and misusedWhy chasing it kills team healthAnd how to bring it back from the deadLet’s sprint into it. (Pun 100% intended.)
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 I remember hearing this conversation like it was yesterday. We need to increase our velocity this quarter. Okay, cool. So do you want me to work faster, lie more, or cut corners? Welcome to the dark side of velocity. I should say that better. Welcome to the dark side of velocity. That sounded better. The number that started as a planning aid and ended up as a weaponized performance metric, often wielded by people who've never touched a user story in their lives.
0:46 Speaker 00 Right? Yeah, and use the force. So I thought it'd be fun to break down what velocity is supposed to do, how it gets misunderstood and misused, why chasing it kills a team self, and how to bring it back from the dead. This sounds very Halloween-ish. But what is velocity really? Well, velocity should be used as a tool for forecasting and not for competition. In its purest form, velocity is a historical measure of the volume of work a team has completed in a given timeframe, usually a sprint. Right? So it's not a speedometer. It's not a benchmark for success. It's not a competition. It's not a target.
1:31 Speaker 00 And velocity's not measured by person. It's measured collectively as a group. It's a trend line. It's one that helps the team be able to forecast the quantity of work they can complete, the volume of work that they can complete realistically, and realistically take on in the future, based on how they've worked in the past, based on yesterday's weather. That's it. No corporate KPIs, no leaderboard rankings, no Team Alpha did 73 points. Why is Team Beta only doing 42? It doesn't matter. But you're probably asking yourself, where does it all go wrong? The moment someone outside of the team starts tracking or optimizing velocity is the moment when
2:13 Speaker 00 velocity stops being useful. It's the moment we start focusing solely on output and stop focusing on outcome. Velocity becomes a performance metric when started as a team tool becomes a scoreboard, or when management starts asking why velocity isn't increasing over time, or stakeholders start demanding more points per sprint. Suddenly, the team can start gaming the system. They can overestimate their story points. They can rush work to boost their number. They can, uh, they can skip factors, skip refactors, skip tests or exploratory work that doesn't show up in their points total. Velocity becomes a number to hit in that case and not a signal to reflect on.
2:55 Speaker 00 We need to take the foot off the gas. Sometimes velocity becomes a comparison tool. Every agile coach has lived through this. Team A is doing 60 points per sprint. Why is team B only doing 45? Uh, because they're different teams composed of different people within different domains, doing different types of work with different levels of maturity, with different interpretations of what a small story is. I mean, you know the term relative, right? It's just, there's so many things that people do and do not understand about why story points are failing them when
3:35 Speaker 00 they're trying to use it as a whipping stick. Interesting, right? Comparing team velocity is like comparing how many fun units different people can get on vacation. It's not just unhelpful, it's fundamentally flawed, right?
3:52 Speaker 00 How about this one? I often see when velocity becomes the wrong answer to the right question. Executives want predictability. That's fair. I'm good with that. They want to know what they'll get and when they'll get it. That, that's also fair. I have no problem with that. But using velocity as a proxy for delivery certainty is like asking a barista how fast they brewed your coffee instead of whether they remembered the espresso shot.
4:21 Speaker 00 Velocity isn't a promise, it's a pattern, one that helps you plan, not a guarantee. So oftentimes, when we start chasing velocity, we see some flaws, we see some hiccups in the system. Oftentimes, we see burnout disguises commitment. Pushing for higher velocity usually translates to pushing everyone for more output. But people aren't machines. Piling more work on them, sprint after sprint, turns teams into tired, corner-cutting, morale-drained, delivery factories. We all know what good teams are rewarded with, right? Good teams are rewarded with more work! Because that's generally the practice that we like to follow. It results in low trust in internal gaming. When velocity becomes a goal,
5:05 Speaker 00 teams often inflate their story points just to hit last sprint's number. Yay! The metric becomes polluted, no longer measuring anything real, just the story teams are pressured to tell. That's sad. What about technical debt? Technical debt just starts to build and accumulate. Slower tasks like refactoring, experimentation, and documentation often get left out of point-based planning. Why? Because they drag velocity down, man. Ironically, these tasks will prevent future slowdowns and actually speed things up. Skipping them is synonymous for pure sabotage. But yet, we got a lot of Beastie Boy fans with the sabotage who want to sabotage everything, and that's not where we should be.
5:49 Speaker 00 It leads to misleading metrics. Velocity might be going up, but quality might be going down. Or maybe dependencies are growing. Or maybe our top people are just about to rage quit. Velocity says nothing about reality. I'm gonna say that sentence again. Velocity really says nothing about reality if you're abusing it or misusing it. That's the key. So what should velocity be used for? I kind of dissed it a little bit. Let's, let's get to the positive side, right? Let's get to the point, to the point. No peeking. I'm in a good mood today. Velocity works only when treated as a team-specific relative trend,
6:32 Speaker 00 a non-judgmental forecasting tool, a reflection of the system and not the people. So if you use it to estimate and not motivate, velocity helps answer the question, how many points worth of work can we take on as a team without getting burned out? I tell people all the time, when you're planning for story points, figure out what your velocity is. And if you feel comfortable, I could do this much work in a sprint, take one small item out. And I know it sounds weird, but just take one down. That way you're always successfully finishing everything you committed to in a sprint. And if by chance you do finish early, don't pull another item in. Go get a head start on the first item in the next sprint.
7:14 Speaker 00 So that way, if you get it done, great, pull it in. If you don't, it's okay. No harm, no foul. You just got a head start on the first item. What this does, it shows leadership, your commitment to finish the work that you've, you've actually committed to doing. And it shows that you're not being lazy, you're not trying to overstretch, you're not carrying things over from one sprint to the next. Also very important.
7:35 Speaker 00 Focus on stability, not growth. A steady predictable velocity is way more valuable than a rapidly increasing when it fails. If your velocity graph looks like, you remember that in Price is Right, when a guy gets to the top of the mountain, what happens? He falls off and dies. We don't want to be that guy. Your process needs more stability, not more speed. Speed, I am speed. Never mind, had a Lightning McQueen moment there. Pair velocity with conversation. Numbers lie without context. Oh my gosh, numbers lie without context. Instead of saying, we did 45 points, say, we completed 45 points, 20 of those were bugs.
8:17 Speaker 00 Ten were investigation and research. We spent extra time pair programming and our new teammate needed onboarding support. Velocity tells part of the story, but individuals fill in the rest. Don't just look at the number, look at the context. Keep it internal. Velocity is for that team. It's not necessarily for executives, it's not for marketing, it's not for cross-team comparison even. It's a planning artifact, not a performance review metric. I always say that if leadership wants transparency, give them delivery forecasts based on team's capacity, not velocity. Dashboards are things they don't understand unless you set them up in such a way that they do.
8:59 Speaker 00 You can use velocity, you can use burn-up charts, you can create a cone of uncertainty. You can give them the things that they're looking for and you can promise things in sprints. But you shouldn't ever do it just solely based on velocity, especially if the team's using velocity as a metric to compare to time. So other metrics that help, well, you can measure cycle time, right? You can look at throughput, you can look at are you limiting whip or not? Do you have too many things in motion? You can look at your bug rate or your defect ratio and make sure you're planning for defect sprints instead of trying to sort it all out. You know, every single sprint with a percentage of one individual's time. If you've got stakeholders or executives that are asking about velocity, try this. Velocity is a planning aid, not a performance metric.
9:44 Speaker 00 It helps teams self-assess what they can realistically take on, but it's not comparable between teams or sprints. If we want predictability, true predictability, we should track trends like cycle time and whip alongside it so that we can make sure we balance velocity accordingly. Or, if you need to be more blunt, you wouldn't ask a chef to cook faster by the pound. Don't ask developers to deliver by the point. I'm going to say that again, you would never ask a chef to cook faster by the pound. Don't ask devs to deliver by the point. It just makes sense, right? So, velocity was never meant to be weaponized. It was born as a humble planning tool, quietly helping teams gauge their own pace and figure out the...
10:30 Speaker 00 The quantity of work they can do, the volume of work that they can do. But in the wrong hands, it can become a lever for pressure, blame, and unhealthy expectations. The fix isn't just to throw it out, it's to bring it back to its roots. Local to the team, useful forecasting, contextual and not comparative, and honest to not game, because the real goal isn't to increase velocity. The real goal is to ship tangible value without losing your mind or self-worth doing it. That's going to do it for this article. I hope that you enjoyed it. 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. Bye now.
Previous A Make-A-Wish That Turned Into a Gift for Others Next If You Want Better Stories, Stop Writing Them All Yourself Page updated November 6, 2026 · transcript and summary are machine-generated