Inspections are the most formal kind of technical review, and they have been found to be extremely effective in detecting defects throughout a project. Developers are trained in the use of inspection techniques and play specific roles during the inspection process. After the meeting, the moderator produces an inspection report that describes each defect and indicates what will be done about it. Throughout the inspection process you gather data about defects, hours spent correcting defects, and hours spent on inspections so that you can analyze the effectiveness of your software-development process and improve it. Comment on Technical Reviews Technical reviews are a useful and important supplement to testing.
Reviews find defects earlier, which saves time and is good for the schedule.
And reviews serve as a time when developers share their knowledge of best practices with each other, which increases their rapid-development capability over time. Technical reviews are thus a critical component of any development effort that aims to achieve the shortest possible schedule. The Other Kind of Quality I mentioned at the beginning of the article that there were two kinds of quality. Unlike the low-defect kind of quality, attention to this kind of quality tends to lengthen the development schedule. Summary When a software product has too many defects, developers spend more time fixing the software than they spend writing it in the first place.