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