Artifact: Iteration Assessment
 Iteration Assessment |
The iteration assessment captures the result of an iteration, the degree to which the evaluation criteria were met, and lessons learned and changes to be done. |
| Worker: | Project Manager |
| Template: | Word template |
Purpose
Each iteration is concluded by an iteration assessment where the development organization makes a pause and reflects on what has happened, what was achieved or not, and why, and the lessons learned.
Brief Outline
1. Objectives
A brief description of the purpose of the Iteration Assessment.
2. Scope
A brief description of what the Iteration Assessment applies to; what is affected or influenced by this document.
3. References
A list of related or referenced documents.
4. Iteration Objectives Reached
Acknowledge the success you reached in the iteration.
5. Adherence to Plan
How did the iteration run according to plan? How well was the budget met?
6. Use Cases and Scenarios Implemented
List the use cases and scenarios that were implemented.
7. Results Relative to Evaluation Criteria
Assess the results of the iteration relative to the evaluation criteria that were established for the iteration plan: functionality, performance, capacity, quality measures.
8. Test Results
Refer to test results.
9. External Changes Occurred
For example, changes in requirements, new user’s need, competitor’s plan.
10. Rework Required
Identify problem areas that need to be reworked in upcoming iterations.
Timing
Iteration assessments are created at the end of each iteration. They are not updated.
Responsibility
The Worker: Project Manager is responsible for the iteration assessment.
Tailoring
Iteration assessments are created at the end of each iteration. They are not updated.
Additional Information
This assessment is a critical step in an iteration and should not be skipped. If iteration assessment is not done properly, many of the benefits of an iterative approach will be lost.
Note that sometimes the right thing to do in this step is to revise the evaluation criteria rather than reworking the system. Sometimes the benefit of the iteration is in revealing that a particular requirement is not important, or too expensive to implement, or creates an unmaintainable architecture. In these cases, a cost/benefit analysis must be done and a business decision must be made.
Metrics must be used as the basis of this assessment.
