These are a strict and formal form of review. The point is to obtain defects, collect data, and communicate development documents.
Roles:
- Moderator
- Ensures that inspection procedures are followed
- Verifies the work product’s readiness for inspection
- Verifies that the entry criteria are met
- Assembles an effective inspection team
- Keeps the inspection meeting on track
- Verifies that the exit criteria are met
- Comes from outside the project team but is still a peer
- Recorder
- Documents all defects that arise from the inspection meeting in an inspection defect list
- Not just a procedural task, this requires technical knowledge
- Reviewer
- Analyzes and detects defects in the work product
- All participants play that role
- Depending on reviewed document, consider a representative each from requirements, test, design, and implementation teams
- Reader
- Leads the inspection team through the inspection meeting by reading aloud small logical units
- Producer
- Work product author
- Responsible for correcting any defects that are found
- Planning
- Identify work product, determine whether the product to be inspected meets the entry criteria, select the team, assign roles, prepare and distribute the inspection forms and materials, set the inspection schedule, and determine whether to hold an overview
- Overview
- Optional phase where team members who are unfamiliar with the work product to be inspected receive orientation
- Preparation
- Key stage in which members of the inspection team inspect the work individually looking for defects in the work product
- Most of the defects are found during this step, not during the inspection meeting
- Inspection meeting
- Inspection team members meet to find, categorize, and record possible defects in the work product
- No resolution of defects is attempted but action items are assigned
- Beware of team size and long, detailed presentations
- Third Hour
- This is optional
- This is used for discussion, possible solutions, closure of open issues raised during the inspection meeting
- Rework
- The work product is revised by the author to correct defects found during the inspection
- Follow up
- Meeting between the moderator and author to determine if defects found during the inspection meeting have been corrected and to ensure that we have no regressed
- Final inspection data is collected and summarized and the inspection is officially closed
Note
Coverage if 5-15% of document pages represents a significant contribution to quality.
We want to include sections with complicated logic, critical sections and sections that deal with no environments
We don’t want to include straightforward sections, sections similar to ones that have already been reviewed, sections not expected to affect functionality if faulty, or reused sections.