Best practices for effective velocity tracking

Tools and techniques

From the developerWorks archives

J. Jeffrey Hanson

Date archived: May 15, 2019 | First published: December 04, 2012

Using velocity tracking, project managers strive to measure and monitor the productivity of software developers and others participating in an Agile-based project. This article examines the concepts behind velocity tracking. It also discusses tools that help facilitate effective implementation and maintenance of these concepts, such as iterations, burn-down and burn-up charts, backlogs, and issue-tracking systems.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some content, steps, or illustrations may have changed.

ArticleTitle=Best practices for effective velocity tracking