PROCESS METRICS

We measure the efficacy of a software process indirectly. That is, we derive a set
of metrics based on the outcomes that can be derived from the process. Outcomes
include measures of errors uncovered before release of the software, defects delivered
to and reported by end-users, work products delivered (productivity), human
effort expended, calendar time expended, schedule conformance, and other measures.
We also derive process metrics by measuring the characteristics of specific

software engineering tasks. For example, we might measure the effort and time spent performing the umbrella activities and the generic software engineering activities.
Grady argues that there are “private and public” uses for different types
of process data. Because it is natural that individual software engineers might be sensitive
to the use of metrics collected on an individual basis, these data should be private
to the individual and serve as an indicator for the individual only. Examples of
private metrics include defect rates (by individual), defect rates (by module), and errors
found during development.