Difference between revisions of "Product backlog"
(So) |
m (terse/full) |
||
| Line 4: | Line 4: | ||
|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 | |goal=do the right things (a.k.a. effectiveness} | ||
|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. | |||
|so=Create a single ordered list of items to do, with crystal clear acceptance criteria. | |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 full=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 full=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}}. | ||
|new=This list typically corresponds to a single product or product line; however, it can be any list of deliverables. | |new=This list typically corresponds to a single product or product line; however, it can be any list of deliverables. | ||
Revision as of 09:20, 16 June 2013
…you have defined a business segment that will be supported by one or more teams that need strategic technical direction.
✣ ✣ ✣
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 product backlog items. The list is called the product backlog. The development team will be driven by the work at the top of the product backlog, and each unit of development staff works from only a single product backlog.
✣ ✣ ✣
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