Product Worker: How do you deal with the backlog items of various granularity?

The product is a continuous challenge for the backlog items from granularity, or small -goal, product owner. Sometimes product backlog items are very large or you are suffering from a lot of additional administrative functions, as the entire packages on small items have to be reprimanded again and again. The central theme of this podcast sequence is the size of a backlog item.

Advertisement

Conscious operation of granulation

While the scum guide only demands that entries should be completed within a sprint, dominic winter and oliver winter recommend an additional rule: an item should not take more than half of the sprint. This thumb rule helps reduce the risk that a single item moves throughout the sprint and has very little scope for adjustment. But granularity is not only a question of the plan, but also a long product strategy. Items, which are only relevant in the distant future, can initially be prepared roughly. Close to the date of implementation, it is equally defined.

Oliver Winter emphasizes that very early detailing is often luxurious because preferences change over time. Summary and re -notice of objects can therefore be useful as a bite of large entries. Another theme is the handling of granularity in the sprint. This is not a problem of different sizes within a sprint until you provide all additional values ​​and understand the team connection. A healthy mixture of small, medium and large items can also help improve better learning and improve forecast. A backlog based on the same big entries – like one in Some things-Prochering is required, although prediction may increase, but may restrict flexibility.

The discussion shows that the product owner should consume the granularity of his backlog items consciously. Recognition activities are necessary to ensure that the team has a general understanding. However, the difference also requires courage: not to prepare each item for the smallest detail. Especially with very small reforms, it may make it more understandable to apply them directly rather than carrying them to the backlog. Ultimately, optimal granulation always depends on the related product and team. The product owner should know that they are not only responsible for the material of the backlog, but also for its structure and manualta.

The current version of the podcast is also available in the product worker’s blog: “How do you deal with the backlog items of various granularity?,

Most Gitops: Continuous delivery is good, progressive distribution is better

(May)