| <?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-Mcx6tqWLjhR3Dd12ad3EsQ" name="product_owner,_ob1d4EuUEeCsWoZ6ZH16Zg" guid="-Mcx6tqWLjhR3Dd12ad3EsQ" changeDate="2011-10-13T09:55:47.374-0600" version="7.5.1"> |
| <mainDescription><p>
 |
| This role is the one and only person responsible for managing the Product Backlog and ensuring the value of the work
 |
| the development team performs. The Product Owner has the responsibility of defining what is the right product to build,
 |
| determining the order in which features will be built, and making sure that the product actually works. The Product
 |
| Owner is responsible for defining the features of the product to be developed by the team in terms of:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <strong>Functionality:</strong> Identifies each product requirement as a Product Backlog Item and supplies
 |
| details for those requirements when they are needed by the team, including specifying the acceptance tests for
 |
| each requirement
 |
| </li>
 |
| <li>
 |
| <strong>Priority:</strong> Defines the order in which those backlog items will be developed, according to the value
 |
| that they bring to Customers and users, which provides the team with a Product Backlog ready for Sprint/Iteration
 |
| planning
 |
| </li>
 |
| <li>
 |
| <strong>Goal:</strong> Defines the release goals and makes decisions concerning release planning
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| The Product Owner has the following responsibilities:
 |
| </p>
 |
| <ul class="noindent">
 |
| <li>
 |
| Define the features of the product
 |
| </li>
 |
| <li>
 |
| Decide on release date and content
 |
| </li>
 |
| <li>
 |
| Responsible for the profitability of the product (ROI)
 |
| </li>
 |
| <li>
 |
| Prioritize features according to market value
 |
| </li>
 |
| <li>
 |
| Adjust features and priorities as needed
 |
| </li>
 |
| <li>
 |
| Accept or reject work results
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| This person maintains the Product Backlog and ensures that it is visible to everyone. Everyone understands what items
 |
| have the highest priority, so everyone on the development Team knows what will be worked on.
 |
| </p>
 |
| <p>
 |
| The Product Owner is one person, not a committee. Committees may exist that advise or influence this person but team
 |
| members who want to change an item's priority must first convince the Product Owner. In this way, organizational
 |
| methods for setting priorities and requirements are influenced over time by this role.
 |
| </p>
 |
| <p>
 |
| For the Product Owner to succeed, everyone in the organization must respect their decisions. No one is allowed to
 |
| direct the development team member to work from a different set of priorities. Team members are not allowed to follow the direction
 |
| of anyone whose direction does not coincide with the direction provided by the Product Owner. The Product Owner’s
 |
| decisions are visible in the content and prioritization of the Product Backlog. This visibility requires that the
 |
| Product Owner do their best. Visibility makes the role of Product Owner both a demanding and a rewarding experience.
 |
| </p>
 |
| <p>
 |
| The Product Owner is responsible for the first of the three Scrum ceremonies, Sprint/Iteration Planning. The development team evaluates
 |
| the prioritized Product Backlog, identifies the top priority items, and commits to completing the selected items during
 |
| a Sprint/Iteration. These items become the basis for the Sprint/Iteration Backlog.
 |
| </p>
 |
| <p>
 |
| In return for the development team's commitment to completing the selected tasks, the Product Owner commits that they will
 |
| not introduce new requirements to the team during the Sprint/Iteration. Requirements are allowed to change but only outside the
 |
| Sprint/Iteration. After the team begins a Sprint/Iteration, it remains focused on the goals of that Sprint/Iteration. The only exception to this
 |
| rule is that a similar amount of work can be removed from a Sprint/Iteration to accommodate a new requirement.
 |
| </p></mainDescription> |
| <keyConsiderations>The Product Owner's commitment is essential to ensure the project success. By defining the product vision, they provide
 |
| direction to the team. By externally promoting each Sprint/Iteration result, the Product Owner brings recognition and motivation
 |
| to the team.</keyConsiderations> |
| <skills><p>
 |
| The person who plays this role should have the following competencies:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Good knowledge of the business domain
 |
| </li>
 |
| <li>
 |
| Demonstrate leadership and be respected by external stakeholders (Customers and users)
 |
| </li>
 |
| <li>
 |
| Make decisions at the right time (not too soon, not too late)
 |
| </li>
 |
| <li>
 |
| "Open minded" to changes
 |
| </li>
 |
| <li>
 |
| Effective communication skills with the team
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| A former Business Analyst or Project Manager is a good candidate for this role.
 |
| </p></skills> |
| <assignmentApproaches><p>
 |
| Only one person can play this role for each development team. This person must be assigned to the project (the Product
 |
| Owner is a member of the development team and should participate in the Daily Stand-up meeting). The workload
 |
| associated with this role almost requires a full-time assignment.
 |
| </p>
 |
| <p>
 |
| The Product Owner is:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| A single person dedicated to the project who must be available to answer the team's questions promptly to define
 |
| feature tests and provide advice regarding various product aspects (the software UI, for example)
 |
| </li>
 |
| <li>
 |
| An extended member of the team who participates in Sprint/Iteration planning and Sprint/Iteration review meetings
 |
| </li>
 |
| <li>
 |
| Typically someone from a Marketing role or a key user in internal development
 |
| </li>
 |
| <li>
 |
| Can be a Customer representative or a Customer proxy
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Suggestions from&nbsp;Ken Schwaber's&nbsp;Scrum Guide:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| The Product Owner can be a Team member, and in addition perform development work. This additional responsibility
 |
| may affect the Product Owner’s ability to work with stakeholders. However, the Product Owner can never be the
 |
| ScrumMaster.
 |
| </li>
 |
| <li>
 |
| For commercial development, the Product Owner may be the product manager. For in-house development efforts, the
 |
| Product Owner can be the manager of the business function that is being automated.
 |
| </li>
 |
| </ul></assignmentApproaches> |
| </org.eclipse.epf.uma:RoleDescription> |
