Velocity is a mythical comfort metric

A quiet road disappearing into fog, symbolising uncertainty, perception and the limits of what can be seen at any one time.
Sometimes the numbers feel solid, even when the road ahead is unclear

Velocity feels reassuring.
A number. A trend. A sense of progress you can point to.

But velocity is a mythical comfort metric.

Outside the narrative context of a single team, velocity has no objective meaning. It is not a speedometer. It is a storytelling device – a shared fiction that helps teams coordinate expectations and have conversations about capacity and flow.

The moment velocity becomes a target, it corrupts its own purpose.
Teams optimise for the number rather than the learning behind it. Quality bends. Curiosity fades. Reality gets edited to fit the chart.

True agility is not measured in points delivered.
It is measured in learning rate – how quickly reality updates your understanding of the problem, the solution and the people doing the work.

Velocity can comfort.
Learning transforms.

Instead of focusing on better estimates…

A tweet from John Cutler has been challenging me recently:

Instead of focusing on making ‘better’ estimates, focus on:

  • working smaller
  • integrating frequently
  • exposing work to users/customers sooner
  • testing assumptions earlier
  • limiting dependencies
  • less fragile code
  • limiting handoffs

Your estimates will improve.

Why?

Continue reading Instead of focusing on better estimates…