| <?xml version="1.0" encoding="UTF-8"?> |
| <xmi:XMI 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"> |
| <org.eclipse.epf.uma:DeliveryProcessDescription xmi:id="-16dzhVoCex78V2iCDZVx0w" |
| name="Scrum,_9llsAQAvEdubGMceRDupFQ" guid="-16dzhVoCex78V2iCDZVx0w"> |
| <mainDescription>The production of a software version (<a class="elementLink"
 |
| href="./../../Scrum/guidances/termdefinitions/Release_A7C0A48E.html" guid="_AIB9gIHrEduFs9jH8xc4xw">Release</a>) is usually
 |
| done in a couple of months. Potential release features are collected in a the product backlog and prioritized. The product
 |
| owner is in charge of updates to this backlog.&nbsp; <br />
 |
| The release is produced with a series of iterations from 2 to 4 weeks called <a class="elementLink"
 |
| href="./../../Scrum/guidances/termdefinitions/Sprint_494C0C24.html" guid="_kftWoIHqEduFs9jH8xc4xw">Sprint</a>s. A Sprint
 |
| content is defined by the product owner, taking both priorities and team capabilities into consideration . The team defines
 |
| required tasks to develop selected features for the Sprint.&nbsp; <br />
 |
| Within a sprint, progress checkpoints are performed during Daily Scrums. This enables the ScrumMaster to figure work
 |
| progress in regards to Sprint goals and to suggest adjustments to ensure Sprint success.&nbsp; <br />
 |
| At the end of each Sprint, the team produces a <a class="elementLink"
 |
| href="./../../Scrum/workproducts/Product%20increment_9A9BD82A.html" guid="_tCmYEP-xEdqLnajTSLeAsA">Product
 |
| increment</a>&nbsp;potentially releasable, which evaluation drives a backlog update for the next Sprint.</mainDescription> |
| <keyConsiderations><p>
 |
| Scrum contributes to strengthen teaming during projects, with a collection of best practices close to those which one
 |
| can find in team sports, rugby in particular.
 |
| </p></keyConsiderations> |
| <purpose>.</purpose> |
| <howtoStaff>A Scrum team is composed of 3 to 10 persons.</howtoStaff> |
| <scope>Scrum does not describe all the software development activities (analysis, design, coding, testing) and must be considered,
 |
| rather than a full process, more as a process pattern to use for project and requirement management. <br />
 |
| Scrum does not provide help to achieve development technical activities.</scope> |
| <estimatingTechnique><p>
 |
| It is recommended to perform point-based estimations using "story points", associated to backlog items.
 |
| </p></estimatingTechnique> |
| </org.eclipse.epf.uma:DeliveryProcessDescription> |
| <org.eclipse.epf.uma:ActivityDescription xmi:id="-WiMYK8iwLeOO-sSBRBjbNQ" name="Phase de préparation,_37TdkAL_EduOAKqB9I73uw" |
| guid="-WiMYK8iwLeOO-sSBRBjbNQ"> |
| <mainDescription><p>
 |
| Scrum does not take into account all aspects of a project planning. Only Scrum's specific tasks are considered, plus
 |
| one to define all the tasks to achieve.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ActivityDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-EpBaHVCIYCqqGX_wv7dlYA" name="Travaux quotidiens,_nXmKUANlEduYd-55D-Aiqg" |
| guid="-EpBaHVCIYCqqGX_wv7dlYA"> |
| <refinedDescription>Scrum offers nothing for technical design, coding and test tasks, but can be merged with the use of XP techniques (pair
 |
| programming, test-driven development…). <br />
 |
| Tasks are not assigned by the ScrumMaster but chosen by the team members one by time after time. <br />
 |
| Team updates, each time necessary, estimation of the remaining work to do on <br />
 |
| Sprint backlog's tasks.</refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-EOwIzNPjfNIjzJ3TRAgeWQ" name="Sprint de release,_zbM2QIGBEduKE9hnyImx1Q" |
| guid="-EOwIzNPjfNIjzJ3TRAgeWQ"> |
| <keyConsiderations>Try not to make code changes during the last Sprint, it's too late and risky.</keyConsiderations> |
| <usageGuidance>It's optional. It depends on the way the product is made available to end-users. One should roll-out this optional Sprint
 |
| with tasks which can't be done before during "normal" Sprints.</usageGuidance> |
| <refinedDescription><p>
 |
| Tasks performed during this Sprint highly depend on the software deployment type.
 |
| </p>
 |
| <p>
 |
| It can include tasks such as:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| hot deployment,
 |
| </li>
 |
| <li>
 |
| product packaging,
 |
| </li>
 |
| <li>
 |
| online download publishment,
 |
| </li>
 |
| <li>
 |
| technical documentation,
 |
| </li>
 |
| <li>
 |
| user training,
 |
| </li>
 |
| <li>
 |
| product marketing.
 |
| </li>
 |
| </ul></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-MupkaQeHNEmiF7Lnl3VirQ" name="Sprint backlog,_glbG2wMAEduOAKqB9I73uw" |
| guid="-MupkaQeHNEmiF7Lnl3VirQ"> |
| <usageGuidance>One per Sprint</usageGuidance> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| </xmi:XMI> |
