This is a listing of sources for best practices for software inspections.
Formal Inspections - The practice of conducting formal Inspections on requirements, architecture, designs at all levels (particularly detailed design), on code prior to unit test, and on test plans, to assess the quality of all baselined artifacts prior to release for project use.
Improving Quality Through Software Inspections - This is an article by Karl E. Weigers from the CAI-sponsored IT Metrics and Productivity Institute dated 29 September 2008. This is a description from the CAI web site:
"Software inspections and their cousins, reviews and walkthroughs, are proven techniques for reducing the number of defects in a program before it goes out the door. If you are in an organization of two or more people, some kind of inspection activity should be a part of your standard software development process."
Software Assessments, Benchmarks, and Best Practices - Written by Capers Jones, Addison-Wesley Pub Co; 1st edition (April 28, 2000), this book explores the methodologies used by businesses for software development, while software benchmarking collects quantitative data on such topics as schedules and costs. This guide combines assessments and benchmark studies to improve software analysis, and identifies best and worst practices of software development.
A reviewer comments: "This is a handy book with a summary and compendium of papers on inspections. The books traces the industry experience with inspections as mirrored in the technical papers published on the subject. For those interested in an important best practice, this is an invaluable resource that is complementary to the standard books on the subject. I am particularly interested in the inspection of natural language requirements documents and found the papers in this area valuable."
SPMN Sixteen Critical Software Practices - The Software Program Managers Network (SPMN) was established in 1992 by the Assistant Secretary of the Navy to identify proven industry and government software best practices and convey these practices to managers of large-scale DoD system acquisition programs. The SPMN 16 Critical Software PracticesTM specifically address underlying cost and schedule drivers that have caused many software intensive systems to be delivered over budget, behind schedule and with significant performance shortfalls.