| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="_BcBR8KX5EdmvhNXG0Oc2uA" name="iteration_plan,_0aQBEslgEdmt3adZL5Dmdw" guid="_BcBR8KX5EdmvhNXG0Oc2uA" changeDate="2008-08-18T04:06:22.000-0700" version="7.2.0"> |
| <mainDescription><p>
 |
| 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.
 |
| </p>
 |
| <p>
 |
| You should list a few objectives for the iteration, which will help guide you throughout the iteration. Also, assess at
 |
| the end if those objectives have been achieved.
 |
| </p>
 |
| <p>
 |
| The task assignments for an iteration are a subset of all tasks on the <a class="elementLinkWithType"
 |
| href="./../../core.mgmt.common.extend_supp/workproducts/work_items_list_39D03CC8.html"
 |
| guid="_rGNWsCbSEdqh1LYUOGRh2A">Artifact: Work Items List</a>. Therefore, the iteration plan ideally references those
 |
| work items.
 |
| </p>
 |
| <p>
 |
| The evaluation criteria and iteration assessment information are captured in this artifact, so that you can communicate
 |
| results and actions from assessments.
 |
| </p></mainDescription> |
| <keyConsiderations><p>
 |
| 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). Once work items have been
 |
| assigned to the iteration, the team ensures that they can complete all work, regardless of original work item
 |
| priorities. Deciding what to develop first on an iteration will vary across projects and iterations.
 |
| </p></keyConsiderations> |
| <purpose><p>
 |
| The main objectives of the iteration plan are to provide the team with the following:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| One central place for information regarding iteration objectives
 |
| </li>
 |
| <li>
 |
| A detailed plan with task assignments
 |
| </li>
 |
| <li>
 |
| Evaluation results
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| This artifact also helps the team to monitor the progress of the iteration, and keeps the results of the iteration
 |
| assessment that may be useful for improving the next one.
 |
| </p></purpose> |
| <impactOfNotHaving>Without this artifact, it will be difficult to assess the results of an iteration to determine whether or not the
 |
| objectives have been met.</impactOfNotHaving> |
| <reasonsForNotNeeding>This artifact is not required if no iterations are being performed, or if the scope of the project and each iteration is
 |
| sufficiently small as to be handled informally amongst the team.</reasonsForNotNeeding> |
| <representationOptions><p>
 |
| The level of detail or formality of the plan must be adapted to what you need in order to meet these objectives
 |
| successfully. The plan could, for example, be captured on the following places:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| A whiteboard listing the objectives, task assignments, and evaluation criteria
 |
| </li>
 |
| <li>
 |
| A one-page document listing the objectives and evaluation criteria of the iteration, as well as referencing the
 |
| Work Items List for assignments for that iteration
 |
| </li>
 |
| <li>
 |
| A more complex document, supported by a Gantt or Pert chart in a project planning tool
 |
| </li>
 |
| </ul></representationOptions> |
| </org.eclipse.epf.uma:ArtifactDescription> |
