Deliverable Review

Checklist and Guidelines

Confidentiality Statement
This <document title> along with all attachments hereto shall be considered <company>’s
Proprietary/Confidential Information
 
 
gantthead.com Deliverable Review Checklist and Guidelines

Conducting the Review Session

Guidelines such as the following for conducting formal deliverable review sessions must
be established in advance, distributed to all reviewers, agreed upon, and followed.
Check your review session against this list at the beginning and end as well as at
periodic points during the session to ensure that you are adhering to these principles.

 Limit the number of participants to as few as necessary, with no more than five
reviewers on the Review Team.

 The duration of the review meeting should be less than 2 hours. Divide the
review into multiple sessions, if it is necessary to take more time.

 All members of the review team should prepare in advance for the meeting by
examining the deliverable to be discussed.

 The Project Manager and Deliverable Author should not interfere with the
assessments of the review team or defend their work during the review meeting.
They should be passive participants and serve only as witnesses to the review and
to clarify misunderstandings or answer questions.

 Review the product, not the producer. The tone of the meeting should be loose
and constructive. The Review Team Leader should conduct the meeting in a
manner that ensures that the proper tone and attitude are maintained.

 Articulate problems, but do not attempt to solve them in the review session.

 Allow every reviewer to present his/her findings. The review team should discuss
each item and come to a consensus on it.

 Record the consensus on each finding in such a way that every reviewer can see
the notes and the Deliverable Author will be able to understand and apply them
during the rework process.

 Rank each finding as a critical error (usability of the product impossible, must be
corrected before release) or non-critical error (recommend change before release,
but not essential).

 Note positive aspects of the deliverable, as well as those areas in need of

change. Deliverable Author should be commended where the work is exceptional
and should be repeated in approach to the development of other deliverables.

 At the end of the review, all reviewers must decide whether to (a) accept the
product without further modification, (b) accept the product provisionally (minor errors
have been encountered and must be corrected, but no additional review will be
required), or (c) reject the product due to significant errors (once corrected, another
review must be performed).

©2007 gantthead.com 2
gantthead.com Deliverable Review Checklist and Guidelines

Review Team Lead should:

Publish the Review Report. It should contain the following information:

 Summary:

o Date, time and place of review session

o Preparation time spent
o List of documents used
o Summary of conclusions and rationale for conclusions
o Name and signature of each review team participant
 All instances of recommended changes to the deliverable:

o Identify location of each problem within the deliverable

o Describe change necessary
o Provide rationale for change
o Rank change as critical or non-critical
 Notable instances of exceptional work, for which Author should be commended
and encouraged to repeat on approach to other deliverables

After changes have been made, Review Team Lead should:

 Re-examine the modified deliverable and authorize Project Manager to release it,
in the case where only minor changes were needed.

 Reassemble the original review team and review the deliverable again, in the
case where significant changes were needed.

Project Manager should:

 Decide whether to rework or to release the deliverable, based on the review
results.

 Allocate resources and determine schedules for rework, if rework is to follow.

 Inform review team about the reasons for releasing deliverable without rework, if
rework was recommended.

Deliverable Author should:

 Modify deliverable based on the review findings and the marked review copies,
adhering closely if not exactly to what the review team recommended.

 Publish a list of modifications to the deliverable, with references to the associated

review items.

©2007 gantthead.com 3