| <?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="-NRwwk6YGAtu25V3Lc04G6w" |
| name="Plan sprint,_4LOggPpaEdqsc-f87sBK8A" guid="-NRwwk6YGAtu25V3Lc04G6w" authors="Claude Aubry" |
| changeDate="2006-12-03T00:57:11.890-0800" version="1.0.0"> |
| <sections xmi:id="_TJNsUP--Edqtbrr0B1TG-A" name="Defining the sprint's goal" guid="_TJNsUP--Edqtbrr0B1TG-A"> |
| <sectionDescription><p>
 |
| At the beginning of the first sprints of the first release of a product, the goal is usually to show the feasability on
 |
| the potential architecture.
 |
| </p>
 |
| <p>
 |
| Then, once the architecture is validated, the goal of a sprint is proposed by the <a class="elementLink"
 |
| href="./../../Scrum/roles/Product%20Owner_D991557B.html" guid="_ICJyYPpaEdqsc-f87sBK8A">Product Owner</a> and discussed
 |
| with the team. It oftenly focuses on a given functional theme.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_xvy5UAPKEdubhrgDuRb4fA" name="Selecting the items" guid="_xvy5UAPKEdubhrgDuRb4fA"> |
| <sectionDescription><p>
 |
| It is about defining the scope of this sprint. This is done by associating <a class="elementLink"
 |
| href="./../../Scrum/workproducts/Product%20Backlog%20Item_C561C125.html" guid="_-D85cIGIEduKE9hnyImx1Q">Product Backlog
 |
| Item</a>s one by one &nbsp;to the sprint, and balancing with the team velocity.
 |
| </p>
 |
| <p>
 |
| If a <a class="elementLink" href="./../../Scrum/guidances/reports/Release%20Planning_ED85F1BB.html"
 |
| guid="_Z2NzkIGWEduKE9hnyImx1Q">Release planning</a>&nbsp;has been done, this step is only about collectively validating
 |
| the forecasted backlog subset for the sprint.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_p4C0sP--Edqtbrr0B1TG-A" name="Identifying tasks from items" guid="_p4C0sP--Edqtbrr0B1TG-A"> |
| <sectionDescription><p>
 |
| The 2nd part of the meeting is about defining how the team is gonna achieve the sprint objectives.<br />
 |
| To do that, each selected <a class="elementLink"
 |
| href="./../../Scrum/workproducts/Product%20Backlog%20Item_C561C125.html" guid="_-D85cIGIEduKE9hnyImx1Q">Product Backlog
 |
| Item</a>&nbsp;is decomposed into tasks. This enables the team to discuss and figure solutions aspects towards this
 |
| item, asking the procut owner, if necessary, precisions on the product behavior.<br />
 |
| </p>
 |
| <p>
 |
| Normaly, all the lifecycle activities are rolled out during a sprint:<br />
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Selected requirements are specified
 |
| </li>
 |
| <li>
 |
| Architecture is modified if necessary
 |
| </li>
 |
| <li>
 |
| Classes and subsystems are designed, implemented and tested
 |
| </li>
 |
| <li>
 |
| The different components are integrated and tested
 |
| </li>
 |
| <li>
 |
| Product is packaged
 |
| </li>
 |
| <li>
 |
| Acceptance tests are passed.<br />
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| The given importance to these activities depends on the position of the sprint within the release.<br />
 |
| <br />
 |
| The planned work in a previous sprint that couldn't be done because of objectives reduction, becomes the priority for
 |
| next sprint.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_DxNQUAPLEdubhrgDuRb4fA" name="Estimating tasks" guid="_DxNQUAPLEdubhrgDuRb4fA"> |
| <sectionDescription><p>
 |
| Tasks are estimated in hours. Tasks should be thin enough to take less than 16 hours.
 |
| </p>
 |
| <p>
 |
| Estimation is collectively made by the team. During this discussion, technical aspects are reviewed.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_worbAP--Edqtbrr0B1TG-A" name="Assigning tasks" guid="_worbAP--Edqtbrr0B1TG-A"> |
| <sectionDescription>Once sprint activities are defined, they will be assigned to team members. Activities can be done by one or many persons.
 |
| All the activities must be taken in to account, including work meetings (non Scrum meetings as well), code or document
 |
| reviews.<br />
 |
| It is preferable to delay assignement of certain activities, which will be assigned during the sprint in accordance with
 |
| team members availability.</sectionDescription> |
| </sections> |
| <sections xmi:id="_Iq14wAPLEdubhrgDuRb4fA" name="Getting team commitment" guid="_Iq14wAPLEdubhrgDuRb4fA"> |
| <sectionDescription><p>
 |
| Team should collectively commit to the sprint backlog, that is on backlog items it estimates being able to implement
 |
| within the sprint.
 |
| </p></sectionDescription> |
| </sections> |
| <keyConsiderations><p>
 |
| The sprint planning meeting is a work in group.
 |
| </p>
 |
| <p>
 |
| It is limited in time:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| max. length: up to 4 hours
 |
| </li>
 |
| <li>
 |
| avg length: 2 hours
 |
| </li>
 |
| </ul></keyConsiderations> |
| <purpose>The goal is to plan the starting sprint..</purpose> |
| </org.eclipse.epf.uma:TaskDescription> |
