Measuring and Determine Velocity

Get an idea about how to measure and determine the velocity of an Agile project.

Measuring velocity

The total number of points for the project is now established. The rate at which these points are realized will determine the end result. Velocity in Agile is usually expressed as follows:

  • Hours per point: This is the average number of hours required to complete an individual point. This is easily determined by dividing the number of hours on the project by the number of points achieved. For example, 8.3 hours per story point or 15.4 hours per smart use case point. The number of hours per point is interesting when the total number of hours for a project needs to be established. If a project realizes 1109 smart use case points, the 15.4 hours per point provides a good basis for an estimate of the total number of hours for the project.
  • Points per iteration: Another important value is the number of points the team achieves per iteration. This is called the iteration velocity. This value can also be calculated easily. Divide the total number of points achieved by the number of completed iterations. The iteration velocity determines the duration of a project. It’s an important tool for improving and adjusting the planning.

Get hands-on with 1200+ tech skills courses.