A History of Software Inspections

  • Michael Fagan


Inspections are now 30 years old and they continue to improve software quality and maintainability reduce time to delivery and lower development costs!

The concept of finding defects as early as possible in the software development process to save time, effort, and money seems intuitive in 2001. Many companies employ variations of the software inspections that I created as part of their development process in order to do just that. However, even 30 years after its creation, it is often not well understood and more often, poorly executed — yielding results that are positive, but well below their potential.

This paper will explore the history and creation of the software inspection process by Michael Fagan. Some readers will find a great deal of similarity between the development environment that led to the creation of this process and the one in which they are currently involved. The process itself has proven to be as effective and necessary today as when it was first created.


Work Product Inspection Process Capability Maturity ModeL Exit Criterion Legacy Product 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Copyright information

© Springer-Verlag Berlin Heidelberg 2002

Authors and Affiliations

  • Michael Fagan
    • 1
  1. 1.Michael Fagan AssociatesPalto AltoUK

Personalised recommendations