<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Product Backlog on Marko Apfel</title><link>http://blog.marko-apfel.de/tags/product-backlog/</link><description>Recent content in Product Backlog on Marko Apfel</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 02 Dec 2025 08:29:07 +0100</lastBuildDate><atom:link href="http://blog.marko-apfel.de/tags/product-backlog/index.xml" rel="self" type="application/rss+xml"/><item><title>Slicing CRUD-Related Activities into Separate Backlog Items</title><link>http://blog.marko-apfel.de/posts/slicing-crud-related-activities-into-separate-backlog-items/</link><pubDate>Thu, 25 Sep 2025 08:05:07 +0200</pubDate><guid>http://blog.marko-apfel.de/posts/slicing-crud-related-activities-into-separate-backlog-items/</guid><description>&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;At first glance, grouping &lt;strong&gt;create&lt;/strong&gt;, &lt;strong&gt;rename&lt;/strong&gt;, and &lt;strong&gt;delete&lt;/strong&gt; operations together seems reasonable. They all operate on the same entity and appear to belong to the same feature.&lt;/p&gt;</description></item></channel></rss>