<?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: Risk boomerang</title>
	<atom:link href="http://www.andybrandt.net/513/risk-boomerang/feed" rel="self" type="application/rss+xml" />
	<link>http://www.andybrandt.net/513/risk-boomerang</link>
	<description>A stream in the sea...</description>
	<lastBuildDate>Wed, 04 Jan 2012 14:33:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Jeff Gordon</title>
		<link>http://www.andybrandt.net/513/risk-boomerang/comment-page-1#comment-58178</link>
		<dc:creator>Jeff Gordon</dc:creator>
		<pubDate>Thu, 29 Oct 2009 23:40:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.andybrandt.net/?p=513#comment-58178</guid>
		<description>Hi Andy:

In theory the client should be involved along the way - but I don&#039;t think the client has the skills or time to wait for an entire project to be completed prior to a first review.  So I normally push for a technique used by countless folks: milestone-based projects/contracting.

The developer breaks the single project into discrete milestones.  Things that ARE capable of inspection (and testing) by the client get reviewed and then PAYMENT is tied to successful milestone acceptance, with the entire amount paid over time tied to successful completion of the entire project (ie: if you never reach the goal, the client gets their $$ back).

Oh, it still doesn&#039;t eliminate the risk, but it does spread it about some.  ;)</description>
		<content:encoded><![CDATA[<p>Hi Andy:</p>
<p>In theory the client should be involved along the way &#8211; but I don&#8217;t think the client has the skills or time to wait for an entire project to be completed prior to a first review.  So I normally push for a technique used by countless folks: milestone-based projects/contracting.</p>
<p>The developer breaks the single project into discrete milestones.  Things that ARE capable of inspection (and testing) by the client get reviewed and then PAYMENT is tied to successful milestone acceptance, with the entire amount paid over time tied to successful completion of the entire project (ie: if you never reach the goal, the client gets their $$ back).</p>
<p>Oh, it still doesn&#8217;t eliminate the risk, but it does spread it about some.  <img src='http://www.andybrandt.net/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://www.andybrandt.net/513/risk-boomerang/comment-page-1#comment-58177</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Thu, 29 Oct 2009 22:00:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.andybrandt.net/?p=513#comment-58177</guid>
		<description>Willy, everyone is just fooled the risk is not on their side. And I&#039;m talking here about custom-built complex products, not about mass manufactured, repeatable goods.</description>
		<content:encoded><![CDATA[<p>Willy, everyone is just fooled the risk is not on their side. And I&#8217;m talking here about custom-built complex products, not about mass manufactured, repeatable goods.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Willy</title>
		<link>http://www.andybrandt.net/513/risk-boomerang/comment-page-1#comment-58176</link>
		<dc:creator>Willy</dc:creator>
		<pubDate>Wed, 28 Oct 2009 20:24:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.andybrandt.net/?p=513#comment-58176</guid>
		<description>In theory it sounds good, and I wish they could, so I can almost agree... Unfortunately the reality is more complex.

Agile doesn&#039;t offers control, offers to fail in a short period of time. This does not reduce the risk, just reduces the loss.

Agile Contract only works in the IT World, not in Real World. Everyone (not IT) puts the risk on supplier side (in fact yourself when you buy anything), that will not change for a while... Do you have only IT clients? Good for you!</description>
		<content:encoded><![CDATA[<p>In theory it sounds good, and I wish they could, so I can almost agree&#8230; Unfortunately the reality is more complex.</p>
<p>Agile doesn&#8217;t offers control, offers to fail in a short period of time. This does not reduce the risk, just reduces the loss.</p>
<p>Agile Contract only works in the IT World, not in Real World. Everyone (not IT) puts the risk on supplier side (in fact yourself when you buy anything), that will not change for a while&#8230; Do you have only IT clients? Good for you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Till</title>
		<link>http://www.andybrandt.net/513/risk-boomerang/comment-page-1#comment-58175</link>
		<dc:creator>Till</dc:creator>
		<pubDate>Wed, 28 Oct 2009 20:02:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.andybrandt.net/?p=513#comment-58175</guid>
		<description>Totally agreed - excellent blog post! The boomerang metaphor may help us in according future discussions :-)</description>
		<content:encoded><![CDATA[<p>Totally agreed &#8211; excellent blog post! The boomerang metaphor may help us in according future discussions <img src='http://www.andybrandt.net/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

