Do You Inspect?

IBM developed formal inspections of source code, config files, and other software artifacts in the 1970s. They're still used today with applications of most any size to eliminate defects and improve quality before the apps get tested. Formal inspections work well with development methods such as CMMI, RUP, TSP, agile, QFD, JAD, and Earned Value. They've been ranked the most efficient defect-removal process available. Because inspection participants tend to avoid making the kinds of errors that are found in formal inspections, they're also one of the top-ranked defect-prevention methods. Given their effectiveness, you'd expect formal inspections would be used on 100% of mission-critical software projects and on all of the critical sections of other software projects. But in reality, they're underutilized. One reason for this underutilization is that no vendor is out marketing formal inspections; that provides discouraging social commentary on how the software-engineering community learns new skills. No company owns formal inspections, and the method behind them is in the public domain.