Scrum/Scrum_EN/library/Scrum/deliveryprocesses/Scrum/content.xmi

<?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.3/uma.ecore" rmc:version="7.1.0" epf:version="1.0.0">
  <org.eclipse.epf.uma:DeliveryProcessDescription xmi:id="-16dzhVoCex78V2iCDZVx0w" name="Scrum,_9llsAQAvEdubGMceRDupFQ" guid="-16dzhVoCex78V2iCDZVx0w">
    <mainDescription>The production of a software version (&lt;a class=&quot;elementLink&quot;
href=&quot;./../../Scrum/guidances/termdefinitions/Release,_AIB9gIHrEduFs9jH8xc4xw.html&quot;
guid=&quot;_AIB9gIHrEduFs9jH8xc4xw&quot;&gt;Release&lt;/a&gt;) 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.&amp;nbsp; &lt;br /&gt;
 The release is produced with a series of iterations from 2 to 4 weeks called &lt;a class=&quot;elementLink&quot;
href=&quot;./../../Scrum/guidances/termdefinitions/Sprint,_kftWoIHqEduFs9jH8xc4xw.html&quot;
guid=&quot;_kftWoIHqEduFs9jH8xc4xw&quot;&gt;Sprint&lt;/a&gt;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.&amp;nbsp;
&lt;br /&gt;
 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.&amp;nbsp; &lt;br /&gt;
 At the end of each Sprint, the team produces a &lt;a class=&quot;elementLink&quot;
href=&quot;./../../Scrum/workproducts/Product increment,_tCmYEP-xEdqLnajTSLeAsA.html&quot; guid=&quot;_tCmYEP-xEdqLnajTSLeAsA&quot;&gt;Product
Increment&lt;/a&gt;&amp;nbsp;potentially releasable, which evaluation drives a backlog update for the next Sprint.</mainDescription>
    <keyConsiderations>&lt;p&gt;
    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.
&lt;/p&gt;</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. &lt;br /&gt;
 Scrum does not provide help to achieve development technical activities.</scope>
    <estimatingTechnique>&lt;p&gt;
    It is recommended to perform point-based estimations using &quot;story points&quot;, associated to backlog items.
&lt;/p&gt;</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>&lt;p&gt;
    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.
&lt;/p&gt;</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…). &lt;br /&gt;
 Tasks are not assigned by the ScrumMaster but chosen by the team members one by time after time. &lt;br /&gt;
 Team updates, each time necessary, estimation of the remaining work to do on &lt;br /&gt;
 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 &quot;normal&quot; Sprints.</usageGuidance>
    <refinedDescription>&lt;p&gt;
    Tasks performed during this Sprint highly depend on the software deployment type.
&lt;/p&gt;
&lt;p&gt;
    It can include tasks such as:
&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;
        hot deployment,
    &lt;/li&gt;
    &lt;li&gt;
        product packaging,
    &lt;/li&gt;
    &lt;li&gt;
        online download publishment,
    &lt;/li&gt;
    &lt;li&gt;
        technical documentation,
    &lt;/li&gt;
    &lt;li&gt;
        user training,
    &lt;/li&gt;
    &lt;li&gt;
        product marketing.
    &lt;/li&gt;
&lt;/ul&gt;</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>