<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: The death of agile</title>
	<atom:link href="http://mikebroberts.com/2009/11/02/the-death-of-agile/feed/" rel="self" type="application/rss+xml" />
	<link>http://mikebroberts.com/2009/11/02/the-death-of-agile/</link>
	<description>Mike Roberts on Life &#38; Technology</description>
	<lastBuildDate>Sun, 07 Aug 2011 20:25:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Zoe Smith</title>
		<link>http://mikebroberts.com/2009/11/02/the-death-of-agile/#comment-371</link>
		<dc:creator><![CDATA[Zoe Smith]]></dc:creator>
		<pubDate>Mon, 07 Mar 2011 16:29:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikebroberts.com/blogtastic/?p=239#comment-371</guid>
		<description><![CDATA[Well, well - amazing that my brother and I land up on the same page sometimes.

Mike, don&#039;t know if you remember the somewhat tortuous title of my MBA dissertation - &#039;multi paradigm multi methodologies as a method of managing IT projects&#039;?!  What this is about is that we can look at using both hard and soft paradigms as a means of managing IT projects - and maybe a combination of both is better at different stages of the SDLC (whether or not we&#039;re waterfall, agile etc).  There are some great techniques and approaches out there (including Agile, Kanban and other softer approaches) but in my humble opinion, the good project manager should be able to:

1) Select the methodologies most appropriate for the project under development at a particular point in time based on a variety of criteria.  These would include scope, organisational culture, objectives, resources (both personalities and constraints) etc.

2) Implement those methodologies throughout the project&#039;s lifecycle at the most appropriate time because that&#039;s what suits - and not because that&#039;s what some Quality Manual says you have to.  (Which, as a QA manager, feels a little odd).

