<?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"
	>
<channel>
	<title>Comments on: Myths I - Change is expensive</title>
	<atom:link href="http://agileblog.3months.com/2007/08/20/change_is_expensive/feed/" rel="self" type="application/rss+xml" />
	<link>http://agileblog.3months.com/2007/08/20/change_is_expensive/</link>
	<description>3months are a New Zealand based Agile Consulting and development company.</description>
	<pubDate>Tue, 06 Jan 2009 02:56:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Early benefit realization and better business alignment through iterative and agile software development cycles - Agility for IT professionals</title>
		<link>http://agileblog.3months.com/2007/08/20/change_is_expensive/#comment-56</link>
		<dc:creator>Early benefit realization and better business alignment through iterative and agile software development cycles - Agility for IT professionals</dc:creator>
		<pubDate>Sat, 01 Sep 2007 11:13:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.smartbeanz.net/blog/index.php/2007/08/20/change_is_expensive/#comment-56</guid>
		<description>[...] Early releases gives the business the option to use the software even with less features (frequent releases will gradually build up the feature list) and hence start reaping the benefits from the investment. Because the features with the most business value are usually prioritized first the software can start paying for itself and for the less important features. And coming back to the previous point I have seen quite a few projects where stakeholders decided to drop the less important features in exchange for changes they would have otherwise had to pay for. This allows a project to stay in budget and deliver totally aligned with the business needs (which of course can change). [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Early releases gives the business the option to use the software even with less features (frequent releases will gradually build up the feature list) and hence start reaping the benefits from the investment. Because the features with the most business value are usually prioritized first the software can start paying for itself and for the less important features. And coming back to the previous point I have seen quite a few projects where stakeholders decided to drop the less important features in exchange for changes they would have otherwise had to pay for. This allows a project to stay in budget and deliver totally aligned with the business needs (which of course can change). [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
