During the meeting, the attendees review the iteration evaluation criteria (as documented in the Iteration Plan), and
the results of the Assess Iteration task (as documented in the Iteration Assessment).
For each of the criteria the group should determine and agree whether or not the test and review results
demonstrated that the requirements of each criterion have been met.
If the requirements of a criterion have not been satisfied, the group should identify the corrective actions
required in order to achieve compliance.
At the end of the meeting, the reviewers should make their approval decision. If some of the iteration criteria have
not been satisfied, the group may still decide to accept the iteration and defer any corrective actions into the next
iteration. You might take this approach if the deficiencies were minor. However, you might also defer corrective
actions if the deficiencies were very significant (e.g. failure of a chosen technology infrastructure) and required a
significant change of approach in the project. In this situation you would initiate a new iteration to deal with the
The result of the Iteration Acceptance Review can be one of the following:
The customer representative and the project team agree that the deliverables for this iteration are
satisfactory, and the project should proceed to the next iteration.
Iteration Not Accepted
The evaluation criteria have not been achieved, and corrective actions are required before the work of the
iteration can be considered complete.
If the iteration is not accepted, the project team should schedule the corrective actions that have been identified,
and re-submit a revised Iteration Assessment for a follow-up review.