| <?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.5/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmi:id="_BcBR8KX5EdmvhNXG0Oc2uA" |
| name="iteration_plan,_0aQBEslgEdmt3adZL5Dmdw" guid="_BcBR8KX5EdmvhNXG0Oc2uA" changeDate="2007-05-19T05:44:15.738-0700" |
| version="1.0.0"> |
| <mainDescription><p>
 |
| 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.
 |
| </p>
 |
| <p>
 |
| The task assignments for an iteration is a subset of all tasks on the <a class="elementLinkWithType" href="./../../openup/workproducts/work_items_list_39D03CC8.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">Artifact: Work Items List</a>, therefore the iteration plan ideally references those work items.
 |
| </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). No matter what previous
 |
| 
 |
| priorities the work items had, when assigned to an iteration&nbsp;the team has to make sure they are able to develop
 |
| 
 |
| what has been&nbsp;assigned to the&nbsp;iteration, and deciding on&nbsp;what to&nbsp;develop first (or
 |
| 
 |
| even&nbsp;develop things in parallel) on an iteration will vary from project to project, from iteration to iteration.
 |
| 
 |
| </p></keyConsiderations> |
| <purpose><p>
 |
| 
 |
| Communicate the objectives, task assignment, and evaluation criteria for a given iteration.
 |
| 
 |
| </p></purpose> |
| <representationOptions><p>
 |
| 
 |
| 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:
 |
| 
 |
| </p>
 |
| 
 |
| <ul>
 |
| 
 |
| <li>
 |
| 
 |
| a whiteboard listing the objectives, task assignments and evaluation criteria;
 |
| 
 |
| </li>
 |
| 
 |
| <li>
 |
| 
 |
| a 1-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> |
