Chapter 11. Measuring and Monitoring Velocity

As you recall from Chapter 9, “Planning a Release,” the release plan was created by breaking the project into a series of iterations, where each iteration included a certain number of story points. The number of story points completed in an iteration is known as the project’s velocity. When planning the project, we either used a known velocity (if we had one, perhaps from another similar project) or we made one up. Velocity can be a useful management tool, so it is important to look at the team’s velocity at the end of each iteration as well as during the iterations.

Measuring Velocity

Because velocity can be such an important measure, it is important to think about how we’ll measure it. Most stories ...

Get User Stories Applied: For Agile Software Development now with the O’Reilly learning platform.

O’Reilly members experience live online training, plus books, videos, and digital content from nearly 200 publishers.