Artifact: Review Record
|
|
A Review Record is created to capture the results of the review of a project artifact. |
| Worker: | Any Reviewer (e.g. Requirements Reviewer) |
| More Information: | See Work Guidelines: Reviews |
Purpose 
A Review Record is a form document that is filled out for each review. It is created as a control document to manage the execution of the review of project artifacts. It is issued to the participants in the review to initiate the review process, and is used to capture the results and any action items arising from the review meeting. It forms an auditable record of the review and its conclusions.
Brief Outline
1. Project Identification and Type of Review
Identify the project and the type of review (e.g. code inspection, requirements traceability review, PRA project review, project planning review)
2. Artifact(s) Reviewed and Objectives of the Review
List the artifact(s) that will be the subject of this review. Describe the objectives of the review.
3. Review Participants
List the individuals who will participate in the review and their roles during the meeting (e.g. moderator, note-taker, reviewer, author)
4. Schedule & Location
Identify the schedule for the review. Include the date, time and place of the review meeting, and also a publication schedule for the review artifacts if they are not attached to the review record.
5. Problems Identified and Recommendations for Resolution
List any problems identified during the review. Reviewers may identify:
- Problems with the review artifact(s) that require correction (i.e. defects)
- Project problems whose symptoms are identified from the review artifact(s)
- Product problems whose symptoms are identified from the review artifact(s)
The review team may make recommendations on problem resolution.
6. Action Item Status
List any action items resulting from the review; these should be listed with an identified owner (responsible for action completion) and target date. These will typically be action items intended to correct the problems identified. Action items may include:
| Continue work: | Artifact is not considered complete and development work should continue |
| Raise Work Order(s): | If problem requires new work to be planned but doesn't change a baselined artifact |
| Raise Change Request(s): | If problem requires change to baselined artifacts |
There may exist action items from previous reviews of this artifact, and these should be listed with their status (e.g. open/closed), owner and target or closure date.
7. Issues for Consideration by the Project Manager
Certain problems or anomalies may be discovered for which a course of action cannot be agreed by the review team, and which need to be escalated for resolution.
8. Follow-up Review
Describes the review team's recommendations for follow-up (e.g. whether another review is necessary) and what, if any, additional information or data is needed.
9. Record of Effort
Captures the effort-hours spent in review preparation and conduct.
Timing
Review activities are integral to the Rational Unified Process and occur throughout the development project. The major reviews are held as scheduled in the Review and Audit Plan section of the Quality Assurance Plan.
Responsibility
The worker reviewer (e.g. Requirements Reviewer) is responsible for the review record, and follow-up on action items and problem resolution.
Tailoring
This is a form artifact which is used to capture the results of a review - all projects should use it, the level of formality will depend on how formal the relationship is between customer and developer, or how formal the developer's own organization is with regard to process compliance. For example, the contract may say that review records are auditable.
Additional Information
For more information on reviews see Guidelines:
Reviews
