Difference between revisions of "Product owner"
Jump to navigation
Jump to search
(Added some notes.) |
(Added some notes.) |
||
Line 1: | Line 1: | ||
Product ownership as it is often interpreted requires a polymath, since a {{p|product owner}} is: | Product ownership as it is often interpreted requires a polymath, since a {{p|product owner}} is: | ||
*Entrepreneur | *'''Entrepreneur''' | ||
*Business Expert | *Business Expert | ||
*Product Manager | *Product Manager | ||
Line 13: | Line 13: | ||
Effective real-world {{p|product owner}}s collaborate with their {{p|development team}}s to do most of this.
But how does it work? | Effective real-world {{p|product owner}}s collaborate with their {{p|development team}}s to do most of this.
But how does it work? | ||
==Key Succes Factors== | |||
For success, a {{p|product owner}} must be: | For success, a {{p|product owner}} must be: | ||
#'''Empowered'''—Able to make decisions, guide and push back on stakeholders. Delays in decision making slow down the team. | #'''Empowered'''—Able to make decisions, guide and push back on stakeholders. Delays in decision making slow down the team. | ||
Line 18: | Line 19: | ||
#'''Available'''—Able to work with the {{p|development team}}s quickly, or customer to understand needs. When split across multiple initiatives, you are unable to fully focus. | #'''Available'''—Able to work with the {{p|development team}}s quickly, or customer to understand needs. When split across multiple initiatives, you are unable to fully focus. | ||
==Product Owner Crew== | |||
A {{p|product owner}} represents many constituents with a single voice. Busy {{p|product owner}}s need not—and should not—act alone. Often, a {{p|product owner}} assembles a {{p|product owner crew}} that includes roles that might assist like: | A {{p|product owner}} represents many constituents with a single voice. Busy {{p|product owner}}s need not—and should not—act alone. Often, a {{p|product owner}} assembles a {{p|product owner crew}} that includes roles that might assist like: | ||
*'''Business Analysts''' help to define business needs and elaborate them for the rest of the Team. | *'''Business Analysts''' help to define business needs and elaborate them for the rest of the Team. | ||
Line 24: | Line 25: | ||
*'''User Experience Experts''' and marketing resources help to elicit and explain end user needs and desires. | *'''User Experience Experts''' and marketing resources help to elicit and explain end user needs and desires. | ||
==Daily Scrum== | |||
As {{p|product owner}}, your primary goals during the {{p|daily scrum}} include: | |||
*'''Listening!'''—This is your clearest window into detailed progress. | |||
*'''Addressing Team Issues''' that fall within your sphere of influence. | |||
*'''Gauge Visual Clues''' on the {{p|scrum wall}} like a flatliner on the {{p|burndown chart}}. | |||
*'''Providing your own status and issues''', where appropriate. | |||
==Product Owner Excellence== | |||
As {{p|product owner}}… | As {{p|product owner}}… | ||
{|rules="none" | {|rules="none" |
Revision as of 16:05, 29 February 2012
Product ownership as it is often interpreted requires a polymath, since a product owner is:
- Entrepreneur
- Business Expert
- Product Manager
- Internal Customer Representative
- Technology Expert
- User Experience Expert
- Subject Matter Expert
- Designer
- Communicator
- Decision Maker
Effective real-world product owners collaborate with their development teams to do most of this. But how does it work?
Key Succes Factors
For success, a product owner must be:
- Empowered—Able to make decisions, guide and push back on stakeholders. Delays in decision making slow down the team.
- Qualified—Experienced in the product domain, the development technology, process and practices, and core personal skills.
- Available—Able to work with the development teams quickly, or customer to understand needs. When split across multiple initiatives, you are unable to fully focus.
Product Owner Crew
A product owner represents many constituents with a single voice. Busy product owners need not—and should not—act alone. Often, a product owner assembles a product owner crew that includes roles that might assist like:
- Business Analysts help to define business needs and elaborate them for the rest of the Team.
- Developers provide available execution paths and describe their respective costs and benefits.
- User Experience Experts and marketing resources help to elicit and explain end user needs and desires.
Daily Scrum
As product owner, your primary goals during the daily scrum include:
- Listening!—This is your clearest window into detailed progress.
- Addressing Team Issues that fall within your sphere of influence.
- Gauge Visual Clues on the scrum wall like a flatliner on the burndown chart.
- Providing your own status and issues, where appropriate.
Product Owner Excellence
As product owner…
You ought to | Own, elaborate and communicate the product vision
|
Formulate the unity of purpose
| |
Limit yourself to tell what needs to be done.
| |
Explain why it needs to be done.
| |
Order product backlog items according to market and user value.
| |
Choose what and when to release.
| |
Create and garden vibrant personas.
| |
Prepare and refine user stories until they are ready to build.
| |
Groom the product backlog based on feedback and changing conditions.
| |
Keep a short, iterative, sustainable, and predictable design cycle.
| |
Perform acceptance tests to meet the criteria of ready to ship.
| |
You ought not to | Manage the work of others
|
Tell anyone how to do their job.
| |
Create your product in a vacuum.
| |
Lose sight of the purpose behind your product.
| |
You should | Identify key moments to present your results.
|
Involve interaction design appropriately.
| |
Leverage and archive existing prototypes.
| |
Perform regular usability tests.
| |
You should not | Solicit feedback from too wide an audience.
|
Drown in detail.
|