Keep a public, written backlog of possible improvements, remedies, tactics or strategies.
- Revise this backlog in regular intervals.
- Define the owner role for this backlog, similar to the product owner in Scrum.
- Enhance the backlog with information from the Evaluate phase, like cost, effort or risk.
Description
Collect all known issues and problems within a system or its associated processes. Make the issues comparable by evaluating each one, usually using economical units like money or time. Align carefully with the issue list.
Content
| ID | Improvement | Description | min cost | max cost | Related issues |
|---|---|---|---|---|---|
| identifier | name | short description of this improvement or remedy | minimal estimated cost or effort | maximal cost or effort | links to related issues |
Representation and tools
Try to use a documentation approach similar to the issue list. It should be as easy as possible to link issues to improvements and vice versa.