| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" |
| xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.4/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0" xmi:id="-KC1R73i9f6P7ZT4pgBOLzA" |
| name="product_backlog_item,_-D85cIGIEduKE9hnyImx1Q" guid="-KC1R73i9f6P7ZT4pgBOLzA" |
| changeDate="2007-08-17T09:52:25.198-0700" version="1.0.0"> |
| <mainDescription>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%20Owner_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></mainDescription> |
| <keyConsiderations>Scrum principle is to complete a PBI within a sprint.</keyConsiderations> |
| <purpose>Serves project management: Will be placed in a sprint</purpose> |
| </org.eclipse.epf.uma:ArtifactDescription> |
