Software Reviews and Audits: A How To Guide for Project Staff: 1 (Software Engineering Project Management)

Every software project that has ever careened off the rails, blown its budget, or shipped a defective product to an embarrassed client had one thing in common: insufficient review. The uncomfortable truth about software development is that defects found late cost exponentially more to fix than defects found early — and most defects are found late because the teams involved either skipped the review process entirely, or conducted it badly.

Software Reviews & Audits: A How To Guide for Project Staff is the book that fixes that problem. Written by David Tuffley and grounded in the authoritative framework of IEEE Standard 1028, it is a comprehensive, practical, and immediately actionable guide to the full suite of review and audit activities that any serious software project demands. This is not a book of vague principles. It is a handbook — the kind you keep on your desk and consult before you chair a review meeting, not the kind you put on a shelf and reference in a footnote.

The book covers five distinct review types, each serving a different purpose at a different point in the project lifecycle. Management reviews assess whether a project is tracking to plan — covering schedule, resources, budget, and risk at the phase level. Technical reviews bring a formal team to bear on specific documents or software modules, verifying that content is correct, standards are met, and defects are identified and logged before they become embedded problems. Walkthroughs offer a more collaborative, improvement-focused approach, encouraging teams to explore alternatives and catch issues while development is still fluid. Audits provide the independent, objective evidence of compliance that clients, regulators, and quality managers require. And inspections — the most rigorous mechanism in the toolkit — apply systematic formal analysis to completed work, identifying defects with the precision that informal review simply cannot match.

What distinguishes this guide is its granularity. For each review type, Tuffley walks the reader through initiation, staffing, notification, input requirements, conduct, agenda structure, exit decisions, and follow-up actions. Nothing is assumed; nothing is glossed over. You will know exactly who needs to be in the room, how much notice they require, what material must be circulated beforehand, and what the three possible exit decisions mean and how to apply them. The roles — review leader, recorder, reviewer, author — are defined with a clarity that eliminates the ambiguity that so often causes reviews to drift into unproductive territory.

The book also addresses the practical texture of review management: how to maintain a review status register, when to conduct partial rather than complete reviews, what constitutes a major defect versus a minor one, and how to write a review summary report that actually drives action rather than gathering dust.

Particularly valuable is the book's treatment of the audit process — the most externally facing of all the review types. Tuffley provides a complete audit plan template covering background, objectives, scope, definitions, project processes, module identification, reporting requirements, distribution, follow-up, objective audit criteria, and budget. It is a framework that an audit leader could pick up and use immediately.

Appendices covering issue types, classification schemes, and severity ratings round out a reference that leaves nothing to chance.

If you manage software projects, develop software, work in quality assurance, or carry any responsibility for the integrity of a software deliverable, this book belongs in your professional library. It will not merely improve your review process — it will give you one worth having.