blob: a088a9453cfa9a969fffbe0b009b3bf6e2726e4a [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;workproducts&amp;#92;&amp;#92;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 -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: presentationName<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:presentationName,_-D85cIGIEduKE9hnyImx1Q CRC: 1745490177 -->Product Backlog Item<!-- END:presentationName,_-D85cIGIEduKE9hnyImx1Q -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: briefDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:briefDescription,_-D85cIGIEduKE9hnyImx1Q CRC: 1414667859 -->Named PBI (Product Backlog Item). Select for development the ones that bring value.<!-- END:briefDescription,_-D85cIGIEduKE9hnyImx1Q -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: mainDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:mainDescription,-KC1R73i9f6P7ZT4pgBOLzA CRC: 1021999899 -->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_D991557B.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 -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: keyConsiderations<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:keyConsiderations,-KC1R73i9f6P7ZT4pgBOLzA CRC: 3467918051 -->Scrum principle is to complete a PBI within a sprint.<!-- END:keyConsiderations,-KC1R73i9f6P7ZT4pgBOLzA -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: purpose<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:purpose,-KC1R73i9f6P7ZT4pgBOLzA CRC: 2741103905 -->Serves project management: Will be placed in a sprint<!-- END:purpose,-KC1R73i9f6P7ZT4pgBOLzA -->
</body>
</html>