| <?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.3/uma.ecore" epf:version="1.0.0" xmi:id="-7gEOFFavlkSqwIoTNrvfJA" name="define_release_plan,{D755C076-8E63-4A24-89AA-A7D64E368B90}" guid="-7gEOFFavlkSqwIoTNrvfJA" version="1.0.0"> |
| <sections xmi:id="_oOauMGE-EdqnIZeW8YpHcA" name="Preparation " guid="_oOauMGE-EdqnIZeW8YpHcA"> |
| <sectionDescription><a id="Prep" name="Prep"></a> |
| <p> |
| The steps for this activity are part of XP release planning. In order for this activity to be successful, the following |
| preconditions should be met: |
| </p> |
| <ul> |
| <li> |
| The customer has enough user stories at present to fill at least one release. |
| </li> |
| <li> |
| The customer understands the user stories very well. |
| </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="_oOauMWE-EdqnIZeW8YpHcA" name="Customer Presents the User Stories " guid="_oOauMWE-EdqnIZeW8YpHcA"> |
| <sectionDescription><a id="Step1" name="Step1"></a> |
| <p> |
| The customer describes each story to the team and explains the conditions under which the story is going to be |
| considered complete. |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_oOauMmE-EdqnIZeW8YpHcA" name="Developers Estimate the User Stories " guid="_oOauMmE-EdqnIZeW8YpHcA"> |
| <sectionDescription><a id="Step2" name="Step2"></a> |
| <p> |
| The developers discuss each story and come up with an estimate based on their experience. High-level design discussions |
| take place as developers try to understand the story and discuss different ways of implementing it. In some cases, the |
| team will not be able to provide a reasonable estimate: |
| </p> |
| <ul> |
| <li> |
| They do not understand the story: the team should be asking more questions&nbsp;to the customer. |
| </li> |
| <li> |
| The story is too big: the developers don't have a good grasp of the scope. It should be broken down into smaller |
| stories. |
| </li> |
| <li> |
| They don't know how to do it: they will need to do some research first. |
| </li> |
| </ul> |
| <p> |
| Be careful to avoid analysis paralysis. The first few times the team estimates stories, it may take as long as an hour |
| to estimate a story. The second story should take less time. Your goal should be to be able to estimate a story in only |
| a few minutes. |
| </p> |
| <p> |
| As a rule of thumb, story estimates should not exceed the iteration length based on a pair of people dedicated to the |
| story. When stories exceed the iteration length, the customer splits the story. |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_oOg00GE-EdqnIZeW8YpHcA" name="Customer Prioritizes Stories " guid="_oOg00GE-EdqnIZeW8YpHcA"> |
| <sectionDescription><a id="Step3" name="Step3"></a> |
| <p> |
| Once all the stories have an estimated cost, the customer can prioritize the stories into the release plan.The customer |
| organizes stories into iterations and sequences of iterations into releases. The sum of all story points in each |
| iteration cannot exceed the team's velocity. At the beginning of the project, you will have to guess the team's |
| velocity. Try one third of the ideal programmer time available in an iteration. After a few iterations, revisit the |
| plan and use the team's measured velocity. See more on release planning in the <a class="elementLinkWithUserText" |
| href="./../../xp/guidances/guidelines/planning_game,6.7335956461328426E-307.html" |
| guid="6.7335956461328426E-307">planning game guideline</a>. |
| </p></sectionDescription> |
| </sections> |
| <purpose><a id="XE_define_release__activity_definition" name="XE_define_release__activity_definition"></a> |
| <ul> |
| <li> |
| To estimate the content and delivery date for a release of the product. |
| </li> |
| </ul></purpose> |
| </org.eclipse.epf.uma:TaskDescription> |