Difference between revisions of "Product owner"
Jump to navigation
Jump to search
(Added “You should (not)“.) |
({{p|sprint review meeting}} Demo or die!) |
||
Line 64: | Line 64: | ||
|align="right" valign="top"|<span style="color:{{pearlblue}};">'''You should'''</span> | |align="right" valign="top"|<span style="color:{{pearlblue}};">'''You should'''</span> | ||
|'''Identify key moments to present your results.''' | |'''Identify key moments to present your results.''' | ||
:...starting with {{p|storyboard scenarios}}, demonstrate the evolving product at the end of each {{p|sprint}}, soliciting feedback from key stakeholders. Keep everyone excited and interested. Decide on how the feedback will be reflected in the {{p|product backlog}}. | :...starting with {{p|storyboard scenarios}}, demonstrate the evolving product at the end of each {{p|sprint}} during the {{p|sprint review meeting}}, soliciting feedback from key stakeholders. Keep everyone excited and interested. Decide on how the feedback will be reflected in the {{p|product backlog}}. Demo or die! | ||
|- | |- | ||
| | | | ||
Line 77: | Line 77: | ||
|'''Perform regular {{p|usability test}}s.''' | |'''Perform regular {{p|usability test}}s.''' | ||
:…regular and affordable {{p|usability test}}s where the whole team watches someone use your product are often eye-opening. Observe… Do they get it? Can they find their way around? Expect head slappers, shocks, inspiration, and passion. Brace yourself, yet do not panic. | :…regular and affordable {{p|usability test}}s where the whole team watches someone use your product are often eye-opening. Observe… Do they get it? Can they find their way around? Expect head slappers, shocks, inspiration, and passion. Brace yourself, yet do not panic. | ||
|- | |- | ||
|align="right" valign="top"|<span style="color:{{pearlblue}};">'''You should not'''</span> | |align="right" valign="top"|<span style="color:{{pearlblue}};">'''You should not'''</span> |
Revision as of 11:50, 29 February 2012
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.
|