A formal technical review (FTR) is a software quality control activity performed by software engineers (and others) The objectives of an FTR are: To uncover errors in function, logic, or implementation; for any representation of the software To verify that the software under review meets its requirements To ensure that the software has been represented according to predefined standards To achieve software that is developed in a uniform manner To make projects more manageable During the FTR, a reviewer (the recorder) actively records all issues that have been raised These are summarized at the end of the review meeting, and a reviewed issues list is produced In addition, a formal technical review summary report is completed Review Guidelines Guidelines for conducting formal technical reviews must be established in advance, distributed to all reviewers, agreed upon & then followed Review the product, not the producer Set an agenda and maintain it Limit debate and denial Speak problem areas, but don't attempt to solve every problem noted Take written notes Conduct meaningful training for all reviewers Limit the number of participants and insist upon advance preparation Develop a checklist for each product that is likely to be reviewed Allocate resources and schedule time for FTRs Review your early reviews
