blob: 78dfe3d4196ad3893601a4117b4571683e7b9b89 [file] [log] [blame]
<?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>&lt;p&gt;
The Agile Manifesto claims that &quot;Individuals and interactions [are valued] over processes and tools&quot; for project
success. This principle must be kept in mind within the application of Scrum. Scrum characteristics should also be
followed:
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
Empirical approach based on process control,
&lt;/li&gt;
&lt;li&gt;
adaptative rather than predictive planning,
&lt;/li&gt;
&lt;li&gt;
team self-management to do what's need to be done.
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
Although, Scrum does not describe engineering activities required for product development.
&lt;/p&gt;
&lt;p&gt;
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.
&lt;/p&gt;
&lt;p&gt;
This lifecycle does not represent the whole product life, but only regards the production of one &lt;a class=&quot;elementLink&quot;
href=&quot;./../../../Scrum/guidances/termdefinitions/Release,_AIB9gIHrEduFs9jH8xc4xw.html&quot;
guid=&quot;_AIB9gIHrEduFs9jH8xc4xw&quot;&gt;Release&lt;/a&gt;. The &lt;a class=&quot;elementLink&quot;
href=&quot;./../../../Scrum/guidances/concepts/Produit, release et sprint,_XtRuYP-zEdqLnajTSLeAsA.html&quot;
guid=&quot;_XtRuYP-zEdqLnajTSLeAsA&quot;&gt;Product, Release and Sprint&lt;/a&gt; guide&amp;nbsp;reconsider this period in a larger context.
&lt;/p&gt;</mainDescription>
</org.eclipse.epf.uma:ContentDescription>