| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ContentDescription 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" xmi:id="-IPxNSDzXKWa-H_kJ2PMtYA" name="new_roadmap,_6Jox0IRuEduo75chJsIcXg" guid="-IPxNSDzXKWa-H_kJ2PMtYA" changeDate="2006-12-05T07:29:34.781-0800" version="1.0.0"> |
| <mainDescription><p> |
| The Agile Manifesto claims that "Individuals and interactions [are valued] over processes and tools" for project |
| success. This principle must be kept in mind within the application of Scrum. Scrum characteristics should also be |
| followed: |
| </p> |
| <ul> |
| <li> |
| Empirical approach based on process control, |
| </li> |
| <li> |
| adaptative rather than predictive planning, |
| </li> |
| <li> |
| team self-management to do what's need to be done. |
| </li> |
| </ul> |
| <p> |
| Although, Scrum does not describe engineering activities required for product development. |
| </p> |
| <p> |
| The application of Scrum as described below, must be read and used with these Agile principles always in mind. It shows |
| how Scrum elements are used during a time period or lifecycle. |
| </p> |
| <p> |
| This lifecycle does not represent the whole product life, but only regards the production of one <a class="elementLink" |
| href="./../../../Scrum/guidances/termdefinitions/Release,_AIB9gIHrEduFs9jH8xc4xw.html" |
| guid="_AIB9gIHrEduFs9jH8xc4xw">Release</a>. The <a class="elementLink" |
| href="./../../../Scrum/guidances/concepts/Produit, release et sprint,_XtRuYP-zEdqLnajTSLeAsA.html" |
| guid="_XtRuYP-zEdqLnajTSLeAsA">Product, Release and Sprint</a> guide&nbsp;reconsider this period in a larger context. |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |