blob: 2b87e3a4eed0db1cceeb1dad5a4ccff7ec5d5d1d [file] [log] [blame]
<?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&amp;#92;tasks&amp;#92;&amp;#92;initiate_product_backlog.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: initiate_product_backlog.xmi<br/><br/>
<!-- END NON-TRANSLATABLE -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: presentationName<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:presentationName,_BGFMoANkEduYd-55D-Aiqg CRC: 3886107154 -->Initiate Product Backlog<!-- END:presentationName,_BGFMoANkEduYd-55D-Aiqg -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: briefDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:briefDescription,_BGFMoANkEduYd-55D-Aiqg CRC: 2541271064 -->Identify a list of items, prioritize and include them in the backlog.<!-- END:briefDescription,_BGFMoANkEduYd-55D-Aiqg -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: keyConsiderations<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:keyConsiderations,-mi1O4H7RRm0YqlUNyp8TJg CRC: 1290072059 --><p>
The initial backlog must help plannning at least the 2 or 3 first sprints.
</p><!-- END:keyConsiderations,-mi1O4H7RRm0YqlUNyp8TJg -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: purpose<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:purpose,-mi1O4H7RRm0YqlUNyp8TJg CRC: 805448319 -->The goal is to produce a backlog big enough to allow the startup of the series of sprints.<!-- END:purpose,-mi1O4H7RRm0YqlUNyp8TJg -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_pWL_gAPJEdubhrgDuRb4fA CRC: 1843519645 -->Collecting the backlog items<!-- END:name,_pWL_gAPJEdubhrgDuRb4fA -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_pWL_gAPJEdubhrgDuRb4fA CRC: 35811637 --><p>
The <a class="elementLink" href="./../../Scrum/roles/product_owner_D991557B.html" guid="_ICJyYPpaEdqsc-f87sBK8A">Product Owner</a>&nbsp;establishes a first list of requirements (a requirement becomes a
<a class="elementLink" href="./../../Scrum/workproducts/product_backlog_item_C561C125.html" guid="_-D85cIGIEduKE9hnyImx1Q">Product Backlog Item</a>)&nbsp;he wish to be implemented for the end of the release.
</p>
<p>
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 <a class="elementLink" href="./../../Scrum/roles/product_owner_D991557B.html" guid="_ICJyYPpaEdqsc-f87sBK8A">Product Owner</a>&nbsp;introduces his backlog draft and each one may suggest additional items.
</p>
<p>
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.
</p><!-- END:sectionDescription,_pWL_gAPJEdubhrgDuRb4fA -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_u0Z7sAPJEdubhrgDuRb4fA CRC: 4277116988 -->Backlog Prioritizing<!-- END:name,_u0Z7sAPJEdubhrgDuRb4fA -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_u0Z7sAPJEdubhrgDuRb4fA CRC: 740234709 --><p>
The <a class="elementLink" href="./../../Scrum/roles/product_owner_D991557B.html" guid="_ICJyYPpaEdqsc-f87sBK8A">Product Owner</a>&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.
</p>
<p>
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 <a class="elementLink" href="./../../Scrum/guidances/termdefinitions/theme_E39DA34D.html" guid="_aeYKoIKlEduQgtHqedKdMA">Theme</a>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.
</p><!-- END:sectionDescription,_u0Z7sAPJEdubhrgDuRb4fA -->
</body>
</html>