Pod Insights The Agile Daily Standup - AgileDad Agile Anti-Patterns That Are Impacting Your Velocity About this episode Agile Anti-Patterns That Are Impacting Your Velocity
Velocity is not vanity. It is feedback. When velocity stops reflecting reality, the team loses the ability to learn and improve. Velocity that lies is worse than no velocity at all. The goal here is clarity, speed, and humane work rhythms.
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 Let's have a quick conversation about velocity. So velocity is not vanity. I'm going to say it again. Velocity is not vanity. In fact, velocity is feedback. When velocity stops reflecting reality, the team loses the ability to learn and improve. Velocity that lies is worse than no velocity at all. The goal here should be clarity, speed, and humane work rhythms. If you're doing those things, you got this down. So let's talk about some anti-patterns. Some anti-patterns that lead to people abusing, misusing velocity?
1:00 Speaker 00 Or things that are causing your organization to not understand how velocity works? So the first one I want to talk about is the one, the one story that's too large to witness sprint. I see this all the time where people say, "Well, this just can't be broken down." So they take into their sprint this really, really large item. And that concerns me because I can tell you right now, it should never be that way. You should never be in a position where you're taking on this giant item because you just feel like, "Well, I guess we can't break it down, so we need to take on this, this humongous item." There's never anything that's too large to break down. In fact, there's gotta be a way to break these things down into some type of vertical slices.
1:42 Speaker 00 But people get caught in a scrum trap where it says that every single sprint, every increment that you build needs to be potentially shippable. Now, I agree that's a good idea. If you have something that you're struggling to make a potentially shippable increment with, it doesn't mean you should ignore breaking it down. Don't get caught in a trap that we'll just leave it large and see what happens. I use the t-shirt sizes where one is extra small, two is small, three is medium, five is large, and eight is extra large. If it's larger than an eight, if it's larger than an extra large, it needs to be broken down. Then it's not to say that it's going to perfectly break down into smaller sizes. It could be multiple stories of varying sizes, but we still need to take the opportunity to do it because we don't. It's going to kill us in the long run. Let's go to number two.
2:26 Speaker 00 Over refinement of backlog items. Now, this one sounds odd, but I've seen organizations where they go into their backlog refinement workshop, which should be once a week for an hour between a product owner and team. But instead of going in with just enough information and making it all work, they go in and they want to know every minutia piece of detail. And as a result, they're refining, then continuing to refine, then over refining, then refining again. And what winds up happening is everybody wants to know all the acceptance criteria, the complete happy path. Uh, let's do a 30 minute spike during a session if we're not sure for just one item. You can't do that.
3:06 Speaker 00 If people are requiring you to spoon feed them requirements, that means that there's another, that's a symptom of something bigger. The team trust has been violated or broken, the organization's not allowing you to properly refine these items that the team can go in and do the work. There are many things wrong with this scenario and we need to do our best to make them right. Let's go to number three. The single point of knowledge or the hero mentality. I know so many people who gatekeep and these individuals are causing us to have severe anti-patterns where we can't, we can't deliver things of value because, well, Joey is way too busy. So because Joey's so busy, we can't, that there's nothing we could do to make it better.
3:52 Speaker 00 And I know it sounds shocking or harsh, but we need to make sure that Joey understands that his job is not to be the single font of all knowledge, the single source of knowledge. When you can get that person to contribute and add value and teach people how to do things and the team understands that they can't rely on this one person or individual to be their single source of knowledge for items. And that individual understands the importance of helping others understand, even if that individual helps five people each understand 20% of what they know. It's better than not having anyone who understands 100% of what they know. All right. Let's go to the next one. The next one I like to call Velocity Theater.
4:33 Speaker 00 This is reporting velocity with no value, or when teams game the system. Let's face reality, teams can optimize numbers, leadership can optimize numbers. And those numbers oftentimes don't reflect value. And this is why velocity mistakenly gets considered as a vanity metric. If you're constantly refining scope to hit certain numbers, that means that you're artificially breaking down or splitting tickets, you're artificially inflating or overcharging for specific items. You can't do that. You need to be consistent with your estimation, consistent with your forecasting. And you need to make sure you have the right party of people involved in the estimation process in order to make sure you're getting the highest value.
5:15 Speaker 00 Okay, let's go to this next one. Meetings that are addressed as collaboration. So this is interesting. I hear people all the time, "Oh, we're gonna get together and collaborate on this. Let's just have a quick meeting to talk about it." And what winds up happening is the organization is spending so much time in meetings talking about it that none of the work actually gets done. So I mean, when you think about it, the team's already involved in daily scrums, kickoff meetings, meeting sinks, design reviews, retrospectives. They need to spend a little bit less time in meetings. And if we can keep them out of meetings and keep them doing work, we might actually be able to get some work done. And then finally, my last one for you. I go into organizations often and I see they have a really rigid definition of done.
5:58 Speaker 00 And one would think, "Oh, that's a good thing," but I'm gonna argue that it's not. And the reason why I say it's not is because there should be no one concrete definition of done that applies to every team, every product, every project. If there were, boy, that would make life easy, but it just doesn't exist. So what do we do instead? We need to make sure that we are delicately handling definition of done. Now, you could have some guardrails, but you want to make sure the definition of done matches the team's needs and the organizational needs. And that we're following definition of done in such a way that we can move things from A over to B. If we can't do that, then we're doing something else wrong. So we need to make sure that we have the right movement in place. And that definition of done supports our process and doesn't hinder our flow.
6:43 Speaker 00 So that's going to do it for this episode. I hope you enjoyed 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.
Previous Sprint Goals DONT Work - Or Do They? Next The Most Underrated Advantage of Short Sprints - Mike Cohn Page updated November 6, 2026 · transcript and summary are machine-generated