<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Backlog on Marko Apfel</title><link>http://blog.marko-apfel.de/tags/backlog/</link><description>Recent content in Backlog on Marko Apfel</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 05 Mar 2026 17:39:07 +0100</lastBuildDate><atom:link href="http://blog.marko-apfel.de/tags/backlog/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Use Requirement, Feature, PBI, and Task Hierarchies Effectively</title><link>http://blog.marko-apfel.de/posts/how-to-use-requirement-feature-pbi-and-task-hierarchies-effectively/</link><pubDate>Thu, 05 Mar 2026 17:39:07 +0100</pubDate><guid>http://blog.marko-apfel.de/posts/how-to-use-requirement-feature-pbi-and-task-hierarchies-effectively/</guid><description>&lt;p&gt;When an initiative spans multiple releases, organizing its backlog can become surprisingly difficult.&lt;/p&gt;
&lt;p&gt;Imagine a larger product capability that starts with an MVP and is extended release by release. Given an &lt;em&gt;Azure DevOps&lt;/em&gt; hierarchy such as:&lt;/p&gt;</description></item><item><title>Using Container Requirements to Organize Requirements in Azure DevOps</title><link>http://blog.marko-apfel.de/posts/using-container-requirements-to-organize-requirements-in-azure-devops/</link><pubDate>Wed, 03 Dec 2025 01:51:07 +0100</pubDate><guid>http://blog.marko-apfel.de/posts/using-container-requirements-to-organize-requirements-in-azure-devops/</guid><description>&lt;p&gt;Requirements rarely exist in isolation. As a project grows, related requirements naturally form larger groups around features, architectural areas, business objectives, or other common themes.&lt;/p&gt;
&lt;p&gt;Ideally, the work item hierarchy in &lt;em&gt;Azure DevOps&lt;/em&gt; reflects this structure. But not every &lt;em&gt;Azure DevOps&lt;/em&gt; project provides suitable higher-level work item types such as Initiatives, and changing the process configuration is not always possible or desirable.&lt;/p&gt;</description></item></channel></rss>