Artifacts > Project Management Artifact Set > Review Record


Review Record

A Review Record is created to capture the results of the review of a project artifact.
Role: Reviewer
More Information: See Work Guidelines: Reviews

Output from Activities:






Templates, Case-Study, Report.. To top of page

The Word template can be bought through a template package. Case studies and reports are freely available in the table below.

Word
Template
Case
Study
Report
---

Purpose To top of page

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 To top of page

1. Project Identification and Type of Review

Identify the project and the type of review; for example, code inspection, requirements traceability review, PRA project review, project planning review.

2. Artifacts Reviewed and Objectives of the Review

List the artifacts that will be the subject of this review and describe the objectives of the review.

3. Review Participants

List the individuals who will participate in the review and their roles during the meeting; for example, 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 artifacts that require correction; that is, defects
  • Project problems whose symptoms are identified from the review artifacts
  • Product problems whose symptoms are identified from the review artifacts

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 Orders:
If problem requires new work to be planned but doesn't change a baselined artifact
Raise Change Requests:
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 (for example, 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 on by the review team, and which needs to be escalated for resolution.

8. Follow-up Review

Describes the review team's recommendations for follow-up (for example, 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 To top of page

Review activities are integral to the Unified Process for EDUcation and occur throughout the development project.

Responsibility To top of page

The role of Reviewer is responsible for the review record, and follow-up on action items and problem resolution.

Tailoring To top of page

This is a form artifact used to capture the results of a review—all projects should use it, and 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 To top of page

For more information on reviews, see Guidelines: Reviews.