<?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: Argument against Waterfall</title>
	<atom:link href="http://www.marekj.com/2007/07/argument-against-waterfall/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.marekj.com/2007/07/argument-against-waterfall/</link>
	<description>cooperative software production infrastructure building</description>
	<pubDate>Sun, 12 Oct 2008 08:41:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Gregory Robinson</title>
		<link>http://www.marekj.com/2007/07/argument-against-waterfall/#comment-4261</link>
		<dc:creator>Gregory Robinson</dc:creator>
		<pubDate>Mon, 19 May 2008 10:56:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.marekj.com/2007/07/14/argument-against-waterfall/#comment-4261</guid>
		<description>Great Post!</description>
		<content:encoded><![CDATA[<p>Great Post!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dkemp</title>
		<link>http://www.marekj.com/2007/07/argument-against-waterfall/#comment-3247</link>
		<dc:creator>dkemp</dc:creator>
		<pubDate>Fri, 08 Feb 2008 16:30:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.marekj.com/2007/07/14/argument-against-waterfall/#comment-3247</guid>
		<description>It is difficult to imagine a project where results are repeatable. Haveing spent the past ten years testing software on teams using every methodology known to man including no apperent methodology. Waterfall, iterative, its just a label that all equals teams running around like heads with their chickens cut off stomping out fires. I recall a conversation with my Test Manager about process where I had suggested we attempt to 'plan' how we intend to impact quality. I said, "We are always reactive; why not proactive?" He said "When the house is burning down around you you need to get as many people as possible to help throw water on it." I said, "If the house if fully engulfed and the outcome obvious isn't it more productive to walk away and build a better house that is more fire resistent?" I was thinking about the 'Three Little Pigs' fairy tale. He said, "The people who pay the bills for that house are paying for us to bail water, not build a better house." How do you argue with that logic? This scenario plays out every release leaving a chared pile of half built product nobody wants to occupy. The customer is paying the bills and therefore has every right to burn it to the ground and complain to us that they aren't happy with the result. They could care less about managing process unless it makes them look productive and can keep getting paid. The idea that 'processes' alone make better software is in my opinion an academics argument that has no chance of survival in a real world situation where millions of dollars are at stake and the people shoveling the pile (paying the bills)haven't commited to it. The money doesn't care what labels we use or about process. All they want is happy people buying their product like hotcakes and paying them big bucks for it. Screw process! Make yourself look busy and keep bailing! Is the check good? Whats to worry about process? Oiy.</description>
		<content:encoded><![CDATA[<p>It is difficult to imagine a project where results are repeatable. Haveing spent the past ten years testing software on teams using every methodology known to man including no apperent methodology. Waterfall, iterative, its just a label that all equals teams running around like heads with their chickens cut off stomping out fires. I recall a conversation with my Test Manager about process where I had suggested we attempt to &#8216;plan&#8217; how we intend to impact quality. I said, &#8220;We are always reactive; why not proactive?&#8221; He said &#8220;When the house is burning down around you you need to get as many people as possible to help throw water on it.&#8221; I said, &#8220;If the house if fully engulfed and the outcome obvious isn&#8217;t it more productive to walk away and build a better house that is more fire resistent?&#8221; I was thinking about the &#8216;Three Little Pigs&#8217; fairy tale. He said, &#8220;The people who pay the bills for that house are paying for us to bail water, not build a better house.&#8221; How do you argue with that logic? This scenario plays out every release leaving a chared pile of half built product nobody wants to occupy. The customer is paying the bills and therefore has every right to burn it to the ground and complain to us that they aren&#8217;t happy with the result. They could care less about managing process unless it makes them look productive and can keep getting paid. The idea that &#8216;processes&#8217; alone make better software is in my opinion an academics argument that has no chance of survival in a real world situation where millions of dollars are at stake and the people shoveling the pile (paying the bills)haven&#8217;t commited to it. The money doesn&#8217;t care what labels we use or about process. All they want is happy people buying their product like hotcakes and paying them big bucks for it. Screw process! Make yourself look busy and keep bailing! Is the check good? Whats to worry about process? Oiy.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