What I want to say is, that as an industry, we need to &#039;professionalise&#039; ourselves, and we can learn a good deal from our colleagues in Operations Research.  We may be the new kids on the block, but that block wasn&#039;t build yesterday.]]></description>
		<content:encoded><![CDATA[<p>Well, well &#8211; amazing that my brother and I land up on the same page sometimes.</p>
<p>Mike, don&#8217;t know if you remember the somewhat tortuous title of my MBA dissertation &#8211; &#8216;multi paradigm multi methodologies as a method of managing IT projects&#8217;?!  What this is about is that we can look at using both hard and soft paradigms as a means of managing IT projects &#8211; and maybe a combination of both is better at different stages of the SDLC (whether or not we&#8217;re waterfall, agile etc).  There are some great techniques and approaches out there (including Agile, Kanban and other softer approaches) but in my humble opinion, the good project manager should be able to:</p>
<p>1) Select the methodologies most appropriate for the project under development at a particular point in time based on a variety of criteria.  These would include scope, organisational culture, objectives, resources (both personalities and constraints) etc.</p>
<p>2) Implement those methodologies throughout the project&#8217;s lifecycle at the most appropriate time because that&#8217;s what suits &#8211; and not because that&#8217;s what some Quality Manual says you have to.  (Which, as a QA manager, feels a little odd).</p>
<p>What I want to say is, that as an industry, we need to &#8216;professionalise&#8217; ourselves, and we can learn a good deal from our colleagues in Operations Research.  We may be the new kids on the block, but that block wasn&#8217;t build yesterday.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anness</title>
		<link>http://mikebroberts.com/2009/11/02/the-death-of-agile/#comment-291</link>
		<dc:creator><![CDATA[Anness]]></dc:creator>
		<pubDate>Sat, 13 Mar 2010 02:08:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikebroberts.com/blogtastic/?p=239#comment-291</guid>
		<description><![CDATA[Interesting post Mike. I work with companies that are just implementing Agile or are adding to the current Agile practices they already have in place. Many companies are still stuck in a rut when it comes to implementing Agile, and so I&#039;m not to surprised that the Agile 2xxx confs had tracks for newbies. As Seth Godin says, we will always be dealing with new people, so producing content on the basics for these folks is a necessity. On the tools and pseudo-agile consulting firms, I see that in many areas of tech, so it was bound to happen with Agile. Companies are going to need to look at how well their current tools and methods work, where they need to be improved, and either go that route or choose a tool that will work better to meet their goals. And for people complaining about the current state of Agile, I&#039;m glad I don&#039;t talk with those people. That gets old real fast.

I don&#039;t think Agile, or at least not Agile principles, is dead. I see more companies going down the road. Ultijately all their goals are the same - better transparency into projects, predicable delivery, and faster dekivery of value to customers. Agile is one way to help these things happen.

And whether or not there is a glut of consultants or not weighing down the community, Agile has laid a foundation that we can all build on.;]]></description>
		<content:encoded><![CDATA[<p>Interesting post Mike. I work with companies that are just implementing Agile or are adding to the current Agile practices they already have in place. Many companies are still stuck in a rut when it comes to implementing Agile, and so I&#39;m not to surprised that the Agile 2xxx confs had tracks for newbies. As Seth Godin says, we will always be dealing with new people, so producing content on the basics for these folks is a necessity. On the tools and pseudo-agile consulting firms, I see that in many areas of tech, so it was bound to happen with Agile. Companies are going to need to look at how well their current tools and methods work, where they need to be improved, and either go that route or choose a tool that will work better to meet their goals. And for people complaining about the current state of Agile, I&#39;m glad I don&#39;t talk with those people. That gets old real fast.</p>
<p>I don&#39;t think Agile, or at least not Agile principles, is dead. I see more companies going down the road. Ultijately all their goals are the same &#8211; better transparency into projects, predicable delivery, and faster dekivery of value to customers. Agile is one way to help these things happen.</p>
<p>And whether or not there is a glut of consultants or not weighing down the community, Agile has laid a foundation that we can all build on.;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julian Simpson</title>
		<link>http://mikebroberts.com/2009/11/02/the-death-of-agile/#comment-289</link>
		<dc:creator><![CDATA[Julian Simpson]]></dc:creator>
		<pubDate>Fri, 22 Jan 2010 15:36:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikebroberts.com/blogtastic/?p=239#comment-289</guid>
		<description><![CDATA[Agile is a good development methodology, maybe the best, but its just a dev method and the danger of quick iterations is the possibility of missing the goal &amp; or increasing disorganization as complexity increases. That&#039;s where a clever bunch of people comes in handy, because they hold it together. If you put a clever bunch of people together then it increases the chance of success...well done to the people who made a shed load of cash of being more competitive than other people who were less creative, intelligent and savvy. However, it still takes huge amounts of cash to do development work and Agile doesn&#039;t do much that is new to remove the risks of failure in IT projects.]]></description>
		<content:encoded><![CDATA[<p>Agile is a good development methodology, maybe the best, but its just a dev method and the danger of quick iterations is the possibility of missing the goal &amp; or increasing disorganization as complexity increases. That&#8217;s where a clever bunch of people comes in handy, because they hold it together. If you put a clever bunch of people together then it increases the chance of success&#8230;well done to the people who made a shed load of cash of being more competitive than other people who were less creative, intelligent and savvy. However, it still takes huge amounts of cash to do development work and Agile doesn&#8217;t do much that is new to remove the risks of failure in IT projects.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Dempsey</title>
		<link>http://mikebroberts.com/2009/11/02/the-death-of-agile/#comment-277</link>
		<dc:creator><![CDATA[Robert Dempsey]]></dc:creator>
		<pubDate>Tue, 03 Nov 2009 20:34:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikebroberts.com/blogtastic/?p=239#comment-277</guid>
		<description><![CDATA[Interesting post Mike. I work with companies that are just implementing Agile or are adding to the current Agile practices they already have in place. Many companies are still stuck in a rut when it comes to implementing Agile, and so I&#039;m not to surprised that the Agile 2xxx confs had tracks for newbies. As Seth Godin says, we will always be dealing with new people, so producing content on the basics for these folks is a necessity. On the tools and pseudo-agile consulting firms, I see that in many areas of tech, so it was bound to happen with Agile. Companies are going to need to look at how well their current tools and methods work, where they need to be improved, and either go that route or choose a tool that will work better to meet their goals. And for people complaining about the current state of Agile, I&#039;m glad I don&#039;t talk with those people. That gets old real fast.

I don&#039;t think Agile, or at least not Agile principles, is dead. I see more companies going down the road. Ultimately all their goals are the same - better transparency into projects, predicable delivery, and faster delivery of value to customers. Agile is one way to help these things happen.

And whether or not there is a glut of consultants or not weighing down the community, Agile has laid a foundation that we can all build on.]]></description>
		<content:encoded><![CDATA[<p>Interesting post Mike. I work with companies that are just implementing Agile or are adding to the current Agile practices they already have in place. Many companies are still stuck in a rut when it comes to implementing Agile, and so I&#8217;m not to surprised that the Agile 2xxx confs had tracks for newbies. As Seth Godin says, we will always be dealing with new people, so producing content on the basics for these folks is a necessity. On the tools and pseudo-agile consulting firms, I see that in many areas of tech, so it was bound to happen with Agile. Companies are going to need to look at how well their current tools and methods work, where they need to be improved, and either go that route or choose a tool that will work better to meet their goals. And for people complaining about the current state of Agile, I&#8217;m glad I don&#8217;t talk with those people. That gets old real fast.</p>
<p>I don&#8217;t think Agile, or at least not Agile principles, is dead. I see more companies going down the road. Ultimately all their goals are the same &#8211; better transparency into projects, predicable delivery, and faster delivery of value to customers. Agile is one way to help these things happen.</p>
<p>And whether or not there is a glut of consultants or not weighing down the community, Agile has laid a foundation that we can all build on.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

