Velocity (software development)
This article needs additional citations for verification. (May 2018) (Learn how and when to remove this template message)
|Paradigms and models|
|Methodologies and frameworks|
|Standards and Bodies of Knowledge|
Measuring velocity is sometimes called velocity tracking. The velocity metric is used for planning sprints and measuring team performance. There is no scientific evidence that measuring velocity improves planning effectiveness or team performance. Furthermore, the metric can be misleading.[according to whom?]
The following terminology is used in velocity tracking.
- Unit of work
- The unit chosen by the team to measure velocity. This can either be a real unit like engineer-hours, engineer-days or Product Backlog Items (PBI) or an abstract unit like story points or ideal days of effort. Each task in the software development process should then be valued in terms of the chosen unit.
- The interval is the duration of each iteration in the software development process for which the velocity is measured. The length of an interval is determined by the team. Most often, the interval is a week, but it can be as long as a month.
Velocity always involves counting the number of units of work completed in a certain interval. However, units of work can be measured in many different units.
The main idea behind velocity is to help teams estimate how much work they can complete in a given time period based on how quickly similar work was previously completed. Velocity is relative measure. In other words, the raw numbers mean little; it is the trend that matters.
One problem with velocity is that it conflates work done with planning accuracy. In other words, a team can inflate velocity by estimating tasks more conservatively. If a team says that a task will take four hours or is worth 4 points instead of taking two hours or being worth two points, their velocity will look better (sometimes called point inflation). Velocity should not be used as a performance metric.
A second problem with velocity is that it does not take quality, alignment with user goals or priority into account. Velocity can be increased by neglecting good design, refactoring, coding standards and technical debt. Simply completing features as quickly as possible increases velocity regardless of quality. Similarly, velocity includes work done regardless of the benefits of that work. For example, building a feature no one wants or needs still counts as "work done” and completing a work unit which moves away from a user goal such as ease of use is movement in the opposite of the direction desired. This makes “velocity” in Agile more like the concept of directionless “speed” from physics.
A third problem with velocity is that it is often misused as a measure of efficiency or team performance. Velocity is a metric of work done, not efficiency. Velocity can be increased by working overtime or adding team members, neither of which necessarily increase efficiency or performance.
In summary, velocity is a problematic metric because it is easy to manipulate and often misused as an indicator of efficiency.
- Rubin, Kenneth (2013), Essential Scrum. A Practical Guide to the Most Popular Agile Process, Addison-Wesley, ISBN 978-0-13-704329-3
- Measures of size, agilesoftwaredevelopment.com, archived from the original on 2010-10-26, retrieved 2010-09-24
- Glossary of scrum terms: Velocity, archived from the original on 2010-11-29, retrieved 2010-09-24
- Agile 101: Agile Software Development Velocity, VersionOne.com, archived from the original on 2010-10-02, retrieved 2010-09-23
- "point inflation". innolution.com. Retrieved 2019-06-06.