| <?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;tasks&#92;&#92;plan_release.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: plan_release.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,_ho-aIP_BEdqtbrr0B1TG-A CRC: 2181311053 -->Plan Release<!-- END:presentationName,_ho-aIP_BEdqtbrr0B1TG-A --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,_ho-aIP_BEdqtbrr0B1TG-A CRC: 3849421930 -->Mid-term planning.<!-- END:briefDescription,_ho-aIP_BEdqtbrr0B1TG-A --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: keyConsiderations<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:keyConsiderations,-3f4axrWBKHGv74oKN2x-gQ CRC: 2379044509 -->It is a collective work initiated by the Product Owner.<!-- END:keyConsiderations,-3f4axrWBKHGv74oKN2x-gQ --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: purpose<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:purpose,-3f4axrWBKHGv74oKN2x-gQ CRC: 1980491333 --><p> |
| Setting up the release's initiale planning in order to launch the series of sprints. |
| </p><!-- END:purpose,-3f4axrWBKHGv74oKN2x-gQ --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: name<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:name,_8qN08APJEdubhrgDuRb4fA CRC: 3942998795 -->Defining release success criterias.<!-- END:name,_8qN08APJEdubhrgDuRb4fA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: sectionDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:sectionDescription,_8qN08APJEdubhrgDuRb4fA CRC: 1254661791 --><p> |
| There are 2 types of releases : |
| </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><!-- END:sectionDescription,_8qN08APJEdubhrgDuRb4fA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: name<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:name,_BuXEQAPKEdubhrgDuRb4fA CRC: 1799632786 -->Estimating backlog items<!-- END:name,_BuXEQAPKEdubhrgDuRb4fA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: sectionDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:sectionDescription,_BuXEQAPKEdubhrgDuRb4fA CRC: 846050048 --><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><!-- END:sectionDescription,_BuXEQAPKEdubhrgDuRb4fA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: name<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:name,_EaLKQAPKEdubhrgDuRb4fA CRC: 1391032814 -->Defining sprints length<!-- END:name,_EaLKQAPKEdubhrgDuRb4fA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: sectionDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:sectionDescription,_EaLKQAPKEdubhrgDuRb4fA CRC: 1875396976 --><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><!-- END:sectionDescription,_EaLKQAPKEdubhrgDuRb4fA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: name<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:name,_HDZ2UAPKEdubhrgDuRb4fA CRC: 1898232669 -->Estimating velocity<!-- END:name,_HDZ2UAPKEdubhrgDuRb4fA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: sectionDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:sectionDescription,_HDZ2UAPKEdubhrgDuRb4fA CRC: 1892905321 --><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><!-- END:sectionDescription,_HDZ2UAPKEdubhrgDuRb4fA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: name<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:name,_I71XkAPKEdubhrgDuRb4fA CRC: 1765873047 -->Associating backlog items to sprints<!-- END:name,_I71XkAPKEdubhrgDuRb4fA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: sectionDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:sectionDescription,_I71XkAPKEdubhrgDuRb4fA CRC: 1642269545 --><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><!-- END:sectionDescription,_I71XkAPKEdubhrgDuRb4fA --> |
| </body> |
| </html> |
