blob: 56ceb865023a5559d6e3328435557d45d27a79fe [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="-BPz1k8sC6CCyJ2yZCc1p2Q" name="Produit, release et sprint,_XtRuYP-zEdqLnajTSLeAsA" guid="-BPz1k8sC6CCyJ2yZCc1p2Q" changeDate="2006-12-01T15:54:40.221-0800" version="1.0.0">
<mainDescription>&lt;p&gt;
A &lt;a class=&quot;elementLink&quot; href=&quot;./../../../Scrum/guidances/termdefinitions/Release,_AIB9gIHrEduFs9jH8xc4xw.html&quot;
guid=&quot;_AIB9gIHrEduFs9jH8xc4xw&quot;&gt;Release&lt;/a&gt;&amp;nbsp;is the result of a series of de &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 and last in general for a few months. During a product life, many releases
are rolled out.
&lt;/p&gt;
&lt;p&gt;
&lt;img height=&quot;115&quot; alt=&quot;release and sprints&quot; src=&quot;./resources/release.jpg&quot; width=&quot;600&quot; /&gt;
&lt;/p&gt;
&lt;p&gt;
A release has the following attibutes:
&lt;/p&gt;
&lt;ul class=&quot;noindent&quot;&gt;
&lt;li&gt;
goal
&lt;/li&gt;
&lt;li&gt;
type, either &quot;fixed&quot; or &quot;variable&quot;(default). If &quot;fixed&quot;, a date is provided.
&lt;/li&gt;
&lt;li&gt;
length, in days , for sprints
&lt;/li&gt;
&lt;li&gt;
forecasted number of sprints
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
&lt;a class=&quot;elementLink&quot; href=&quot;./../../../Scrum/guidances/reports/Release Planning,_Z2NzkIGWEduKE9hnyImx1Q.html&quot;
guid=&quot;_Z2NzkIGWEduKE9hnyImx1Q&quot;&gt;Release Planning&lt;/a&gt;&amp;nbsp;is a level of project planning: it shows at a high level, the
list of items to be developed during this release' sprints.&lt;br /&gt;
&lt;br /&gt;
&lt;/p&gt;</mainDescription>
</org.eclipse.epf.uma:ContentDescription>