Difference between revisions of "Product backlog"
Jump to navigation
Jump to search
(Added two sources.) |
(+= backlog consists of goals) |
||
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{Oyster | {{Oyster | ||
|goal=do the right things (a.k.a. effectiveness} | |||
|stage=Germ | |stage=Germ | ||
|theme=Agile, Scrum | |theme=Agile, Scrum, Product | ||
|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 | |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. | ||
|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 | |background=Backlog consists of goals: | ||
*Enables multiple approaches. | |||
*Facilitates proper situational {{p|triage}}. | |||
*Fuels the right conversations. | |||
*Builds common understanding. | |||
|therefore full=Create a {{p|story map}} with ordered slices of deliverables. 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. | ||
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== | |||
*[[product backlog ordering]] | |||
==To process== | ==To process== | ||
*Should be renamed to {{p|futurelog}} or {{p|whish list}} or even {{p|product wish list}} | |||
*A potential increment will be prioritized based on ‘stakeholder value for costs’, with ‘respect to risk’—Tom & Kai Gilb. | *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 | *Geoffry Moore: value graph: market cap discounted for risk | ||
*http://agilebench.com/blog/the-product-backlog-for-agile-teams | *http://agilebench.com/blog/the-product-backlog-for-agile-teams | ||
{{tag|product backlog}} | |||
{{tag|product}} | |||
{{Source | {{Source | ||
|source=ScrumPlop | |source=ScrumPlop | ||
Latest revision as of 11:36, 2 December 2016
…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.
Backlog consists of goals:
- Enables multiple approaches.
- Facilitates proper situational triage.
- Fuels the right conversations.
- Builds common understanding.
Therefore:
Create a story map with ordered slices of deliverables. 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
- Should be renamed to futurelog or whish list or even product wish list
- 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