| Artifact: Iteration Plan |
 |
 |
|
The main objectives of the iteration plan is to provide the team with one central place for information regarding iteration objectives, detailed plan with task assignments, and evaluation results. This artifact also helps the team to monitor the progress of the iteration and keeps the results of the iteration assessment that may be usefull for improving the next one. |
| Fulfilled Slots | ||
|---|---|---|
| Roles | Responsible: | Modified By: |
| Tasks | Input To:
| Output From: |
| Main Description | This artifact captures the key milestones of an iteration, showing start and end dates, intermediate milestones, synchronization points with other teams, demos, and so on. This artifact is also used to capture issues that need to be solved during the iteration. You should list a few objectives for the iteration, which will help guide you throughout the iteration and also assess at the end if those objectives have been achieved. The task assignments for an iteration are a subset of all tasks on the Artifact: Work Items List. Therefore, the iteration plan ideally references those work items. The evaluation criteria and iteration assessment information is captured in this artifact, so results and actions from assessments can be communicated. |
|---|
| Templates | |
|---|---|
| Reports | |
| Examples |
Work items assigned to an iteration do not necessarily have the same priority. When selecting work items from the Work Items List, the iteration plan may end up having work items with different priorities (for example, you assign the remaining high priority work items, plus a few mid priority ones from the Work Items List). No matter what previous priorities the work items had, when assigned to an iteration the team has to make sure they are able to develop what has been assigned to the iteration, and deciding on what to develop first (or even develop things in parallel) on an iteration will vary from project to project, from iteration to iteration. |
| Impact of not having | Without this artifact it will be difficult to assess the results of an iteration to determine whether the objectives have been met. |
|---|---|
| Reasons for not needing | This artifact is not required if no iterations are being performed or the scope of the project and each iteration is sufficiently small as to be handled informally amongst the team. |
| Representation Options | The level of detail/formality of the plan must be adapted to what you need to successfully meet these objectives. The plan could, for example, be captured on the following places:
|
| Concepts |
|---|
This program and the accompanying materials are made available under the |