While it’s normal that a product backlog changes, some backlogs grow too big and become overly long and detailed. Consequently, they are difficult to update, prioritise, and refine. The following tips help you simplify such a backlog so you can manage with it more easily.
If you grew up as a teenager in the 1980s like me, you are probably familiar with the quote “There can only be one” from the first Highlander movie. Interestingly, this statement is also true for product owners: There should only be one product owner per product. But don’t worry: You don’t have to become an immortal warrior to understand the Highlander principle. Reading this blog post will do the trick.
“Which project is best suited to pilot Agile?” is a question I get regularly asked. This blog post discusses the following six criteria that help you select the right agile pilot project: small, important, independent, collocated, software only, and new product development.
The product backlog is meant to be a simple tool that allows product owners to express detailed product decisions and direct the work of the development team. But in practice, product backlogs can grow big and become large and unwieldy. Break up your product backlog can address this issue, as this article explains.