Measuring Project Health -- Part II

From the developerWorks archives

Kurt Bittner

Date archived: December 16, 2016 | First published: March 15, 2007

from The Rational Edge: What aspects of a software development project should be measured in the middle phases of the lifecycle to ensure that the project is healthy and on track? Read how risk lists, backlogs, and other project artifacts can be used to objectively measure project health.

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 steps and illustrations may have changed.

ArticleTitle=Measuring Project Health -- Part II