<?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: Taking Agile Beyond &#8220;Faster&#8221;</title>
	<atom:link href="http://www.bigvisible.com/bbozzuto/taking-agile-beyond-faster/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bigvisible.com/bbozzuto/taking-agile-beyond-faster/</link>
	<description></description>
	<lastBuildDate>Tue, 20 Jul 2010 04:54:15 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Brian Bozzuto</title>
		<link>http://www.bigvisible.com/bbozzuto/taking-agile-beyond-faster/comment-page-1/#comment-21469</link>
		<dc:creator>Brian Bozzuto</dc:creator>
		<pubDate>Wed, 06 Jan 2010 15:37:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.bigvisible.com/?p=571#comment-21469</guid>
		<description>Hi Michael, thanks for the thoughtful feedback and highlighting the point that most traditional projects have bloated requirements. I like this a lot, and I think it is critical to my point about iterative development, it certainly would have bolstered my point about doing less and having the option to keep going. That image articulates the idea that we can get a &quot;pretty good&quot; product early, and based on that feedback, we can continue to improve and refine it. I believe the other statistic is that something lie 80% of all features are implemented in successive releases.

In the case of the financial model, you are correct, if we incorporated the fact that a team could launch with less work, that would increase the ROI, but I was trying to isolate variables and show how the simple act of delivering earlier makes a substantial difference.</description>
		<content:encoded><![CDATA[<p>Hi Michael, thanks for the thoughtful feedback and highlighting the point that most traditional projects have bloated requirements. I like this a lot, and I think it is critical to my point about iterative development, it certainly would have bolstered my point about doing less and having the option to keep going. That image articulates the idea that we can get a &#8220;pretty good&#8221; product early, and based on that feedback, we can continue to improve and refine it. I believe the other statistic is that something lie 80% of all features are implemented in successive releases.</p>
<p>In the case of the financial model, you are correct, if we incorporated the fact that a team could launch with less work, that would increase the ROI, but I was trying to isolate variables and show how the simple act of delivering earlier makes a substantial difference.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Sahota</title>
		<link>http://www.bigvisible.com/bbozzuto/taking-agile-beyond-faster/comment-page-1/#comment-21466</link>
		<dc:creator>Michael Sahota</dc:creator>
		<pubDate>Wed, 06 Jan 2010 13:37:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.bigvisible.com/?p=571#comment-21466</guid>
		<description>Hi Brian, this is a great write-up and goes a long way towards explaining the value proposition of Agile. I will include some parts that I don&#039;t already use the next time I tell that story.  

One thing that you mention, but I find a key element is that with an Agile project you will build only the most important features - see chart(http://bit.ly/4Eeyoq). So, in the one year project you mention, you will actually end up with a different result.  So the financial model actually understates the value of Agile.  For me this is an essential point.

I like the section on Iterative delivery, but doesn&#039;t seem to fit well with the rest.</description>
		<content:encoded><![CDATA[<p>Hi Brian, this is a great write-up and goes a long way towards explaining the value proposition of Agile. I will include some parts that I don&#8217;t already use the next time I tell that story.  </p>
<p>One thing that you mention, but I find a key element is that with an Agile project you will build only the most important features &#8211; see chart(http://bit.ly/4Eeyoq). So, in the one year project you mention, you will actually end up with a different result.  So the financial model actually understates the value of Agile.  For me this is an essential point.</p>
<p>I like the section on Iterative delivery, but doesn&#8217;t seem to fit well with the rest.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
