| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:TaskDescription 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="_Wk7noKe1EdmGSrcKGOYDGg" |
| name="plan_iteration,_0keUEMlgEdmt3adZL5Dmdw" guid="_Wk7noKe1EdmGSrcKGOYDGg" changeDate="2007-04-30T14:45:54.184-0700" |
| version="1.0.0"> |
| <mainDescription><p>
 |
| 
 |
| 
 |
| During project planning, iterations are identified but the estimates have an acceptable uncertainty due to the lack of
 |
| 
 |
| 
 |
| detail at the project inception. This task is repeated for each iteration within a release. It allows the team to
 |
| 
 |
| 
 |
| increase the accuracy of the estimates for one iteration, as more detail is known along the project. The&nbsp;<a class="elementLink" href="./../../openup/roles/project_manager_E657F936.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">Project Manager</a>&nbsp;has the responsibility of ensuring that the team commits to a
 |
| 
 |
| 
 |
| reasonable amount&nbsp;of work&nbsp; for the iteration, based on team performance from previous iterations.
 |
| 
 |
| 
 |
| </p></mainDescription> |
| <sections xmi:id="_59g8cBs_EdyFhYaJcRUltg" name="Prioritize Work Items List" guid="_59g8cBs_EdyFhYaJcRUltg"> |
| <sectionDescription>The WIL should be prioritized before you plan the next iteration.&nbsp; Consider what has changed since the last iteration
 |
| plan such as new change requests, shifting priorities of your stakeholders or new risks that have been encountered.</sectionDescription> |
| </sections> |
| <sections xmi:id="_mMmDcPC9EdueN4Zcx2QxHQ" name="Refine project plan" guid="_mMmDcPC9EdueN4Zcx2QxHQ"> |
| <sectionDescription>Depending on the results of the previous iteration assessment&nbsp;the&nbsp;<a class="elementLink" href="./../../openup/roles/project_manager_E657F936.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">Project Manager</a>&nbsp;may need to
 |
| 
 |
| revise the&nbsp;<a class="elementLink" href="./../../openup/workproducts/project_plan_1CDBB7E4.html" guid="_0a6vcMlgEdmt3adZL5Dmdw">Project Plan</a>. Necessary changes can encompass the need to acquire new resources, to
 |
| 
 |
| absorb an unplanned effort increase, or to implement a specific change request.&nbsp;If a change affects defined project
 |
| 
 |
| milestones, the <a class="elementLink" href="./../../openup/roles/project_manager_E657F936.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">Project Manager</a> should consult with the stakeholders before committing to them.</sectionDescription> |
| </sections> |
| <sections xmi:id="_CtKCMMBHEdqSgKaj2SZBmg" name="Define the iteration objectives" |
| guid="_CtKCMMBHEdqSgKaj2SZBmg"> |
| <sectionDescription><p>
 |
| 
 |
| 
 |
| Work with the team to refine the iteration objectives found in the&nbsp;<a class="elementLink" href="./../../openup/workproducts/project_plan_1CDBB7E4.html" guid="_0a6vcMlgEdmt3adZL5Dmdw">Project Plan</a>, and document them in the <a class="elementLink" href="./../../openup/workproducts/iteration_plan_B46FED39.html" guid="_0aQBEslgEdmt3adZL5Dmdw">Iteration Plan</a>&nbsp;in order to provide high-level direction to what should be
 |
| 
 |
| 
 |
| targeted for the iteration. The objectives should be driven based on&nbsp;<a class="elementLink" href="./../../openup/roles/stakeholder_9FFD4106.html" guid="_dTa6gMAYEdqX-s4mWhkyqQ">Stakeholder</a>&nbsp;priorities, and will be revised as the iteration plan is finalized.
 |
| 
 |
| 
 |
| Those objectives are usually defined as high-level capabilities or scenarios that need to be implemented and tested
 |
| 
 |
| 
 |
| during the iteration in order to deliver increased value to the customer.<br />
 |
| 
 |
