Agile Velocity: measuring what we don’t want?

Velocity is Agile's most ubiquitous metric. But does it measure the right thing? Let's talk about that.

[@benhill4874]

Good point! In the US we are often more about driving the amount of work completed - Velocity. But Value, as you say here, is much more important. So how to measure value rather than Velocity, or with it, is the real question.

[@stantoniification]

My experience is of a team that prioritises items by value, but uses velocity to create a sense of predictability around release dates etc.

[@Developmentthatpays]

That sounds good to me 👍

[@youngloenoe]

Gotta measure the outcome to make sure the work has value. Or else it becomes a factory just putting out work so people have jobs.

[@Developmentthatpays]

You're exactly right: if we're not careful it becomes a factory.

[@PaulHenman]

Focusing on velocity -> feature factories -> keep shovelling widgets out the door & don't waste time thinking about feedback ☹

[@PaulHenman]

But if you're stuck in that situation and the pressure is to increase velocity, simply change all your 1SP stories to 2SP, your 2SP to 4SP, etc.

[@Developmentthatpays]

I've had that happen. Lead Dev: "I know this sucks, but from now on: if it's a 5, it's and 8; if it's an 8 it's a 15."