Are Points the New Currency of Agile?
Let me set the scene for you: I recently shadowed a Sprint Review where the Scrum Master proudly unveiled a slide showing the team's velocity over the past six sprints. The numbers were going up—the universal sign of success! Then, almost as an afterthought, she casually mentioned that new team members had joined the team.
Wait, what? Did no one else see the connection between more people and more points? Of course velocity increased—adding team members will do that. But instead of digging into what this meant, the conversation stayed laser-focused on how “productive” the team had become.
Ah, yes. Points: the ultimate measure of progress. Forget solving user problems or delivering value; as long as the numbers look good, we’re good, right?
The Worship of Velocity: An Agile Parody
Here’s the unspoken truth: Story points are the agile equivalent of Monopoly money. They’re great for planning and estimating, but when teams and leaders start treating them as the ultimate goal, things get ridiculous.
Let me break down what happens when we bow at the altar of velocity:
1. Numbers Over Everything
Who cares if the user isn’t happy? We completed 100 points this sprint! Look at us go! Never mind that those points represent a mishmash of tech debt, low-value features, and tasks no one will ever notice.
2. The Art of Gaming the System
Want to boost your velocity? Simple! Just estimate everything at 13 points. Suddenly, you're delivering more than ever—except you’re not. But hey, the chart looks amazing, and that’s all that matters.
3. Context? Who Needs It?
Velocity increased because we added new team members? Nope, we’ll just assume it’s because the team is so much better now. Let’s not even talk about onboarding time, coordination challenges, or whether we’re delivering anything users actually care about.
Let’s Get Real: What Actually Matters?
Points might make for a nice graph, but users don’t care about your velocity. No one ever opened an app and said, “Wow, I bet the team completed 50 points this sprint!” They care about value—so why don’t we?
Here’s what teams should actually focus on:
1. Value > Velocity
Points don’t ship. Outcomes do. Ask yourself:💡 Are we solving real problems?💡 Are we delivering something users need? Or are we just chasing numbers like hamsters on a wheel?
2. Conversations > Calculations
The beauty of story points lies in the discussions they spark. They help teams align on complexity and scope. But if we treat the number as the goal, we miss the point (pun intended).
3. Context > Correlation
Velocity went up? Cool. But why? Did we add team members? Simplify scope? Game the system? Metrics without context are like plot twists with no setup—they’re meaningless.
How to Break the Velocity Addiction
Here’s a crazy idea: Stop focusing on points. Start focusing on outcomes.
Tie Sprints to Real Value: If your sprint goal doesn’t connect to user needs, why are you doing it?
Celebrate Learning, Not Just Completion: Delivering fewer points but learning something game-changing is a win.
Ask Better Questions: Instead of “How many points did we finish?” try “What impact did we make?”
Final Thoughts
Agile isn’t about chasing numbers. It’s about delivering value, solving problems, and improving continuously. So let’s stop pretending velocity is the holy grail. It’s a planning tool—not a badge of honor.
And if your next Sprint Review includes a slide celebrating velocity, just remember: somewhere out there, a user is waiting for real value—not your points.
At NBD Consulting Services, we specialize in helping teams ditch the points obsession and focus on what really matters: outcomes, value, and continuous improvement. Want to know how? Reach out—we’d love to help.
Comments