View source for Product backlog

{{Oyster
|goal=do the right things
|stage=Germ
|theme=Agile, Scrum
|context=you have defined a business segment that will be supported by one or more teams that need strategic technical direction.
|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.
|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 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.

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==
*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

{{tag|product backlog}}

{{tag|product}}
{{Source
|source=ScrumPlop
|author=Jeff Sutherland
|coder={{mvs}}
|pattern=product backlog
|web=https://sites.google.com/a/scrumplop.org/published-patterns/value-stream-pattern-language/product-backlog
|title=ScrumPlop
}}