Management preparation: Responsible management make sure that the review will be appropriately resourced with personnel, time, materials and tools, and will be performed according to policies, standards or other pertinent requirements. 2. Planning the review: The review leader recognizes or verifies the goals of the review, organises a group of customers and guarantees that the team is geared up with all essential resources for performing the evaluation.
Introduction of review treatments: The evaluation leader, or some other certified individual, ensures (at a conference if required) that all customers comprehend the evaluation goals, the evaluation procedures, the products offered to them and the treatments for conducting the evaluation. 4. [Specific] Preparation: The customers separately prepare for group assessment of the work under review, by analyzing it carefully for "abnormalities" (possible defects), the nature of which will differ with the type of evaluation and its objectives.
[Group] Evaluation: The customers satisfy at a scheduled time to pool the outcomes of their preparation activity and get to an agreement concerning the status of the file (or activity) being evaluated. 6. Rework/follow-up: The author of the work item (or other appointed individual) undertakes whatever actions are required to repair problems or otherwise please the requirements accepted at the examination meeting.
7. [Exit examination]: The evaluation leader verifies that all activities essential for effective review have been achieved which all outputs proper to the kind of review have actually been settled. Value of evaluations [modify] The most obvious value of software evaluations (particularly official reviews) is that they can determine concerns earlier and more cheaply than they would be determined by screening or by field usage (the "defect detection process") []
This is especially the case for peer evaluations if they are performed early and frequently, on samples of work, instead of waiting up until the work has actually been completed. Early and Did you see this? of little work samples can identify methodical mistakes in the author's work procedures, which can be remedied before additional malfunctioning work is done.
As a basic concept, the earlier a technical file is produced, the higher will be the effect of its flaws on any downstream activities and their work items. Appropriately, greatest value will accumulate from early reviews of documents such as marketing strategies, contracts, task strategies and schedules and requirements specs.