TL;DR: 28 Product Backlog and Refinement Anti-Patterns
Scrum is a practical framework to build products, provided you identify in advance what to build. But even after a successful product discovery phase, you may struggle to make the right thing in the right way if your product backlog is not up to the job. Garbage in, garbage out – as the saying goes. The following article points at 28 of the most common product backlog anti-patterns – including the product backlog refinement process – that limit your Scrum team’s success.
Product Backlog Refinement—TL;DR
Where to start when kicking-off an agile transition?
Usually, tools and processes are smallest the common denominator among all participants, as they are at the core of the grand scheme of agile things.
It is a rare occasion that you start from scratch with a brand-new team without an existing product, probably even in a more or less nascent organization, for example, a startup.
In most cases, an existing product delivery organization with available products, and services will go “agile“. In this case, turning attention to the available product backlog is a pragmatic first step. The following process describes what aspects need to be attended to optimize the outcome.