blob: 48a9cc5b3e18ca0dd507852596da8031796ba08b [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="" xmlns:org.eclipse.epf.uma="" epf:version="1.0.0" xmi:id="_Wk7noKe1EdmGSrcKGOYDGg" name="plan_iteration,_0keUEMlgEdmt3adZL5Dmdw" guid="_Wk7noKe1EdmGSrcKGOYDGg" changeDate="2006-09-07T19:29:53.219-0400">
<sections xmi:id="_CtKCMMBHEdqSgKaj2SZBmg" name="Define the iteration objectives" guid="_CtKCMMBHEdqSgKaj2SZBmg">
At the beginning of an iteration, the &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/roles/project_manager,_0a0o0MlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0a0o0MlgEdmt3adZL5Dmdw&quot;&gt;Role: Project Manager&lt;/a&gt;&amp;nbsp;works with the team to define 1-5 objectives. These objectives should be a refinement of the
iteration objectives found in the &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/workproducts/project_plan,_0a6vcMlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0a6vcMlgEdmt3adZL5Dmdw&quot;&gt;Artifact: Project Plan&lt;/a&gt;, and should provide high-level direction to what should be
targeted for the iteration. The objectives should be driven based on &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/roles/stakeholder,_dTa6gMAYEdqX-s4mWhkyqQ.html&quot; guid=&quot;_dTa6gMAYEdqX-s4mWhkyqQ&quot;&gt;Role: Stakeholder&lt;/a&gt;&amp;nbsp;priorities, and&amp;nbsp;will be revised as the iteration plan is finalized. The objectives are
usually defined as high-level capabilities or scenarios that need to be implemented and tested during the
iteration.&lt;br /&gt;
<sections xmi:id="_307v0MMsEdmdo9HxCRR_Gw" name="Produce detailed plan" guid="_307v0MMsEdmdo9HxCRR_Gw">
<sectionDescription>The &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/roles/project_manager,_0a0o0MlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0a0o0MlgEdmt3adZL5Dmdw&quot;&gt;Role: Project Manager&lt;/a&gt; works with the rest of the team, and especially the project
stakeholders,&amp;nbsp;to identify the high-priority work items from the &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/workproducts/work_items_list,_rGNWsCbSEdqh1LYUOGRh2A.html&quot; guid=&quot;_rGNWsCbSEdqh1LYUOGRh2A&quot;&gt;Artifact: Work Items List&lt;/a&gt; to be addressed within the iteration. The high-level
objectives provide guidance on what work items should be considered. The team should break down work items so they fit
within the iteration as necessary. Actual effort to complete each Work Item should be estimated. 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.</sectionDescription>
<sections xmi:id="_7Hqr4MMsEdmdo9HxCRR_Gw" name="Define evaluation criteria" guid="_7Hqr4MMsEdmdo9HxCRR_Gw">
Each iteration should include testing as a part of the evaluation, and the test objectives and test cases needs to be
detailed. Other evaluation criteria may include successful demonstrations to key stakeholders, or favorable usage by a
small group of target users.&lt;br /&gt;
<purpose>&lt;p class=&quot;MsoNormal&quot; style=&quot;MARGIN: 0in 0in 0pt&quot;&gt;
Develop a fine-grained plan for a single iteration, identifying the goals and evaluation criteria of an iteration
(usually the next one).