<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Agile on MYLES — Strategy &amp; Innovation Consulting</title><link>https://myles-innovation.com/tags/agile/</link><description>Recent content in Agile on MYLES — Strategy &amp; Innovation Consulting</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 06 Mar 2026 00:00:00 +0100</lastBuildDate><atom:link href="https://myles-innovation.com/tags/agile/index.xml" rel="self" type="application/rss+xml"/><item><title>JTBD vs. User Stories: When to Use Which</title><link>https://myles-innovation.com/blog/jtbd-vs-user-stories/</link><pubDate>Fri, 06 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/jtbd-vs-user-stories/</guid><description>&lt;h2 id="a-false-competition-that-is-costing-product-teams-time"&gt;A False Competition That Is Costing Product Teams Time&lt;/h2&gt;
&lt;p&gt;Every few years, the product management community invents a new thing that is going to replace user stories. Design thinking replaced them. Now JTBD is replacing them. Except user stories keep showing up in sprint planning, and the teams that abandoned them for something more sophisticated often find themselves arguing about what a feature should do without any shared language to resolve the argument.&lt;/p&gt;</description></item></channel></rss>