| <?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.4/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0" xmi:id="-BWG5zUGb8c25kuLJ3ck8ng" |
| name="define_iteration_plan,{849E3635-6FCD-4FAD-A007-CA34B9998622}" guid="-BWG5zUGb8c25kuLJ3ck8ng" |
| version="1.0.0"> |
| <sections xmi:id="_oQSWcGE-EdqnIZeW8YpHcA" name="Preconditions " guid="_oQSWcGE-EdqnIZeW8YpHcA"> |
| <sectionDescription><a id="PreCond" name="PreCond"></a> |
| <p> |
| The steps for this activity are part of XP iteration planning. In order for this activity to be successful, the |
| following preconditions should be met: |
| </p> |
| <ul> |
| <li> |
| <div align="left"> |
| The customer understands the user stories very well. |
| </div> |
| </li> |
| <li> |
| The customer has defined acceptance criteria for the stories. |
| </li> |
| <li> |
| All team members that will be involved in developing the stories should be present. |
| </li> |
| </ul></sectionDescription> |
| </sections> |
| <sections xmi:id="_oQSWcWE-EdqnIZeW8YpHcA" name="Customer Presents the User Stories " |
| guid="_oQSWcWE-EdqnIZeW8YpHcA"> |
| <sectionDescription><a id="Step1" name="Step1"></a> |
| <p> |
| The customer selects a list of user stories that he would like included in the next iteration. The stories typically |
| come from the release plan but may also include new stories that were not originally planned. The customer explains the |
| stories and the acceptance test criteria to the developers. |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_oQSWcmE-EdqnIZeW8YpHcA" name="Developers Break Down Stories " |
| guid="_oQSWcmE-EdqnIZeW8YpHcA"> |
| <sectionDescription><a id="Step2" name="Step2"></a> |
| <p> |
| The developers discuss how to implement the story and break it down into engineering tasks. Tasks should include |
| everything necessary to get the story to pass the customer's acceptance test. |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_oQSWc2E-EdqnIZeW8YpHcA" name="Developers Sign Up and Estimate " |
| guid="_oQSWc2E-EdqnIZeW8YpHcA"> |
| <sectionDescription><a id="Step3" name="Step3"></a> |
| <p> |
| The developers sign up for all the tasks. The developers put estimates only for the tasks they have personally signed |
| up for. |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_oQSWdGE-EdqnIZeW8YpHcA" name="Customer Adjusts Iteration Plan " |
| guid="_oQSWdGE-EdqnIZeW8YpHcA"> |
| <sectionDescription><a id="Step4" name="Step4"></a> |
| <p> |
| If the sum of all the task estimates is greater than the sum of all the tasks done by the team during the last |
| iteration, the customer must remove some work in order to&nbsp;respect the team's iteration velocity. |
| </p></sectionDescription> |
| </sections> |
| <purpose><a id="XE_define_iteration__activity_definition" name="XE_define_iteration__activity_definition"></a> 
 |
| <ul>
 |
| <li>
 |
| Establish what can be built during the iteration, given the team's constraints.
 |
| </li>
 |
| <li>
 |
| Allow the team to manage itself at the task level.
 |
| </li>
 |
| </ul></purpose> |
| </org.eclipse.epf.uma:TaskDescription> |