Change control reports

This category contains reports that help you control and manage changes that occur during the course of the project. The reports help to assess the health of the project and proactively take corrective action by monitoring parameters, such as the number of lines of code, the number of defects, and how these numbers vary during the stage of the project.

The following sample reports are available:

Code Churn

This report shows how the volume of code changes in a project trends over time. An upward slope is normal through the early and middle stages of a project. As the project nears completion, the curve should slope downward. An upward slope late in a project might indicate that the project is not stabilizing.

Code Contributions

This report displays the amount of code produced by each developer. Understanding the relative code contributions that people make to a project is important. Generally, the work should be spread relatively evenly across the team. One person with significantly more or less than the others could indicate a project planning issue. However, this report does not take into account factors such as other responsibilities, relative difficulty of the work, and vacation time.

Defect Arrival Rate

This report shows the frequency of new defect submissions over time, categorized by severity. Generally, the lines should slope upward earlier in the project and then downward as the project nears completion. At least the high severity defect lines should show this trend, or else the project is not stabilizing.

Defect Distribution

This report shows the number of defects per component in a project. An upward sloping line may indicate a problem area to investigate, or could be due to increased testing. Similarly, a low value might indicate good quality or insufficient testing. The lines should generally slope downward later in the project.

Defect Verification Failure Rate

A "Verification Failure" is a defect that was fixed but had to be re-opened because the defect was not fully resolved. An increasing or high number could indicate a communication problem within the team.

SLOC by component

This report shows the number of lines of source code (SLOC) for each component. The report helps you to check whether the code size is reasonable and close to what is expected for that component.


Feedback