<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>agile manifesto on Agile Software Development</title>
    <link>https://agilesoftdev.com/tags/agile-manifesto/</link>
    <description>Recent content in agile manifesto on Agile Software Development</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 02 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://agilesoftdev.com/tags/agile-manifesto/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Agile Is Not Dead — the Cargo Cult Version Deserved to Fail</title>
      <link>https://agilesoftdev.com/agile-is-not-dead-the-cargo-cult-version-deserved-to-fail/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://agilesoftdev.com/agile-is-not-dead-the-cargo-cult-version-deserved-to-fail/</guid>
      <description>The &amp;ldquo;agile is dead&amp;rdquo; argument appears on a reliable cycle, usually authored by someone who spent years watching organizations adopt the ceremonies, terminology, and org charts of agile while preserving the planning assumptions, reporting structures, and risk culture of waterfall. The frustration is legitimate. The conclusion is wrong.
What failed in most organizations was not agile. It was a management consulting product that appropriated agile vocabulary while systematically removing the practices that give agile its value.</description>
    </item>
    
  </channel>
</rss>
