…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.
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.
✣ ✣ ✣
- 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
|Author||Jeff Sutherland +|
|Goal||do the right things (a.k.a. effectiveness} +|
|Pearl||Triage +, Story map +, Product backlog +, Development team +, Product backlog item +, Product owner +, Release plan +, Roadmap +, Futurelog +, Whish list + and Product wish list +|
|So||Create a single ordered list of items to do, with crystal clear acceptance criteria. +|
|Theme||Agile +, Scrum + and Product +|
|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. +|