Lessons Learned
There are several key lessons learned from this PIE project
:
-
Although Defect Prevention is considered an SEI/CMM Level-5
KPA, we found that a strong level-3 organization, with a Defect Prevention
infrastructure, can build an effective Defect Prevention Process, and obtain
excellent results.
-
The primary cause of defects is classified by the development
team as oversight, or human error (almost 75% ). Our experience
shows that the term "oversight" is too broad and should be broken down
somewhat, probably based on those Beizer clasifications which were categorized
as "oversight".
-
The Timing of the Phase Kickoff meetings is critical. A Phase
Kickoff should be planned early and performed as close as it is possible
to the beginning of the phase.
-
In order for the Defect Prevention process to be effective,
the software teams need in depth training and initial support in using
the taxonomy and performing the root cause analysis.
-
There is a need for a tool to input the classification of
defects, according to the Beizer Taxonomy. An automatic tool is needed
to analyze the defects and to get statistical results. The current vehicle
we have for input of cause analysis and defect classification is deficient.
A better interface is needed, as well as a mechanism for adding new categories
to the Beizer Taxonomy. Standardized statistical analysis reports are needed
for use by all projects for ongoing Defect Prevention and process improvement.
|
|
Lessons learned
|
|
|
|
Measured results
|
|
|
|
|
