| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:RoleDescription 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="-35iKPqDM2F2PjKWQLCW4tA" |
| name="Product Owner,_ICJyYPpaEdqsc-f87sBK8A" guid="-35iKPqDM2F2PjKWQLCW4tA" authors="Claude Aubry" |
| changeDate="2006-12-06T00:55:24.078-0800" version="1.0.0"> |
| <mainDescription><p>
 |
| The Product Owner (<i>Product Owner</i>) represents customers and users in the team.
 |
| </p>
 |
| <p>
 |
| He is responsible for defining the features of the product to be developed be the team in terms of:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <strong>functionality</strong>. He identifies each product requirement as a <a class="elementLink"
 |
| href="./../../Scrum/workproducts/Product%20Backlog%20Item_C561C125.html" guid="_-D85cIGIEduKE9hnyImx1Q">Product
 |
| Backlog Item</a>. He supplies details for those requirements when they are needed by the team. It is desirable that
 |
| he specifies the acceptance tests for those requirements.
 |
| </li>
 |
| <li>
 |
| <strong>priority</strong>. He is the one that defines the order in which those items will be developed, according
 |
| to the value that they bring to customers and users. That feeds the team with <a class="elementLink"
 |
| href="./../../Scrum/workproducts/Product%20Backlog_DB75BBD.html" guid="_5ABscPpYEdqsc-f87sBK8A">Product
 |
| Backlog</a>&nbsp;ready for planning sprints.
 |
| </li>
 |
| <li>
 |
| <strong>goal</strong>. He defines the release goals and makes decisions concerning <a class="elementLink"
 |
| href="./../../Scrum/guidances/reports/Release%20Planning_ED85F1BB.html" guid="_Z2NzkIGWEduKE9hnyImx1Q">Release
 |
| planning</a>.
 |
| </li>
 |
| </ul></mainDescription> |
| <keyConsiderations><p>
 |
| His commitment is essential to ensure the project success. By defining his product vision, he gives the pulse to the
 |
| team. By externally promoting each sprint result, he brings a motivating recognition to the team.
 |
| </p></keyConsiderations> |
| <skills><p>
 |
| A person who plays this role should have the following competencies:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| good knowledge of business domain,
 |
| </li>
 |
| <li>
 |
| being able to demonstrate a leadership, respected by external stakeholders (customers and users),
 |
| </li>
 |
| <li>
 |
| being able to make decisions at the right time (not too soon, not too late),
 |
| </li>
 |
| <li>
 |
| "open minded" to changes,
 |
| </li>
 |
| <li>
 |
| good communication skills witht the team.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| A former business analyst is a good candidate for this role.
 |
| </p></skills> |
| <assignmentApproaches><p>
 |
| There's only one person who plays this role. This person must be assigned to the project (the Product Owner is a member
 |
| of the extended team and participates to meetings). The workload almost requires a full-time assignement.
 |
| </p>
 |
| <p>
 |
| It is important he is very available to answer to team's questions, in order to define feature tests and give his
 |
| advice on various product aspects (the software UI for instance).
 |
| </p></assignmentApproaches> |
| <synonyms>Product Owner,&nbsp;(customer in XP)</synonyms> |
| </org.eclipse.epf.uma:RoleDescription> |
