Lists rock. They’re even better when someone has put together an awesome list for public consumption. Upon thinking about how to better use your product backlog as a Product Owner, consider the following helpful guidelines [distilled for a quicker read].
Top Ten Backlog Tips
- One product at a time – Derive your product backlog from the product vision or the product roadmap.
- Detailed – Make your product backlog as detailed as possible.
- Be structured – Group similar items items into themes.
- Visible – Put your backlog up on the wall.
- Focused backlog – Start with many, but have the courage to weed out other items over time.
- Capture functional requirements – Start with large, coarse-grained stories and progressively decompose them over time into detailed ones utilizing customer feedback.
- Start with risky stories first – Use risk/uncertainty, dependencies and releasability to decide how soon an item should be implemented. Addressing risky items early on allows you to fail fast.
- Manage global nonfunctional requirements carefully – Describe them precisely upfront. Capture operational qualities such as performance, robustness and interoperability as constraints; describe usability requirements visually, for instance in form of sketches, mock-ups, and screen shots.
- Housekeeping – Groom your product backlog regularly and collaboratively. Run weekly grooming workshops with the team to ensure that your backlog is in good shape. Involve stakeholders including customers and users as appropriate.
- Be ready – Make sure the top items are always “ready:” clear, feasible, and testable. This allows the items to flow into the sprint and facilitates a firm commitment.
[VIA: Roman Pichler]