Difference between Inspections and Walkthroughs.
| Inspection | Walkthrough |
| Formal | Informal |
| Initiated by the project team | Initiated by the author |
| Planned meeting with fixed roles assigned to all the members involved | Unplanned. |
| Reader reads the product code. Everyone inspects it and comes up with defects. | Author reads the product code and his team mate comes up with defects or suggestions |
| Recorder records the defects | Author makes a note of defects and suggestions offered by team mate |
| Moderator has a role in making sure that the discussions proceed on the productive lines | Informal, so there is no moderator |
Inspection: is used to verify the compliance of the product with specified standards and requirements. It is done by examining, comparing the product with the designs, code, artefacts and any other documentation available. It needs proper planning and overviews are done on the planning to ensure that inspections are held properly. Lots of preparations are needed, meetings are held to do inspections and then on the basis of the feedback of the inspection, rework is done.
Inspection is deserving method with careful consideration of an organization, which concerns about the quality of the product. The process is being done by the quality control department.
Inspection is a disciplined practice for correcting defects in software artifacts.
Walkthroughs: Author presents their developed artifact to an audience of peers. Peers question and comment on the artifact to identify as many defects as possible. It involves no prior preparation by the audience. Usually involves minimal documentation of either the process or any arising issues. Defect tracking in walkthroughs is inconsistent.
A walk through is an evaluation process which is an informal meeting, which does not require preparation.
The product is described by the produced and queries for the comments of participants. The results are the information to the participants about the product instead of correcting it.
