<?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: Agile or Waterfall&#8230;does it matter?</title>
	<atom:link href="http://ericbrown.com/agile-or-waterfalldoes-it-matter.htm/feed" rel="self" type="application/rss+xml" />
	<link>http://ericbrown.com/agile-or-waterfalldoes-it-matter.htm</link>
	<description>Technology, Strategy, People and Projects</description>
	<lastBuildDate>Fri, 19 Mar 2010 11:51:21 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Eric Brown</title>
		<link>http://ericbrown.com/agile-or-waterfalldoes-it-matter.htm/comment-page-1#comment-206</link>
		<dc:creator>Eric Brown</dc:creator>
		<pubDate>Mon, 10 Sep 2007 20:36:13 +0000</pubDate>
		<guid isPermaLink="false">http://ericbrownpm.com/2007/08/24/agile-or-waterfalldoes-it-matter/#comment-206</guid>
		<description>Mark - Thanks for the link to ObjectMentor.com...I will check them out.

Thanks!
Eric</description>
		<content:encoded><![CDATA[<p>Mark &#8211; Thanks for the link to ObjectMentor.com&#8230;I will check them out.</p>
<p>Thanks!<br />
Eric</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mark</title>
		<link>http://ericbrown.com/agile-or-waterfalldoes-it-matter.htm/comment-page-1#comment-205</link>
		<dc:creator>mark</dc:creator>
		<pubDate>Mon, 10 Sep 2007 20:29:02 +0000</pubDate>
		<guid isPermaLink="false">http://ericbrownpm.com/2007/08/24/agile-or-waterfalldoes-it-matter/#comment-205</guid>
		<description>To quote you:
&#039;I’ve never heard of Agile methods being used in very large scale complex projects (construction, defense industry, etc) and don’t believe the agile models scale that well to projects of that scale but I’d love to be proven wrong.&#039;
Check out objectmentor.com. They have cleaned up a few large projects by using agile development. Ask them.</description>
		<content:encoded><![CDATA[<p>To quote you:<br />
&#8216;I’ve never heard of Agile methods being used in very large scale complex projects (construction, defense industry, etc) and don’t believe the agile models scale that well to projects of that scale but I’d love to be proven wrong.&#8217;<br />
Check out objectmentor.com. They have cleaned up a few large projects by using agile development. Ask them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pawel Brodzinski</title>
		<link>http://ericbrown.com/agile-or-waterfalldoes-it-matter.htm/comment-page-1#comment-204</link>
		<dc:creator>Pawel Brodzinski</dc:creator>
		<pubDate>Tue, 28 Aug 2007 15:07:39 +0000</pubDate>
		<guid isPermaLink="false">http://ericbrownpm.com/2007/08/24/agile-or-waterfalldoes-it-matter/#comment-204</guid>
		<description>You can rarely see a &quot;clean&quot; model of software development (either agile or waterfall). The truth is that usually we some mixture of those and more (iterative, process-oriented etc). And as you write there&#039;s no rule which says which methodology is the best for which project. If there was one everyone would use it.

However, the discussion about project management and software development methodologies is old and has rather religious base (which isn&#039;t a good one). The most important thing you&#039;ve pointed is the key role of people in all those mess. I don&#039;t say the great team will always deliver, no matter what the process is but in most cases result should be at least promising. On the other hand if the team is poor no matter how superior the methodology is you&#039;re doomed to failure.

Considering this context the methodology wars are not only boring but also overrated.</description>
		<content:encoded><![CDATA[<p>You can rarely see a &#8220;clean&#8221; model of software development (either agile or waterfall). The truth is that usually we some mixture of those and more (iterative, process-oriented etc). And as you write there&#8217;s no rule which says which methodology is the best for which project. If there was one everyone would use it.</p>
<p>However, the discussion about project management and software development methodologies is old and has rather religious base (which isn&#8217;t a good one). The most important thing you&#8217;ve pointed is the key role of people in all those mess. I don&#8217;t say the great team will always deliver, no matter what the process is but in most cases result should be at least promising. On the other hand if the team is poor no matter how superior the methodology is you&#8217;re doomed to failure.</p>
<p>Considering this context the methodology wars are not only boring but also overrated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Brown</title>
		<link>http://ericbrown.com/agile-or-waterfalldoes-it-matter.htm/comment-page-1#comment-203</link>
		<dc:creator>Eric Brown</dc:creator>
		<pubDate>Mon, 27 Aug 2007 15:42:11 +0000</pubDate>
		<guid isPermaLink="false">http://ericbrownpm.com/2007/08/24/agile-or-waterfalldoes-it-matter/#comment-203</guid>
		<description>Tom - Thanks for the comment.

I agree wholeheartedly...project success will come down to the people involved.</description>
		<content:encoded><![CDATA[<p>Tom &#8211; Thanks for the comment.</p>
<p>I agree wholeheartedly&#8230;project success will come down to the people involved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://ericbrown.com/agile-or-waterfalldoes-it-matter.htm/comment-page-1#comment-202</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Mon, 27 Aug 2007 15:30:11 +0000</pubDate>
		<guid isPermaLink="false">http://ericbrownpm.com/2007/08/24/agile-or-waterfalldoes-it-matter/#comment-202</guid>
		<description>I believe that waterfall only works when all parties are commited to a given project. The adavantage that agile brings to the table is that it exposes all levels of the project to all people. Big or small the project size does not matter, it always comes down to the people involved.</description>
		<content:encoded><![CDATA[<p>I believe that waterfall only works when all parties are commited to a given project. The adavantage that agile brings to the table is that it exposes all levels of the project to all people. Big or small the project size does not matter, it always comes down to the people involved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Brown</title>
		<link>http://ericbrown.com/agile-or-waterfalldoes-it-matter.htm/comment-page-1#comment-201</link>
		<dc:creator>Eric Brown</dc:creator>
		<pubDate>Mon, 27 Aug 2007 01:51:17 +0000</pubDate>
		<guid isPermaLink="false">http://ericbrownpm.com/2007/08/24/agile-or-waterfalldoes-it-matter/#comment-201</guid>
		<description>Rajeev,

Thanks for the comment.  I agree with every point.

I think agile methods are viable for projects and companies of any size...but the argument that I hear most often for Agile is that waterfall doesn&#039;t work...which is incorrect.  Any methodology will work work in the right circumstances with the right backing and right people.

Thanks again for the comments!</description>
		<content:encoded><![CDATA[<p>Rajeev,</p>
<p>Thanks for the comment.  I agree with every point.</p>
<p>I think agile methods are viable for projects and companies of any size&#8230;but the argument that I hear most often for Agile is that waterfall doesn&#8217;t work&#8230;which is incorrect.  Any methodology will work work in the right circumstances with the right backing and right people.</p>
<p>Thanks again for the comments!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rajeev Singh</title>
		<link>http://ericbrown.com/agile-or-waterfalldoes-it-matter.htm/comment-page-1#comment-200</link>
		<dc:creator>Rajeev Singh</dc:creator>
		<pubDate>Mon, 27 Aug 2007 01:40:29 +0000</pubDate>
		<guid isPermaLink="false">http://ericbrownpm.com/2007/08/24/agile-or-waterfalldoes-it-matter/#comment-200</guid>
		<description>Yes and I would like to put forh my opinion on it.

1. I have heard a lot about Agile not suitable for large projects and being a good fit for small projects with a &quot;few&quot; programmer. The problem with these opinions is that these writers never specify what &#039;small&#039; or &#039;few&#039; is.

2. Agile does definitely matter. These days it matters to the client, where they want to see results early on. They wwant to know as early as possible if their strategy is working or not, if they have the right people or not, etc.

3. People are the key. It is a pleasure to realize that people can make or break a project and companies. And smart are those who realize that&#039;s its all about people. Afterall, there are still companies that produce world class products and either don&#039;t want to or don&#039;t have the freedom and knowhow to become Agile, yet. And, it&#039;s their people that make them world class.</description>
		<content:encoded><![CDATA[<p>Yes and I would like to put forh my opinion on it.</p>
<p>1. I have heard a lot about Agile not suitable for large projects and being a good fit for small projects with a &#8220;few&#8221; programmer. The problem with these opinions is that these writers never specify what &#8217;small&#8217; or &#8216;few&#8217; is.</p>
<p>2. Agile does definitely matter. These days it matters to the client, where they want to see results early on. They wwant to know as early as possible if their strategy is working or not, if they have the right people or not, etc.</p>
<p>3. People are the key. It is a pleasure to realize that people can make or break a project and companies. And smart are those who realize that&#8217;s its all about people. Afterall, there are still companies that produce world class products and either don&#8217;t want to or don&#8217;t have the freedom and knowhow to become Agile, yet. And, it&#8217;s their people that make them world class.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
