Note: review doesn't contain explicit recommendation
Reviewed: January 2014
This is one of two books that I read recently on software reviews. I bought it partly because in my current job we do ‘code reviews’ and I wanted to get some ideas for participating in and running such reviews. None of my previous employers had ever done any sort of organized reviews. The other factor in my purchasing this book was my generally positive experience of reading two other books by Tom Gilb (namely Competitive Engineering and Principles of Software Engineering Management).
This book is fairly high up on the prescriptive scale. It describes Software Inspection (note the capital letters) as invented by Michael Fagan at IBM in the 70s. Other software inspection methods (no capitals) are described, but mostly in terms of how less efficient they are than the real thing.
The parts of the book are introduction (chapters 1–3), the grist of Software Inspection (chapters 4–7), more details on running the process and solving problems in the process (chapters 8–12). The next two parts of the book cover case studies (chapters 12–17) and the appendices, five of them, mostly templates for plans and reports to use in the inspection process.
Well, I wasn’t entirely convinced. Though there are a few success stories, I imagine that it is difficult to get buy-in for such a heavy method from management and engineering.