<?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: Different Flavours of Waterfall and Agile Development</title>
	<atom:link href="http://geek4eva.com/2009/09/29/different-flavours-of-waterfall-and-agile-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://geek4eva.com/2009/09/29/different-flavours-of-waterfall-and-agile-development/</link>
	<description>No Limits</description>
	<lastBuildDate>Thu, 03 Nov 2011 20:40:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Waterfall and Agile</title>
		<link>http://geek4eva.com/2009/09/29/different-flavours-of-waterfall-and-agile-development/#comment-61</link>
		<dc:creator>Waterfall and Agile</dc:creator>
		<pubDate>Thu, 01 Oct 2009 15:18:56 +0000</pubDate>
		<guid isPermaLink="false">http://geek4eva.logicx.co.nz/blog/?p=397#comment-61</guid>
		<description>Waterfall and agile are two unique development models used in interactive and software production. It&#039;s likely the debate over which is better will continue indefinitely, but in reality, both approaches boast significant but different benefits. It&#039;s generally accepted that agile, specifically, lends itself well to software development and large-scale website projects. Although a novice Project Manager may feel more comfortable working with a waterfall approach because each step is predictable, letting go of the familiar may well be worth it to make the move to an agile model. The collaboration and flexibility that agile brings can result in a better end product for your client, and a more engaged, harmonious internal team.</description>
		<content:encoded><![CDATA[<p>Waterfall and agile are two unique development models used in interactive and software production. It&#8217;s likely the debate over which is better will continue indefinitely, but in reality, both approaches boast significant but different benefits. It&#8217;s generally accepted that agile, specifically, lends itself well to software development and large-scale website projects. Although a novice Project Manager may feel more comfortable working with a waterfall approach because each step is predictable, letting go of the familiar may well be worth it to make the move to an agile model. The collaboration and flexibility that agile brings can result in a better end product for your client, and a more engaged, harmonious internal team.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

