Purpose

  • To approve the criteria that will be used to determine if the work completed during an iteration meets the iteration's objectives.

Role:  Management Reviewer 
Frequency: Once per iteration 
Steps

Input Artifacts: 

 

Resulting Artifacts: 

 

Tool Mentors:   

Workflow Details:   

The Iteration Evaluation Criteria Review is a formal review of the tests and reviews that will be used to demonstrate to the customer that the objectives for an iteration have been met. This is an important review because it ensures that the project team and customer have consistent expectations for how success in the work of the iteration will be measured.

 

Schedule Iteration Evaluation Criteria Review Meeting

To top of page

The Iteration Evaluation Review meeting is a meeting between a customer representative and the project's management team (the project manager, plus the team leads for the various functional areas of the project team). Representative(s) of the Project Review Authority may also be involved.

Once the attendees of the meeting have been identified, set a date/time for the meeting to take place. It is important that you provide sufficient lead time to allow the participants to review the materials that will be used as the basis for the approval decision.

 

Distribute Meeting Materials

To top of page

Prior to the meeting, distribute the review materials to the reviewers. Make sure these materials are sent out sufficiently in advance of the meeting to allow the reviewers adequate time to review them. A minimum set of artifacts that should be presented for review is:

  • Iteration Plan
  • Test Plan

 

Conduct Iteration Evaluation Criteria Review Meeting

To top of page

During the meeting, the reviewers assess the proposed program of tests and reviews defined in the Test Plan that will be used to determine if the iteration's objectives have been met. During the meeting, make sure that:

  • Both the customer representative and the project team have a clear understanding of which project artifacts will be delivered at the end of the iteration
  • Both the customer representative and the project team have a clear understanding of which reviews, tests and demonstrations will be carried out, and how the results will be interpreted
  • That reviews and tests are planned covering each of the objectives defined for the iteration in the Iteration Plan

At the end of the meeting, the reviewers should make their approval decision. The result can be one of the following:

Criteria Approved   The customer representative and the project team agree that the evaluation criteria are satisfactory 
Criteria Rejected   The evaluation criteria are not acceptable. This could be due to incomplete coverage of iteration objectives, or tests/reviews that do not properly assess whether particular objectives are met. 

If the criteria are rejected, the project team should address the identified deficiencies and re-submit revised iteration evaluation criteria for a follow-up review.

 

Record Decision

To top of page

At the end of the meeting, a Review Record is completed capturing any important discussions or action items, and recording the result of the Iteration Evaluation Criteria Review. If the result was "criteria rejected" a follow-up Iteration Evaluation Criteria Review Meeting should be scheduled for a later date.



Rational Unified Process  

2003.06.13