Do Your Inspections Work?

  • (an inspection that goes much faster than average probably missed some defects).
  • Correlate pairs of metrics, such as defect density and preparation time (slower preparation generally finds more defects).
  • Use statistical process control to monitor key parameters, such as defect density (an unusually low defect density could indicate that inspectors missed some defects).

Inspection data can also indicate whether you are catching defects in the same lifecycle phase in which they were created. Because the cost of dealing with defects in subsequent stages increases rapidly, your goal should be 100 percent defect containment, with none leaking into downstream work products.

Some Measurement Caveats
The prime directive of software measurement is that a manager must neither reward nor punish individuals for their metrics results. The first time a practitioner is punished for some data he reported is the last time the manager will get accurate data. Aggregate the data from multiple inspections to monitor averages and trends in your inspection process without compromising the privacy of individual authors.

Beware of measurement dysfunction, which arises when the measurement process leads to counterproductive behaviors. Forms of inspection measurement dysfunction include defect severity inflation or deflation, and distorted defect densities, preparation times, and defect discovery rates. Inspectors who are rated on how many defects they find will report many defects, even if it means debating whether every small issue truly is a defect. Authors whose performance evaluation depends on how many defects inspectors find in their products will avoid inspections, fudge the data, or spend excessive time perfecting a product before inspecting it.

Your Bottom Line
I don't know how many defects your inspectors will find. However, many organizations have saved considerable effort through software inspections, which provides an excellent counter-argument to resisters who fear that inspections will slow the project down. The ROI only has to be a little higher than 1.0 to make inspections worth doing.

About the author

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.