http://blog.marko-apfel.de/tags/scrum/Recent content in Scrum on Marko ApfelHugoen-USThu, 05 Mar 2026 17:39:07 +0100http://blog.marko-apfel.de/posts/how-to-use-requirement-feature-pbi-and-task-hierarchies-effectively/Thu, 05 Mar 2026 17:39:07 +0100http://blog.marko-apfel.de/posts/how-to-use-requirement-feature-pbi-and-task-hierarchies-effectively/<p>When an initiative spans multiple releases, organizing its backlog can become surprisingly difficult.</p> <p>Imagine a larger product capability that starts with an MVP and is extended release by release. Given an <em>Azure DevOps</em> hierarchy such as:</p>http://blog.marko-apfel.de/posts/slicing-crud-related-activities-into-separate-backlog-items/Thu, 25 Sep 2025 08:05:07 +0200http://blog.marko-apfel.de/posts/slicing-crud-related-activities-into-separate-backlog-items/<p>A common question during backlog refinement is whether closely related CRUD operations should be implemented within a single Product Backlog Item (PBI) or split into multiple work items.</p> <p>At first glance, grouping <strong>create</strong>, <strong>rename</strong>, and <strong>delete</strong> operations together seems reasonable. They all operate on the same entity and appear to belong to the same feature.</p>