blob: 7fbfab888d86a18c74ad04115c25d94eb1b1fc9d [file] [log] [blame]
<?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:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf"
epf:version="1.5.0" xmi:id="_Wk7noKe1EdmGSrcKGOYDGg"
name="plan_iteration,_0keUEMlgEdmt3adZL5Dmdw" guid="_Wk7noKe1EdmGSrcKGOYDGg" changeDate="2008-02-21T12:32:50.812-0800"
version="7.2.0">
<mainDescription>&lt;p>&#xD;
During project planning, iterations are identified, but the estimates have an acceptable uncertainty due to the lack of&#xD;
detail at the project inception. This task is repeated for each iteration within a release. It allows the team to&#xD;
increase the accuracy of the estimates for one iteration, as more detail is known along the project. The project&#xD;
manager has the responsibility of ensuring that the team commits to a reasonable amount of work for the&#xD;
iteration, based on team performance from previous iterations.&#xD;
&lt;/p></mainDescription>
<sections xmi:id="_7bz7AIyAEdyhZb-MhCJrlA" name="Prioritize Work Items List" guid="_7bz7AIyAEdyhZb-MhCJrlA">
<sectionDescription>The work items list should be prioritized before you plan the next iteration. Consider what has changed since the last&#xD;
iteration plan (such as new change requests, shifting priorities of your stakeholders, or new risks that have been&#xD;
encountered).</sectionDescription>
</sections>
<sections xmi:id="_CtKCMMBHEdqSgKaj2SZBmg" name="Define iteration objectives" guid="_CtKCMMBHEdqSgKaj2SZBmg">
<sectionDescription>&lt;p>&#xD;
Work with the team to refine the iteration objectives found in the project definition and scope, and document them in&#xD;
the iteration plan in order to provide high-level direction to what should be targeted for the iteration. The&#xD;
objectives should be driven based on stakeholder priorities, and will be revised as the iteration plan is&#xD;
finalized. Those objectives are usually defined as high-level capabilities or scenarios, which need to be implemented and&#xD;
tested during the iteration in order to deliver increased value to the customer.&lt;br />&#xD;
&lt;/p></sectionDescription>
</sections>
<sections xmi:id="_307v0MMsEdmdo9HxCRR_Gw" name="Commit work to the iteration" guid="_307v0MMsEdmdo9HxCRR_Gw">
<sectionDescription>&lt;p>&#xD;
The project manager works with the team, and especially the project stakeholders, to identify the&#xD;
high-priority work items from the work items list to be addressed. The high-level objectives provide guidance on what&#xD;
work items should be considered. The iteration plan from previous iteration should include an assessment of the results,&#xD;
and can also be used as input to the current iteration planning. The team reviews its velocity and determines the&#xD;
amount of work that can be done within the iteration. The team breaks down into tasks those work items that are&#xD;
assigned to the iteration, and estimates the effort to complete each task. Typical tasks range from half a day to two&#xD;
days in length, and are captured in the work items list. See &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../core.mgmt.common.extend_supp/guidances/guidelines/agile_estimation_A4EF42B3.html&quot; guid=&quot;_CGHskBEdEdqY7JB6N6CW2w&quot;>Guideline: Agile Estimation&lt;/a> for more information.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
When the team has decided to take on a work item, it will assign the work to one or several team members. Ideally,&#xD;
this is done by team members signing up to do the work, since this makes people motivated and committed to doing the&#xD;
job. However, based on your culture, you may instead have the project manager assign the work.&lt;br />&#xD;
&lt;/p></sectionDescription>
</sections>
<sections xmi:id="_HzNVgIyBEdyhZb-MhCJrlA" name="Identify and review risks" guid="_HzNVgIyBEdyhZb-MhCJrlA">
<sectionDescription>&lt;p>&#xD;
Throughout the project, new assumptions and concerns may arise. The team identifies and prioritizes new risks&#xD;
as part of iteration planning, updating the risk list. Responses to risks are added to the work items&#xD;
list, influencing the work that is being planned for that iteration.&#xD;
&lt;/p></sectionDescription>
</sections>
<sections xmi:id="_7Hqr4MMsEdmdo9HxCRR_Gw" name="Define evaluation criteria" guid="_7Hqr4MMsEdmdo9HxCRR_Gw">
<sectionDescription>&lt;p>&#xD;
Each iteration should include testing as a part of the evaluation, as well as the test objectives and test cases&#xD;
that need to be detailed. Other evaluation criteria may include successful demonstrations to key stakeholders, or&#xD;
favorable usage by a small group of target users. Document evaluation criteria in the iteration plan.&#xD;
&lt;/p></sectionDescription>
</sections>
<sections xmi:id="_-tp18FHjEd2IaYFd32DrjQ" name="Refine project definition and scope"
guid="_-tp18FHjEd2IaYFd32DrjQ">
<sectionDescription>&lt;p>&#xD;
Depending on the results of the previous iteration assessment, update the project definition work products as&#xD;
needed. Necessary changes can encompass the need to acquire new resources, to absorb an unplanned effort increase, or&#xD;
to implement a specific change request. If a change affects defined project milestones, consult with the&#xD;
stakeholders before committing to it.&#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>