<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>MVP on Marko Apfel</title><link>http://blog.marko-apfel.de/tags/mvp/</link><description>Recent content in MVP on Marko Apfel</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 20 Nov 2025 16:49:07 +0100</lastBuildDate><atom:link href="http://blog.marko-apfel.de/tags/mvp/index.xml" rel="self" type="application/rss+xml"/><item><title>Where Does the MVP Belong in an Azure DevOps Backlog Hierarchy?</title><link>http://blog.marko-apfel.de/posts/where-does-the-mvp-belong-in-an-azure-devops-backlog-hierarchy/</link><pubDate>Thu, 20 Nov 2025 16:49:07 +0100</pubDate><guid>http://blog.marko-apfel.de/posts/where-does-the-mvp-belong-in-an-azure-devops-backlog-hierarchy/</guid><description>&lt;p&gt;When a new product capability is implemented incrementally, a common question arises during backlog refinement:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;At which backlog level should the MVP live?&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Consider an Azure DevOps hierarchy consisting of:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;Requirement
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;└── Feature
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; └── PBI
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; └── Task
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The capability may evolve over several releases. The first release provides a &lt;strong&gt;Minimum Viable Product (MVP)&lt;/strong&gt;, while later releases gradually extend it with additional functionality.&lt;/p&gt;</description></item></channel></rss>