Scrum/Scrum_EN/library/Scrum/tasks/Initiate Product Backlog.xmi

<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:TaskDescription 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="-mi1O4H7RRm0YqlUNyp8TJg" name="Initiate Product Backlog,_BGFMoANkEduYd-55D-Aiqg" guid="-mi1O4H7RRm0YqlUNyp8TJg" authors="Claude Aubry" changeDate="2006-12-03T00:00:53.343-0800" version="1.0.0">
  <keyConsiderations>&lt;p&gt;
    The initial backlog must help plannning at least the 2 or 3 first sprints.
&lt;/p&gt;</keyConsiderations>
  <sections xmi:id="_pWL_gAPJEdubhrgDuRb4fA" name="Collecting the backlog items" guid="_pWL_gAPJEdubhrgDuRb4fA">
    <sectionDescription>&lt;p&gt;
    The &lt;a class=&quot;elementLink&quot; href=&quot;./../../Scrum/roles/Product Owner,_ICJyYPpaEdqsc-f87sBK8A.html&quot;
    guid=&quot;_ICJyYPpaEdqsc-f87sBK8A&quot;&gt;Product Owner&lt;/a&gt;&amp;nbsp;establishes a first list of requirements (a requirement becomes a
    &lt;a class=&quot;elementLink&quot; href=&quot;./../../Scrum/workproducts/Product Backlog Item,_-D85cIGIEduKE9hnyImx1Q.html&quot;
    guid=&quot;_-D85cIGIEduKE9hnyImx1Q&quot;&gt;Product Backlog Item&lt;/a&gt;)&amp;nbsp;he wish to be implemented for the end of the release.
&lt;/p&gt;
&lt;p&gt;
    To complere this list and obtain a sufficient backlog, it is better to organize a workshop including the whole team
    plus stakeholders. During this workshop, the &lt;a class=&quot;elementLink&quot;
    href=&quot;./../../Scrum/roles/Product Owner,_ICJyYPpaEdqsc-f87sBK8A.html&quot; guid=&quot;_ICJyYPpaEdqsc-f87sBK8A&quot;&gt;Product
    Owner&lt;/a&gt;&amp;nbsp;introduces his backlog draft and each one may suggest additional items.
&lt;/p&gt;
&lt;p&gt;
    It is frequent a backlog item be identified as a User story, technique coming from EXtreme Programming (XP) et fitting
    very well to the Scrum pattern.
&lt;/p&gt;</sectionDescription>
  </sections>
  <sections xmi:id="_u0Z7sAPJEdubhrgDuRb4fA" name="Backlog Prioritizing" guid="_u0Z7sAPJEdubhrgDuRb4fA">
    <sectionDescription>&lt;p&gt;
    The &lt;a class=&quot;elementLink&quot; href=&quot;./../../Scrum/roles/Product Owner,_ICJyYPpaEdqsc-f87sBK8A.html&quot;
    guid=&quot;_ICJyYPpaEdqsc-f87sBK8A&quot;&gt;Product Owner&lt;/a&gt;&amp;nbsp;prioritizes backlog items by decreasing priorities. To him, A
    more important than B means he wants A to be implemented before B across the series of partial products.
&lt;/p&gt;
&lt;p&gt;
    wjem a backlog contains a lot of items, the prioritization of each of them is fastidious and subtil. That's why it is
    useful to define &lt;a class=&quot;elementLink&quot;
    href=&quot;./../../Scrum/guidances/termdefinitions/Theme,_aeYKoIKlEduQgtHqedKdMA.html&quot;
    guid=&quot;_aeYKoIKlEduQgtHqedKdMA&quot;&gt;Theme&lt;/a&gt;s, associate one to each item and prioritize themes before getting to item
    prioritization. This can be done during a meeting with team members and stakeholders.
&lt;/p&gt;</sectionDescription>
  </sections>
  <purpose>The goal is to produce a backlog big enough to allow the startup of the series of sprints.</purpose>
</org.eclipse.epf.uma:TaskDescription>