An Antidote to Velocity Obsession

Getting things done is great; to get things done is why we start things in the first place and why we follow through even when presented with obstacles and setbacks. We do things because they will (hopefully) bring us to some better state. So getting these things done quickly is good because we arrive at this better state sooner.  We track our rate of development (velocity) as a useful measure of progress and also as a leading indicator towards when we should be done. However focussing too much on velocity is dangerous; it leads to myopic mindsets and even moronic behaviour. Yes, velocity is good, but not at the expense of quality, good-will, or noticing subtle changes in direction. At […]

Read more

Velocity Signature Analysis

Most agile projects track their velocity. For the past 10 years or so I have been studying the velocity profiles of my projects and any other projects I can get data from. Velocity profiles tell a story about the project, and like signatures are unique. Tracking stories, or more normally points completed per iteration, gives the classic velocity graphs such as the one shown below. Here we can see the Projected Velocity shown by the dotted blue line and the Actual Velocity shown in dark blue. From observing 15-20 projects I have noticed the following reoccurring patterns. Am I the only one, or are these common? 

Read more