<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Scrum on The Dangling Pointer</title><link>https://aaron.blog/tags/scrum/</link><description>Recent content in Scrum on The Dangling Pointer</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 18 Apr 2014 14:29:14 +0000</lastBuildDate><atom:link href="https://aaron.blog/tags/scrum/index.xml" rel="self" type="application/rss+xml"/><item><title>Agility Not Agile Development</title><link>https://aaron.blog/agility-not-agile-development/</link><pubDate>Fri, 18 Apr 2014 14:29:14 +0000</pubDate><guid>https://aaron.blog/agility-not-agile-development/</guid><description>&lt;p&gt;Dave Thomas has a really excellent post about how &lt;a href="http://pragdave.me/blog/2014/03/04/time-to-kill-agile/" rel="noopener"&gt;it's time to kill Agile&lt;/a&gt;.  It's a very well thought out post and it embodies a lot of my concerns with the movement.  I have a few insights to add to his perspective.&lt;/p&gt;&lt;p&gt;I was a software engineer consultant for over five years.  The Java and open-source community had adopted Agile and implementations like Scrum and XP fairly quickly.  It made us find the way to get software that was good out the door in a timely fashion.  It made us not sit on our asses collecting requirements for months before any real work was done.  I worked on a very successful search project at a Fortune 500 company following Agile methods loosely based on Scrum.  I still believe to this day the level of success was due to the project being in "skunkworks" and therefore having a simplified budget and leaving us in control of the moving parts.  Once that project got into a normal budgeting process, innovation floundered.&lt;/p&gt;</description></item></channel></rss>