<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="https://elezea.com/wp-content/themes/elz_2023/styles/pretty-feed-v3.xsl" type="text/xsl"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  xmlns:slash="http://purl.org/rss/1.0/modules/slash/" >
  <channel>
    <title>Elezea by Rian van der Merwe - RSS Feed</title>
    <atom:link href="https://elezea.com/2019/05/agile-is-not-just-for-software-development/feed/" rel="self" type="application/rss+xml" />
    <link>https://elezea.com/2019/05/agile-is-not-just-for-software-development/</link>
    <description>A personal blog about product, technology, and interesting things that are worth sharing.</description>
    <lastBuildDate>Thu, 02 Apr 2026 17:43:52 +0000</lastBuildDate>
    <language></language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <generator>https://wordpress.org/?v=6.9.4</generator>
          <item>
        <title>“Agile” is not just for software development, it’s for the whole business</title>
        <link>https://elezea.com/2019/05/agile-is-not-just-for-software-development/</link>
        <pubDate>Wed, 29 May 2019 00:00:00 +0000</pubDate>
        <dc:creator>Rian van der Merwe</dc:creator>
        <guid isPermaLink="false">https://elezea.com/?p=7120</guid>
        <description>
          <![CDATA[Why restricting agile to software development is such a big problem.]]>
        </description>
        <content:encoded>
          <![CDATA[<p>Steve Denning’s Forbes essay <a href="https://www.forbes.com/sites/stevedenning/2019/05/23/understanding-fake-agile/#1fbecf894bbe">Understanding Fake Agile</a> is the most useful thing I’ve read about the state of Agile in a long time. It starts off extremely strong, with his “three laws of Agile”:</p>
<blockquote>
<ul>
<li><strong>The Law of the Customer</strong> — an obsession with delivering value to customers as the be-all and end-all of the organization.</li>
<li><strong>The Law of the Small Team</strong> — a presumption that all work be carried out by small self-organizing teams, working in short cycles and focused on delivering value to customers—and</li>
<li><strong>The Law of the Network</strong> — a continuing effort to obliterate  bureaucracy and top-down hierarchy so that the firm operates as an interacting network of teams, all focused on working together to deliver increasing value to customers.</li>
</ul>
</blockquote>
<p>Note that there’s no mention of <em>software</em> in those laws. This goes <em>way</em> beyond the original <a href="https://agilemanifesto.org/">Agile Manifesto</a>, and the idea that Agile is for software only:</p>
<blockquote>
<p>But restricting agile to software development becomes a problem. When agile thinking takes over software development in a traditionally managed organization, it inevitably begins to run into conflict with other parts of the organization that are moving less rapidly and less flexibly.</p>
</blockquote>
<p>This is how you get organizations that follow an agile process for their <em>development</em> process, while the rest of the organization still operates in silos. Steve discusses many of the other misconceptions and problems with Agile in his post.</p>
          <br>
          <br>
          <hr>
          Thanks for still believing in RSS! Get in touch <a href="https://elezea.com/contact">here</a> if you'd like.]]>
        </content:encoded>
                      </item>
      </channel>
</rss>