blob: 33f6117ea63e56bbb358ef39c9d9e1afd4ceb724 [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\workproducts\Product Backlog Item.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: Product Backlog Item.xmi<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START NON-TRANSLATABLE -->
<br/><br/><br/>
Attribute: presentationName<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:presentationName,_-D85cIGIEduKE9hnyImx1Q CRC: 1745490177 -->
Product Backlog Item<!-- END:presentationName,_-D85cIGIEduKE9hnyImx1Q -->
<!-- START NON-TRANSLATABLE -->
<br/><br/><br/>
Attribute: briefDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:briefDescription,_-D85cIGIEduKE9hnyImx1Q CRC: 458923285 -->
Named PBI (Product Backlog Item). Select for development the ones that bring value. <!-- END:briefDescription,_-D85cIGIEduKE9hnyImx1Q -->
<!-- START NON-TRANSLATABLE -->
<br/><br/><br/>
Attribute: mainDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:mainDescription,-KC1R73i9f6P7ZT4pgBOLzA CRC: 386624364 -->
It's either a functional or technical requirement, an enhancement request, a bug or anything else which implementation brings up value to the <a class="elementLink"
href="./../../Scrum/roles/Product Owner,_ICJyYPpaEdqsc-f87sBK8A.html" guid="_ICJyYPpaEdqsc-f87sBK8A">Product Owner</a>.&nbsp;<p>Its general attributes are:</p>
<ul>
<li>estimated value, most oftenly calculated relatively to other items through priorities,</li>
<li>estimated development cost,</li>
<li>eventually the theme (functional domain) it belongs to,</li>
<li>eventually its type (defined by the project, user story, for instance, bug, non-funcitonal requirement),</li>
</ul>
<p>If the user story technique is used, as well as test-driven development, test acceptance criterias are associated.</p>
<p>A PBI goes through the following states:</p>
<ul class="noindent">
<li>created</li>
<li>estimated</li>
<li>planned (associated to a future sprint)</li>
<li>associated to current sprint (implementation is ongoing)</li>
<li>done</li>
<li style="list-style: none">
<br />
</li>
</ul><!-- END:mainDescription,-KC1R73i9f6P7ZT4pgBOLzA -->
<!-- START NON-TRANSLATABLE -->
<br/><br/><br/>
Attribute: keyConsiderations<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:keyConsiderations,-KC1R73i9f6P7ZT4pgBOLzA CRC: 4066930091 -->
Scrum principle is to complete a PBI within a sprint.<!-- END:keyConsiderations,-KC1R73i9f6P7ZT4pgBOLzA -->
<!-- START NON-TRANSLATABLE -->
<br/><br/><br/>
Attribute: purpose<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:purpose,-KC1R73i9f6P7ZT4pgBOLzA CRC: 3975210310 -->
Serves project management: Will be placed in a sprint<!-- END:purpose,-KC1R73i9f6P7ZT4pgBOLzA -->
</body>
</html>