This blog will be looking at the difference between how we view increases in velocity and the type of speed increased velocity is linked to.
What is velocity?
Velocity is the rate at which potentially releasble work is completed within a sprint that is tailored towards the end objective which is the final release of software. Velocity per sprint can be displayed in different ways however, in many instances line graphs are developed to show the change in team velocity from sprint to sprint. Velocity can increase due to various factors such as an increase in team efficiency for example, the ability for the team to reuse code enabling the team to complete more releasable incremented work which draws the team closer to the end goal within that sprint.
Why higher velocity is not ‘bad’ speed in development
One of the main reasons why an increase in velocity is not always an increase in speed in development is because more work completed in a sprint does not mean code in a particular sprint has been done correctly or adds value to the customer and as a result if lots of bugs/technical debt have been created this slows down the development. When bugs are found this takes time for other features to be developed to help towards delivery of the releasable product which is bad speed. Good speed which is linked to increased velocity is where there was more work developed meeting the customers needs and adding value towards the end objective .