<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Scrum on Software Engineering Thoughts</title><link>https://software.skipoles.co.uk/tags/scrum/</link><description>Recent content in Scrum on Software Engineering Thoughts</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 08 Sep 2023 13:44:19 +0100</lastBuildDate><atom:link href="https://software.skipoles.co.uk/tags/scrum/index.xml" rel="self" type="application/rss+xml"/><item><title>The Confusion Between Scrum and Agile</title><link>https://software.skipoles.co.uk/posts/confusion-between-scrum-and-agile/</link><pubDate>Fri, 08 Sep 2023 13:44:19 +0100</pubDate><guid>https://software.skipoles.co.uk/posts/confusion-between-scrum-and-agile/</guid><description>&lt;p&gt;More and more I am reading about, and experiencing, organisations who have adopted &amp;ldquo;Scrum&amp;rdquo; as their
process, but are complaining that they aren&amp;rsquo;t achieving any of the benefits that they expected from
&amp;ldquo;going agile&amp;rdquo;. This often manifests itself in broad claims that agile is a failure as a methodology.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ve come to believe that there is a fundamental misunderstanding around what agile actually is,
how it is supposed to help, and in particular how it relates to Scrum. In this post I want to try
to address this confusion.&lt;/p&gt;</description></item></channel></rss>