| 
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_307v0MMsEdmdo9HxCRR_Gw" name="Commit work to the iteration" guid="_307v0MMsEdmdo9HxCRR_Gw"> |
| <sectionDescription><p>
 |
| 
 |
| The <a class="elementLink" href="./../../openup/roles/project_manager_E657F936.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">Project Manager</a>&nbsp;works with the rest of the team, and especially the project
 |
| 
 |
| stakeholders,&nbsp;to identify the high-priority work items from the <a class="elementLink" href="./../../openup/workproducts/work_items_list_39D03CC8.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">Work Items List</a> to be
 |
| 
 |
| addressed. The high-level objectives provide guidance on what work items should be considered. The <a class="elementLink" href="./../../openup/workproducts/iteration_plan_B46FED39.html" guid="_0aQBEslgEdmt3adZL5Dmdw">Iteration Plan</a>&nbsp; from previous iteration should include an assessment of the
 |
| 
 |
| results and can also be used as input to the current iteration planning.&nbsp;The team reviews its velocity and
 |
| 
 |
| determines the amount of work that can be done within the iteration.&nbsp;The team breaks down into tasks those work
 |
| 
 |
| items that are assigned to the iteration&nbsp;and estimates the effort to complete each task (see&nbsp;<a class="elementLinkWithType" href="./../../openup/guidances/guidelines/agile_estimation_A4EF42B3.html" guid="_CGHskBEdEdqY7JB6N6CW2w">Guideline: Agile Estimation</a>). Typical tasks range from half day to two days in
 |
| 
 |
| lenght.
 |
| 
 |
| </p>
 |
| 
 |
| <p>
 |
| 
 |
| When a team has decided to take on a work item, it will assign the work to one or several team members. Ideally, this
 |
| 
 |
| is done by team members signing up to do the work, since this makes people motivated and committed to doing the job,
 |
| 
 |
| but based on culture, you may instead have the project manager assign the work.<br />
 |
| 
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_gIMOAPDeEdueN4Zcx2QxHQ" name="Review risks" guid="_gIMOAPDeEdueN4Zcx2QxHQ"> |
| <sectionDescription><p>
 |
| 
 |
| 
 |
| Throughout the project, new assumptions and concerns may arise.&nbsp;The team identifies and prioritizes new&nbsp;risks
 |
| 
 |
| 
 |
| as part of iteration planning, updating the <a class="elementLink" href="./../../openup/workproducts/risk_list_C4B6F290.html" guid="_Ckay8Cc_EduIsqH1Q6ZuqA">Risk List</a>. Responses to risks&nbsp;are added to the&nbsp;<a class="elementLink" href="./../../openup/workproducts/work_items_list_39D03CC8.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">Work Items List</a>, influencing the work that is being planned for that iteration.
 |
| 
 |
| 
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_7Hqr4MMsEdmdo9HxCRR_Gw" name="Define evaluation criteria" guid="_7Hqr4MMsEdmdo9HxCRR_Gw"> |
| <sectionDescription><p>
 |
| 
 |
| 
 |
| Each iteration should include testing as a part of the evaluation, and the test objectives and test cases
 |
| 
 |
| 
 |
| that&nbsp;need to be detailed. Other evaluation criteria may include successful demonstrations to key stakeholders, or
 |
| 
 |
| 
 |
| favorable usage by a small group of target users. Document evaluation criteria in the <a class="elementLink" href="./../../openup/workproducts/iteration_plan_B46FED39.html" guid="_0aQBEslgEdmt3adZL5Dmdw">Iteration Plan</a>.<br />
 |
| 
 |
| 
 |
| </p></sectionDescription> |
| </sections> |
| <purpose><p>
 |
| 
 |
| 
 |
| To identify the next increment of system capability, and create a fine-grained plan for achieving that capability
 |
| 
 |
| 
 |
| within a single iteration.
 |
| 
 |
| 
 |
| </p></purpose> |
| </org.eclipse.epf.uma:TaskDescription> |
