operations A typical Fagan inspection consists of the following operations: Planning Preparation of materials Arranging of participants Arranging of meeting place Overview Group education of participants on the materials under review Assignment of roles Preparation The participants review the item to be inspected and supporting material to prepare for the meeting noting any questions or possible defects The participants prepare their roles Inspection meeting Actual finding of defect Rework Rework is the step in software inspection in which the defects found during the inspection meeting are resolved by the author, designer or programmer. On the basis of the list of defects the low-level document is corrected until the requirements in the high-level document are met. Follow-up In the follow-up phase of software inspections all defects found in the inspection meeting should be corrected (as they have been fixed in the rework phase). The moderator is responsible for verifying that this is indeed the case. They should verify that all defects are fixed and no new defects are inserted while trying to fix the initial defects. It is crucial that all defects be corrected, as the costs of fixing them in a later phase of the project can be 10 to 100 times higher compared to the current costs. Follow-up In the follow-up phase of a Fagan inspection, defects fixed in the rework phase should be verified. The moderator is usually responsible for verifying rework. Sometimes fixed work can be accepted without being verified, such as when the defect was trivial. In non-trivial cases, a full re-inspection is performed by the inspection team (not only the moderator). If verification fails, go back to the rework process. Roles The inspection process is normally performed by members of the same team that is implementing the project. The participants fulfill different roles within the inspection process: Author/Designer/Coder: the person who wrote the low-level document Reader: paraphrases the low-level document Reviewers: reviews the low-level document from a testing standpoint Moderator: responsible for the inspection session, functions as a coach Benefits and results By using inspections the number of errors in the final product can significantly decrease, creating a higher quality product. In the future the team will even be able to avoid errors as the inspection sessions give them insight into the most frequently made errors in both design and coding providing avoidance of error at the root of their occurrence. By continuously improving the