| <?xml version="1.0" encoding="UTF-8"?> |
| <!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd"> |
| <!-- VERSION rmc:7.1.0 --> |
| <html xmlns="http://www.w3.org/1999/xhtml"> |
| <head> |
| <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> |
| <!-- START NON-TRANSLATABLE --> |
| <title>Scrum&#92;deliveryprocesses&#92;&#92;content.xmi</title> |
| </head> |
| <!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. --> |
| <body> |
| Element Name: content.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,_9llsAQAvEdubGMceRDupFQ CRC: 992889505 -->Scrum Lifecycle<!-- END:presentationName,_9llsAQAvEdubGMceRDupFQ --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,_9llsAQAvEdubGMceRDupFQ CRC: 4077553412 -->Phases, sprints and tasks to roll-out during a release production.<!-- END:briefDescription,_9llsAQAvEdubGMceRDupFQ --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: mainDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:mainDescription,-16dzhVoCex78V2iCDZVx0w CRC: 2116215177 -->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. <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. <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. <br /> |
| At the end of each Sprint, the team produces a <a class="elementLink" href="./../../Scrum/workproducts/product_increment_9A9BD82A.html" guid="_tCmYEP-xEdqLnajTSLeAsA">Product increment</a> potentially releasable, which evaluation drives a backlog update for the next Sprint.<!-- END:mainDescription,-16dzhVoCex78V2iCDZVx0w --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: keyConsiderations<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:keyConsiderations,-16dzhVoCex78V2iCDZVx0w CRC: 2562853902 --><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><!-- END:keyConsiderations,-16dzhVoCex78V2iCDZVx0w --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: purpose<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:purpose,-16dzhVoCex78V2iCDZVx0w CRC: 248832578 -->.<!-- END:purpose,-16dzhVoCex78V2iCDZVx0w --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: howtoStaff<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:howtoStaff,-16dzhVoCex78V2iCDZVx0w CRC: 986612138 -->A Scrum team is composed of 3 to 10 persons.<!-- END:howtoStaff,-16dzhVoCex78V2iCDZVx0w --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: scope<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:scope,-16dzhVoCex78V2iCDZVx0w CRC: 1645246931 -->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.<!-- END:scope,-16dzhVoCex78V2iCDZVx0w --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: estimatingTechnique<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:estimatingTechnique,-16dzhVoCex78V2iCDZVx0w CRC: 1591701511 --><p> |
| It is recommended to perform point-based estimations using "story points", associated to backlog items. |
| </p><!-- END:estimatingTechnique,-16dzhVoCex78V2iCDZVx0w --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,_37TdkAL_EduOAKqB9I73uw CRC: 2792626813 -->Preparation Phase<!-- END:presentationName,_37TdkAL_EduOAKqB9I73uw --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,_37TdkAL_EduOAKqB9I73uw CRC: 688115355 -->This initiale phase allows to prepare all prerequisites before starting a series of Sprints<!-- END:briefDescription,_37TdkAL_EduOAKqB9I73uw --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: mainDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:mainDescription,-WiMYK8iwLeOO-sSBRBjbNQ CRC: 668695787 --><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><!-- END:mainDescription,-WiMYK8iwLeOO-sSBRBjbNQ --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,_glbG2wMAEduOAKqB9I73uw CRC: 439217272 -->Sprint Backlog<!-- END:presentationName,_glbG2wMAEduOAKqB9I73uw --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: usageGuidance<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:usageGuidance,-MupkaQeHNEmiF7Lnl3VirQ CRC: 2624939969 -->One per Sprint<!-- END:usageGuidance,-MupkaQeHNEmiF7Lnl3VirQ --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,_nXmKUANlEduYd-55D-Aiqg CRC: 170677076 -->Daily works<!-- END:presentationName,_nXmKUANlEduYd-55D-Aiqg --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,_nXmKUANlEduYd-55D-Aiqg CRC: 880605671 -->The team performs backlog tasks to reach Sprint goal.<!-- END:briefDescription,_nXmKUANlEduYd-55D-Aiqg --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: refinedDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:refinedDescription,-EpBaHVCIYCqqGX_wv7dlYA CRC: 3231498880 -->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.<!-- END:refinedDescription,-EpBaHVCIYCqqGX_wv7dlYA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,_zbM2QIGBEduKE9hnyImx1Q CRC: 2097837169 -->Release work<!-- END:presentationName,_zbM2QIGBEduKE9hnyImx1Q --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,_zbM2QIGBEduKE9hnyImx1Q CRC: 490900752 -->This last Sprint is for product release preparation.<!-- END:briefDescription,_zbM2QIGBEduKE9hnyImx1Q --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: keyConsiderations<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:keyConsiderations,-EOwIzNPjfNIjzJ3TRAgeWQ CRC: 3753199623 -->Try not to make code changes during the last Sprint, it's too late and risky.<!-- END:keyConsiderations,-EOwIzNPjfNIjzJ3TRAgeWQ --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: usageGuidance<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:usageGuidance,-EOwIzNPjfNIjzJ3TRAgeWQ CRC: 2612246193 -->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.<!-- END:usageGuidance,-EOwIzNPjfNIjzJ3TRAgeWQ --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: refinedDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:refinedDescription,-EOwIzNPjfNIjzJ3TRAgeWQ CRC: 4134451947 --><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><!-- END:refinedDescription,-EOwIzNPjfNIjzJ3TRAgeWQ --> |
| </body> |
| </html> |
