| <?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="-3f4axrWBKHGv74oKN2x-gQ" |
| name="Plan release,_ho-aIP_BEdqtbrr0B1TG-A" guid="-3f4axrWBKHGv74oKN2x-gQ" changeDate="2006-12-03T00:23:18.328-0800" |
| version="1.0.0"> |
| <sections xmi:id="_8qN08APJEdubhrgDuRb4fA" name="Defining release success criterias." |
| guid="_8qN08APJEdubhrgDuRb4fA"> |
| <sectionDescription><p>
 |
| There are 2 types of releases&nbsp; :
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| end date driven release. The goal is to be on production or available to end users before a deadline.
 |
| </li>
 |
| <li>
 |
| feature driven release. The list of requirements est known and release will end when all of the requirements will
 |
| be implemented.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Success criterias depends on release type.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_BuXEQAPKEdubhrgDuRb4fA" name="Estimating backlog items" guid="_BuXEQAPKEdubhrgDuRb4fA"> |
| <sectionDescription><p>
 |
| Estimation is performed per item. It's best to work on most important items first.
 |
| </p>
 |
| <p>
 |
| Estimation is performed by the team.
 |
| </p>
 |
| <p>
 |
| The unit of measure used for estimations is commonly the point. The range of values is picked from the Fibonacci
 |
| Numbers: 1, 2, 3, 5, 8 and 13.
 |
| </p>
 |
| <p>
 |
| Estimation techniques are preferably based on a collective estimation approach. "Planning Poker" should be the rule of
 |
| game and also working with analogies by comparing estimated items works well.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_EaLKQAPKEdubhrgDuRb4fA" name="Defining sprints length" guid="_EaLKQAPKEdubhrgDuRb4fA"> |
| <sectionDescription><p>
 |
| Historically in Scrum, a sprint length is 30 days. However, it is possible, and even recommended to make shorted
 |
| sprints. Length depends on the project and its constraints.<br />
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_HDZ2UAPKEdubhrgDuRb4fA" name="Estimating velocity" guid="_HDZ2UAPKEdubhrgDuRb4fA"> |
| <sectionDescription><p>
 |
| Ideally, the team should yet have worked together on a project so its actual <a class="elementLink"
 |
| href="./../../Scrum/guidances/termdefinitions/Velocity_410B5A1F.html" guid="_HQEP8ILXEduLd8CaF_IcMA">Velocity</a>
 |
| should be yet known. This value would then be used for this release, eventually adjusted to the nature of the project.
 |
| Attention however as a point hasn't necessarily the same value across different projects.
 |
| </p>
 |
| <p>
 |
| If it's not the case, velocity must be estimated. The best way is to work on the first sprint's content and figure what
 |
| the team thinks being able to implement during this first sprint. This gives a velocity estimation which can be used
 |
| for the release planning. Then, planning will be based on velocity measured during previous sprints.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_I71XkAPKEdubhrgDuRb4fA" name="Associating backlog items to sprints" |
| guid="_I71XkAPKEdubhrgDuRb4fA"> |
| <sectionDescription><p>
 |
| With the following parameters:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| each item estimation,
 |
| </li>
 |
| <li>
 |
| items prioritization,
 |
| </li>
 |
| <li>
 |
| estimated velocity for the release,
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| items are affected to sprints of the release.
 |
| </p>
 |
| <p>
 |
| It is normal to adjust, i.e. to slightly change items prioritization, so the velocity can be the most accurate.
 |
| </p>
 |
| <p>
 |
| Items must be associated to the first sprints (2 or 3 first ones), but it is not required to do it for all sprints of
 |
| the release at first.
 |
| </p></sectionDescription> |
| </sections> |
| <keyConsiderations>It is a collective work initiated by the Product Owner.</keyConsiderations> |
| <purpose><p>
 |
| Setting up the release's initiale planning in order to launch the series of sprints.
 |
| </p></purpose> |
| </org.eclipse.epf.uma:TaskDescription> |
