In engineering, technical peer review is a type of engineering review. Technical peer reviews are a well defined review process for finding and fixing defects, conducted by a team of peers with assigned roles. Technical peer reviews are carried out by peers representing areas of life cycle affected by material being reviewed (usually limited to 6 or fewer people). Technical peer reviews are held within development phases, between milestone reviews, on completed products or completed portions of products.
A technical peer review may also be called a engineering peer review, a product peer review, a peer review/inspection or an inspection.
- 1 Overview
- 2 Roles of participants
- 3 Vested interest of reviewers
- 4 Distinction from other types of technical review
- 5 Management involvement
- 6 Detailed instructions
- 7 See also
- 8 References
The purpose of technical peer reviews is to remove defects as early as possible in the development process. By removing defects at their origin (e.g., requirements and design documents, test plans and procedures, software code, etc.), technical peer reviews prevent defects from propagating through multiple phases and work products, and reduce the overall amount of rework necessary on projects.
In addition, improved team efficiency is a side effect of technical peer reviews (e.g., by improving team communication, integrating the viewpoints of various engineering specialty disciplines, more quickly bringing new members up to speed, and educating project members about effective development practices).
In CMMI, peer reviews are used as a principal means of verification in the Verification process area and as an objective evaluation method in the Process and Product Quality Assurance process area. The results of technical peer reviews can be reported at milestone reviews. (See Milestone (project management).)
Roles of participants
Responsible for conducting the technical peer review process and collecting inspection data. Plays key role in all stages of the technical peer review process except rework. Required to perform several duties during a technical peer review in addition to inspector’s tasks.
Responsible for finding defects in work product from a general point of view, as well as defects that affect their area of expertise.
Provides information about work product during all stages of process. Responsible for correcting all major defects and any minor and trivial defects that cost and schedule permit. Performs duties of an inspector.
Guides team through work product during the technical peer review meeting. Reads or paraphrases work product in
detail. Performs duties of an inspector in addition to reader’s role.
Accurately records each defect found during inspection meeting on the Inspection Defect List. Performs duties of an inspector in addition to recorder’s role.
Vested interest of reviewers
There are two philosophies about the vested interest of the inspectors in the product under review. On one hand, project personnel who have a vested interest in the work product under review have the most knowledge of the product and are motivated to find and fix defects. On the other hand, personnel from outside the project
who do not have a vested interest in the work product bring objectivity and a fresh viewpoint to the technical peer review team.
Each inspector is invited to disclose vested interests to the rest of the technical peer review panel so the Moderator can exercise sound judgement in evaluating the inspector’s inputs.
Distinction from other types of technical review
Peer reviews are distinct from management reviews, which are conducted by management representatives rather than by colleagues, and for management and control purposes rather than for technical evaluation. They are also distinct from software audit reviews, which are conducted by personnel external to the project, to evaluate compliance with specifications, standards, contractual agreements, or other criteria.
A software peer review is a type of technical peer review. The IEEE defines formal structures, roles, and processes for software peer reviews.
Management representatives are typically not involved in the conduct of a peer review. This is especially true of line managers of the author or other participants in the review. A policy of encouraging management to stay out of peer reviews encourages the peer review team to concentrate on the product being reviewed and not on the people or personalities involved.
For detailed instructions on conducting a technical peer review/inspection, see NASA Systems Engineering Handbook, Appendix N.
- Design review – encompasses preliminary, critical and other design reviews