| <?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\tasks\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 --> |
| <!-- START NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,_BGFMoANkEduYd-55D-Aiqg CRC: 3886107154 --> |
| Initiate Product Backlog<!-- END:presentationName,_BGFMoANkEduYd-55D-Aiqg --> |
| <!-- START NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| |
| 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 --> |
| <!-- START NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| |
| Attribute: keyConsiderations<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:keyConsiderations,-mi1O4H7RRm0YqlUNyp8TJg CRC: 919313895 --> |
| <p>The initial backlog must help plannning at least the 2 or 3 first sprints.</p><!-- END:keyConsiderations,-mi1O4H7RRm0YqlUNyp8TJg --> |
| <!-- START NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| |
| Attribute: purpose<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:purpose,-mi1O4H7RRm0YqlUNyp8TJg CRC: 3385836891 --> |
| The goal is to produce a backlog big enough to allow the startup of the series of sprints.<!-- END:purpose,-mi1O4H7RRm0YqlUNyp8TJg --> |
| <!-- START NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| |
| Attribute: name<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:name,_pWL_gAPJEdubhrgDuRb4fA CRC: 3629735713 --> |
| Collecting the backlog items<!-- END:name,_pWL_gAPJEdubhrgDuRb4fA --> |
| <!-- START NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| |
| Attribute: sectionDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:sectionDescription,_pWL_gAPJEdubhrgDuRb4fA CRC: 2317119429 --> |
| <p>The <a class="elementLink" href="./../../Scrum/roles/Product Owner,_ICJyYPpaEdqsc-f87sBK8A.html" |
| guid="_ICJyYPpaEdqsc-f87sBK8A">Product Owner</a> establishes a first list of requirements (a requirement becomes a <a class="elementLink" |
| href="./../../Scrum/workproducts/Product Backlog Item,_-D85cIGIEduKE9hnyImx1Q.html" |
| guid="_-D85cIGIEduKE9hnyImx1Q">Product Backlog Item</a>) 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,_ICJyYPpaEdqsc-f87sBK8A.html" guid="_ICJyYPpaEdqsc-f87sBK8A">Product Owner</a> 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 --> |
| <!-- START NON-TRANSLATABLE --> |
| <br /> |
| <br/><br/><br/> |
| |
| Attribute: name<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:name,_u0Z7sAPJEdubhrgDuRb4fA CRC: 2739709896 --> |
| Backlog Prioritizing<!-- END:name,_u0Z7sAPJEdubhrgDuRb4fA --> |
| <!-- START NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| |
| Attribute: sectionDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:sectionDescription,_u0Z7sAPJEdubhrgDuRb4fA CRC: 756747292 --> |
| <p>The <a class="elementLink" href="./../../Scrum/roles/Product Owner,_ICJyYPpaEdqsc-f87sBK8A.html" |
| guid="_ICJyYPpaEdqsc-f87sBK8A">Product Owner</a> 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,_aeYKoIKlEduQgtHqedKdMA.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> |
