Velocity Stability

As a team monitors its velocity across iterations, patterns begin to emerge.

Velocity may exhibit stability, remaining consistent, or fluctuate from one iteration to another. Both scenarios offer valuable insights into the team's performance and work dynamics.

For effective forecasting and planning, a stable and steady velocity is preferable. A consistent velocity results in a narrow future cone of uncertainty on the team's burnup chart.

It is important to note the difference between raw velocity and weighted velocity when considering this stability. Weighted velocity, i.e. taking into account lost days and resources, should be used when calculating velocity stability.

Although velocity can evolve and ideally increase over time, a stable velocity signifies that the team is successfully attaining the Agility Outcomes of Trusted Dependability and Enduring Sustainability. It reflects a reliable and sustainable pace of progress, contributing to the team's overall success in delivering valuable outcomes consistently.

Resources

The topic of Velocity stability is covered in the Adaptive Agility Fundamentals class.

In this short article, Agile Alliance mentioned how failing to bring stories to completion and "see-sawing" velocity are valuable observations a team can action on. One expected response is to seek a finer-grained decomposition of stories.