<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Agile Product Development on MYLES — Strategy &amp; Innovation Consulting</title><link>https://myles-innovation.com/tags/agile-product-development/</link><description>Recent content in Agile Product Development on MYLES — Strategy &amp; Innovation Consulting</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 01 Mar 2026 00:00:00 +0100</lastBuildDate><atom:link href="https://myles-innovation.com/tags/agile-product-development/index.xml" rel="self" type="application/rss+xml"/><item><title>Agile Product Development with a Focus on Customer Outcomes</title><link>https://myles-innovation.com/blog/agile-product-development-customer-outcomes/</link><pubDate>Sun, 01 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/agile-product-development-customer-outcomes/</guid><description>&lt;h2 id="agile-without-outcomes-is-just-fast-wrong"&gt;Agile Without Outcomes Is Just Fast Wrong&lt;/h2&gt;
&lt;p&gt;The promise of agile product development was compelling: shorter cycles, faster feedback, less waste from building the wrong things. Two decades after the Agile Manifesto, most software product teams work in some variant of agile. A growing proportion of hardware and industrial product teams have adopted agile-inspired elements. And yet the failure rate for product development — the proportion of products that fail to achieve meaningful market adoption — has not improved materially.&lt;/p&gt;</description></item></channel></rss>