A review is any activity in which a work product is distributed to reviewers who examine it and give feedback. Reviews are useful not only for finding and eliminating defects, but also for gaining consensus among the project team, securing approval from stakeholders, and aiding in professional development for team members. Reviews help teams find defects soon after they are injected making them cost less to fix than they would cost if they were found in test. All work products in a software project should be either reviewed or tested. Software requirements specifications, schedules, design documents, code, test plans, test cases, and defect. | REVIEWS Applied Software Project Management WHEN ARE REVIEWS NEEDED? A review is any activity in which a work product is distributed to reviewers who examine it and give feedback. Reviews are useful not only for finding and eliminating defects, but also for gaining consensus among the project team, securing approval from stakeholders, and aiding in professional development for team members. Reviews help teams find defects soon after they are injected making them cost less to fix than they would cost if they were found in test. All work products in a software project should be either reviewed or tested. Software requirements specifications, schedules, design documents, code, test plans, test cases, and defect reports should all be reviewed. TYPES OF REVIEW: INSPECTIONS Inspections are moderated meetings in which reviewers list all issues and defects they have found in the document and log them so that they can be addressed by the author. The goal of the inspection is to repair all of the defects so that everyone on the inspection team can approve the work product. Commonly inspected work products include software requirements specifications and test plans. TYPES OF REVIEW: INSPECTIONS Running an inspection meeting: A work product is selected for review and a team is gathered for an inspection meeting to review the work product. A moderator is chosen to moderate the meeting. Each inspector prepares for the meeting by reading the work product and noting each defect. In an inspection, a defect is any part of the work product that will keep an inspector from approving it. Discussion is focused on each defect, and coming up with a specific resolution. It’s the job of the inspection team to do more than just identify the problems; they must also come up with the solutions. The moderator compiles all of the defect resolutions into an inspection log CHOOSE THE INSPECTION TEAM The job of the inspection team is to work with the author of the . | REVIEWS Applied Software Project Management WHEN ARE REVIEWS NEEDED? A review is any activity in which a work product is distributed to reviewers who examine it and give feedback. Reviews are useful not only for finding and eliminating defects, but also for gaining consensus among the project team, securing approval from stakeholders, and aiding in professional development for team members. Reviews help teams find defects soon after they are injected making them cost less to fix than they would cost if they were found in test. All work products in a software project should be either reviewed or tested. Software requirements specifications, schedules, design documents, code, test plans, test cases, and defect reports should all be reviewed. TYPES OF REVIEW: INSPECTIONS Inspections are moderated meetings in which reviewers list all issues and defects they have found in the document and log them so that they can be addressed by the author. The goal of the inspection is .
