<?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/"
		>
<channel>
	<title>Comments on: Iterative development is not unplanned development</title>
	<atom:link href="http://www.stellman-greene.com/2009/07/16/iterative-development-is-not-unplanned-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.stellman-greene.com/2009/07/16/iterative-development-is-not-unplanned-development/</link>
	<description>because people want their software to work</description>
	<lastBuildDate>Thu, 19 Jan 2012 02:40:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: denovich</title>
		<link>http://www.stellman-greene.com/2009/07/16/iterative-development-is-not-unplanned-development/comment-page-1/#comment-2228</link>
		<dc:creator>denovich</dc:creator>
		<pubDate>Thu, 16 Jul 2009 15:00:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.stellman-greene.com/?p=298#comment-2228</guid>
		<description>The analogy that came to me while reading this is of GTD: Getting Things Done (a todo-list management strategy.)

There isn&#039;t any real magic to it.  It&#039;s main feature is that it&#039;s simple enough to follow.  If you just follow the rules, you are almost assured of better than average results.  Since we all don&#039;t live on Lake Wobegon, above average is more than good enough.  The only problem:  You still have to do the items on your list!

Agile processes are very similar in that regard.  They tend to be simple enough for most teams to follow (at an acceptable cost in effort) while at the same time encouraging good habits and discouraging bad habits.  It does not transmute bad programmers/managers/customers into good ones...  It will help protect you from benign neglect/apathy/inertia, but it&#039;s no match for sustained stupidity or ignorance.</description>
		<content:encoded><![CDATA[<p>The analogy that came to me while reading this is of GTD: Getting Things Done (a todo-list management strategy.)</p>
<p>There isn&#8217;t any real magic to it.  It&#8217;s main feature is that it&#8217;s simple enough to follow.  If you just follow the rules, you are almost assured of better than average results.  Since we all don&#8217;t live on Lake Wobegon, above average is more than good enough.  The only problem:  You still have to do the items on your list!</p>
<p>Agile processes are very similar in that regard.  They tend to be simple enough for most teams to follow (at an acceptable cost in effort) while at the same time encouraging good habits and discouraging bad habits.  It does not transmute bad programmers/managers/customers into good ones&#8230;  It will help protect you from benign neglect/apathy/inertia, but it&#8217;s no match for sustained stupidity or ignorance.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

