Difference between revisions of "Product backlog"
Jump to navigation
Jump to search
m (Therefore in a single line → So) |
(So) |
||
| Line 1: | Line 1: | ||
{{Oyster | {{Oyster | ||
|goal=do the right things | |||
|stage=Germ | |stage=Germ | ||
|theme=Agile, Scrum | |theme=Agile, Scrum | ||
|context=you have defined a business segment that will be supported by one or more teams that need strategic technical direction. | |context=you have defined a business segment that will be supported by one or more teams that need strategic technical direction. | ||
|wish in a single line=It is important that everyone agrees to what needs to be done next at any given time, and that the agreement be made visible. | |wish in a single line=It is important that everyone agrees to what needs to be done next at any given time, and that the agreement be made visible. | ||
|so=Create a single ordered list of | |so=Create a single ordered list of items to do, with crystal clear acceptance criteria. | ||
|wish=It is important that everyone agrees to what needs to be done next at any given time, and that the agreement be made visible. You can't do everything at once—in fact, you can't even do two things well at the same time. It's important to have focus. | |wish=It is important that everyone agrees to what needs to be done next at any given time, and that the agreement be made visible. You can't do everything at once—in fact, you can't even do two things well at the same time. It's important to have focus. | ||
|therefore=Create a single ordered list of deliverables called {{pbi}}s. The list is called the {{pb}}. The {{dt}} will be driven by the work at the top of the {{pb}}, and each unit of development staff works from only a single {{pb}}. | |therefore=Create a single ordered list of deliverables called {{pbi}}s. The list is called the {{pb}}. The {{dt}} will be driven by the work at the top of the {{pb}}, and each unit of development staff works from only a single {{pb}}. | ||
| Line 10: | Line 11: | ||
Annotating each {{pbi}} with a cost, and a positionally sensitive market value, can help the {{po}} optimize [[ROI]]. The {{pb}} can also be used to do scheduling and to create a {{rp}} and {{rm}}. | Annotating each {{pbi}} with a cost, and a positionally sensitive market value, can help the {{po}} optimize [[ROI]]. The {{pb}} can also be used to do scheduling and to create a {{rp}} and {{rm}}. | ||
|therefore in a single line=Create a single ordered list of deliverables. | |||
}} | }} | ||
==See also== | ==See also== | ||
| Line 21: | Line 23: | ||
{{tag|product}} | {{tag|product}} | ||
{{Source | {{Source | ||
|source=ScrumPlop | |source=ScrumPlop | ||
Revision as of 19:58, 25 May 2013
…you have defined a business segment that will be supported by one or more teams that need strategic technical direction.
✣ ✣ ✣
{{{wish full}}}
Therefore:
{{{therefore full}}}
✣ ✣ ✣
This list typically corresponds to a single product or product line; however, it can be any list of deliverables.
Annotating each product backlog item with a cost, and a positionally sensitive market value, can help the product owner optimize ROI. The product backlog can also be used to do scheduling and to create a release plan and roadmap.
✣ ✣ ✣
See also
To process
- A potential increment will be prioritized based on ‘stakeholder value for costs’, with ‘respect to risk’—Tom & Kai Gilb.
- Geoffry Moore: value graph: market cap discounted for risk
- http://agilebench.com/blog/the-product-backlog-for-agile-teams