Risk-Based Peer Reviews
While the benefits of formal inspections are well documented, in reality, many projects don’t have the resources to formally peer review every work product at that level of rigor. By analyzing the probability that a work product contains defects that will escape from development into the user environment and the potential impact of those defects, developers can make strategic, risk-based trade-offs between efficiency and effectiveness in their peer review processes. These decisions include the type(s) of peer review, the level of formality, the number of participants and peer review sufficiency needed for each work product.
This paper was presented by Linda Westfall at the 4th World Congress for Software Quality in Bethesda, Maryland.