<?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: Rusty Automobiles</title>
	<atom:link href="http://theagileexecutive.com/2009/06/01/rusty-automobiles/feed/" rel="self" type="application/rss+xml" />
	<link>http://theagileexecutive.com/2009/06/01/rusty-automobiles/</link>
	<description>Making Agile Work</description>
	<lastBuildDate>Tue, 10 Apr 2012 21:58:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Paul Brownell</title>
		<link>http://theagileexecutive.com/2009/06/01/rusty-automobiles/#comment-348</link>
		<dc:creator><![CDATA[Paul Brownell]]></dc:creator>
		<pubDate>Tue, 02 Jun 2009 19:06:03 +0000</pubDate>
		<guid isPermaLink="false">http://theagileexecutive.com/?p=2546#comment-348</guid>
		<description><![CDATA[I would add that even software with a slow decay curve suffers from accumulated mass over time.  That mass creates a technology inertia as palpable as a rolling snowball.  Once the snowball becomes a certain size, it becomes almost impossible to lift or reshape it without immense effort.  One need look no further than Microsoft Windows to see the effect.  Each new release seems to require a longer time and greater complexity.]]></description>
		<content:encoded><![CDATA[<p>I would add that even software with a slow decay curve suffers from accumulated mass over time.  That mass creates a technology inertia as palpable as a rolling snowball.  Once the snowball becomes a certain size, it becomes almost impossible to lift or reshape it without immense effort.  One need look no further than Microsoft Windows to see the effect.  Each new release seems to require a longer time and greater complexity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Israel Gat</title>
		<link>http://theagileexecutive.com/2009/06/01/rusty-automobiles/#comment-347</link>
		<dc:creator><![CDATA[Israel Gat]]></dc:creator>
		<pubDate>Tue, 02 Jun 2009 18:50:40 +0000</pubDate>
		<guid isPermaLink="false">http://theagileexecutive.com/?p=2546#comment-347</guid>
		<description><![CDATA[We are in full agreement, Ayman. I believe the malleability of software often makes us forget about the decay. The problem is particularly bad when life-cycle costs of software are not sufficiently understood. The post Can You Afford the Software You are Developing (http://tr.im/nchq) speaks to the economics of the issue.

Israel]]></description>
		<content:encoded><![CDATA[<p>We are in full agreement, Ayman. I believe the malleability of software often makes us forget about the decay. The problem is particularly bad when life-cycle costs of software are not sufficiently understood. The post Can You Afford the Software You are Developing (<a href="http://tr.im/nchq" rel="nofollow">http://tr.im/nchq</a>) speaks to the economics of the issue.</p>
<p>Israel</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ayman Nassar</title>
		<link>http://theagileexecutive.com/2009/06/01/rusty-automobiles/#comment-346</link>
		<dc:creator><![CDATA[Ayman Nassar]]></dc:creator>
		<pubDate>Tue, 02 Jun 2009 12:19:22 +0000</pubDate>
		<guid isPermaLink="false">http://theagileexecutive.com/?p=2546#comment-346</guid>
		<description><![CDATA[It is very true that software just like everything else does become obsolete. Obsolescence is relative from one organization to another, at one place a policy can make a software system obsolete while at another it might still be producing. 

Thanks for sharing those links.]]></description>
		<content:encoded><![CDATA[<p>It is very true that software just like everything else does become obsolete. Obsolescence is relative from one organization to another, at one place a policy can make a software system obsolete while at another it might still be producing. </p>
<p>Thanks for sharing those links.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

