<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Beware The Iterative Approach</title>
	<atom:link href="http://danrough.net/2007/12/27/beware-the-iterative-approach/feed/" rel="self" type="application/rss+xml" />
	<link>http://danrough.net/2007/12/27/beware-the-iterative-approach/</link>
	<description></description>
	<lastBuildDate>Sun, 11 Sep 2011 08:36:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Ralph</title>
		<link>http://danrough.net/2007/12/27/beware-the-iterative-approach/#comment-1206</link>
		<dc:creator><![CDATA[Ralph]]></dc:creator>
		<pubDate>Tue, 18 Mar 2008 13:47:08 +0000</pubDate>
		<guid isPermaLink="false">http://danrough.wordpress.com/2007/12/27/beware-the-iterative-approach/#comment-1206</guid>
		<description><![CDATA[Hi Dan,

Being an former contracting colleague of Rob&#039;s, I stumbled upon your short description of what you consider to be iterative software development.  This is so true...  Unfortunaletly larger organisations do not realise this soon enough, and enormous mishaps resulting ion cancellations or strained relationships between integrators and clients are the result.  I have seen this in two projects I have worked on thus far, one for BMW and one for DHL (Current project, and in limbo between continuation or cancel)

A similar issue I have with a UseCase approach for implementations of relatyively predefined software solutions such as Siebel.  UseCase driven development is fine for .Net or Java framework development, but packages such as Siebel have constraints for which UseCases do not cater.

nevertheless, I am delighted to see that your stay in Canada was good, and have pity on you that the rat race has picked up pace again.

Say &#039;Hi&#039; to Read when you see him. (I was his BA way back in Q1-Q2 2005)

Ralph]]></description>
		<content:encoded><![CDATA[<p>Hi Dan,</p>
<p>Being an former contracting colleague of Rob&#8217;s, I stumbled upon your short description of what you consider to be iterative software development.  This is so true&#8230;  Unfortunaletly larger organisations do not realise this soon enough, and enormous mishaps resulting ion cancellations or strained relationships between integrators and clients are the result.  I have seen this in two projects I have worked on thus far, one for BMW and one for DHL (Current project, and in limbo between continuation or cancel)</p>
<p>A similar issue I have with a UseCase approach for implementations of relatyively predefined software solutions such as Siebel.  UseCase driven development is fine for .Net or Java framework development, but packages such as Siebel have constraints for which UseCases do not cater.</p>
<p>nevertheless, I am delighted to see that your stay in Canada was good, and have pity on you that the rat race has picked up pace again.</p>
<p>Say &#8216;Hi&#8217; to Read when you see him. (I was his BA way back in Q1-Q2 2005)</p>
<p>Ralph</p>
]]></content:encoded>
	</item>
</channel>
</rss>

