<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.7" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Too Big to Fail</title>
	<link>http://www.blog.sethroberts.net/2009/10/28/too-big-to-fail/</link>
	<description>Self-Experimentation, Scientific Method, the Shangri-La Diet, etc.</description>
	<pubDate>Sat, 20 Mar 2010 05:50:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.7</generator>

	<item>
		<title>by: Igor Carron</title>
		<link>http://www.blog.sethroberts.net/2009/10/28/too-big-to-fail/#comment-357096</link>
		<pubDate>Sat, 31 Oct 2009 18:15:51 +0000</pubDate>
		<guid>http://www.blog.sethroberts.net/2009/10/28/too-big-to-fail/#comment-357096</guid>
					<description>It is a big lesson for the customer (the government in this case). O agree, consultants can and do strive in this environment.</description>
		<content:encoded><![CDATA[<p>It is a big lesson for the customer (the government in this case). O agree, consultants can and do strive in this environment.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: JLD</title>
		<link>http://www.blog.sethroberts.net/2009/10/28/too-big-to-fail/#comment-357073</link>
		<pubDate>Sat, 31 Oct 2009 17:21:23 +0000</pubDate>
		<guid>http://www.blog.sethroberts.net/2009/10/28/too-big-to-fail/#comment-357073</guid>
					<description>&lt;i&gt;The big lessons are that in extremely complex projects, sometimes you should not allow your customer to be able to change your requirements as you go.&lt;/i&gt;

Wait til you enter real professionnal life.
Retired consultant.</description>
		<content:encoded><![CDATA[<p><i>The big lessons are that in extremely complex projects, sometimes you should not allow your customer to be able to change your requirements as you go.</i></p>
<p>Wait til you enter real professionnal life.<br />
Retired consultant.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Igor Carron</title>
		<link>http://www.blog.sethroberts.net/2009/10/28/too-big-to-fail/#comment-357022</link>
		<pubDate>Sat, 31 Oct 2009 14:33:35 +0000</pubDate>
		<guid>http://www.blog.sethroberts.net/2009/10/28/too-big-to-fail/#comment-357022</guid>
					<description>There may be good reasons sometimes as to why these projects do change in their price tags over time. I have seen several projects like this and clearly remember a prof at MIT showing us why (I need to dig his name up, I think it was Michael Golay, http://web.mit.edu/nse/people/faculty/golay.html). 

The idea was that in a government projects, the customer (the government) ends up changing the requirements of the project many times over the life of the project. These changes of requirements are extremely bad with regards to the flow of execution of the project. 

In the space business for instance, there is one example that is pretty interesting: Spacelab, a large cylinder that goes in the shuttle's belly for astronauts to do their experiments. A company ended up designing the same cylinder and eventually sold the services to this new cylinder to NASA. It was pretty obvious that the company's cylinder had cost much less than the original Spacelab built inside NASA. However, as is often the case in comparing gov and private projects, it is a somewhat an unfair comparison as the second cylinder was built with the knowledge of what the first cylinder final requirements were. The big lessons are that in extremely complex projects, sometimes you should not allow your customer to be able to change your requirements as you go.</description>
		<content:encoded><![CDATA[<p>There may be good reasons sometimes as to why these projects do change in their price tags over time. I have seen several projects like this and clearly remember a prof at MIT showing us why (I need to dig his name up, I think it was Michael Golay, <a href="http://web.mit.edu/nse/people/faculty/golay.html" rel="nofollow">http://web.mit.edu/nse/people/faculty/golay.html</a>). </p>
<p>The idea was that in a government projects, the customer (the government) ends up changing the requirements of the project many times over the life of the project. These changes of requirements are extremely bad with regards to the flow of execution of the project. </p>
<p>In the space business for instance, there is one example that is pretty interesting: Spacelab, a large cylinder that goes in the shuttle&#8217;s belly for astronauts to do their experiments. A company ended up designing the same cylinder and eventually sold the services to this new cylinder to NASA. It was pretty obvious that the company&#8217;s cylinder had cost much less than the original Spacelab built inside NASA. However, as is often the case in comparing gov and private projects, it is a somewhat an unfair comparison as the second cylinder was built with the knowledge of what the first cylinder final requirements were. The big lessons are that in extremely complex projects, sometimes you should not allow your customer to be able to change your requirements as you go.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Tom in TX</title>
		<link>http://www.blog.sethroberts.net/2009/10/28/too-big-to-fail/#comment-356596</link>
		<pubDate>Fri, 30 Oct 2009 16:52:02 +0000</pubDate>
		<guid>http://www.blog.sethroberts.net/2009/10/28/too-big-to-fail/#comment-356596</guid>
					<description>"There should be some term for these screw-the-public-they’re-too-stupid-to-realize-it situations."

I think they are called "government projects".</description>
		<content:encoded><![CDATA[<p>&#8220;There should be some term for these screw-the-public-they’re-too-stupid-to-realize-it situations.&#8221;</p>
<p>I think they are called &#8220;government projects&#8221;.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: JLD</title>
		<link>http://www.blog.sethroberts.net/2009/10/28/too-big-to-fail/#comment-356446</link>
		<pubDate>Fri, 30 Oct 2009 06:51:18 +0000</pubDate>
		<guid>http://www.blog.sethroberts.net/2009/10/28/too-big-to-fail/#comment-356446</guid>
					<description>Pretty puzzling that being in China you could not identify &lt;a href="http://www.google.com/search?hl=en&#38;safe=off&#38;edition=us&#38;num=50&#38;q=%E2%80%9Cthree+gorges+dam%E2%80%9D+cost+overruns&#38;btnG=Search&#38;aq=f&#38;oq=&#38;aqi=" rel="nofollow"&gt;the matter&lt;/a&gt;.
Thus the chinese gov't "control" over news is pretty effective.</description>
		<content:encoded><![CDATA[<p>Pretty puzzling that being in China you could not identify <a href="http://www.google.com/search?hl=en&amp;safe=off&amp;edition=us&amp;num=50&amp;q=%E2%80%9Cthree+gorges+dam%E2%80%9D+cost+overruns&amp;btnG=Search&amp;aq=f&amp;oq=&amp;aqi=" rel="nofollow">the matter</a>.<br />
Thus the chinese gov&#8217;t &#8220;control&#8221; over news is pretty effective.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Peter McDonnell</title>
		<link>http://www.blog.sethroberts.net/2009/10/28/too-big-to-fail/#comment-356282</link>
		<pubDate>Thu, 29 Oct 2009 23:57:46 +0000</pubDate>
		<guid>http://www.blog.sethroberts.net/2009/10/28/too-big-to-fail/#comment-356282</guid>
					<description>I suspect that Nathan meant "Three Gorges Dam"</description>
		<content:encoded><![CDATA[<p>I suspect that Nathan meant &#8220;Three Gorges Dam&#8221;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: seth</title>
		<link>http://www.blog.sethroberts.net/2009/10/28/too-big-to-fail/#comment-356236</link>
		<pubDate>Thu, 29 Oct 2009 20:39:32 +0000</pubDate>
		<guid>http://www.blog.sethroberts.net/2009/10/28/too-big-to-fail/#comment-356236</guid>
					<description>Nathan, trying to figure out what you are talking about I got this:
&lt;blockquote&gt;Your search - "three rivers dam" gigantic cost overruns - did not match any documents.&lt;/blockquote&gt;
could you provide a link?

"boondoogle" isn't right because these projects do work; they just cost vastly more than estimated.</description>
		<content:encoded><![CDATA[<p>Nathan, trying to figure out what you are talking about I got this:</p>
<blockquote><p>Your search - &#8220;three rivers dam&#8221; gigantic cost overruns - did not match any documents.</p></blockquote>
<p>could you provide a link?</p>
<p>&#8220;boondoogle&#8221; isn&#8217;t right because these projects do work; they just cost vastly more than estimated.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Nathan Myers</title>
		<link>http://www.blog.sethroberts.net/2009/10/28/too-big-to-fail/#comment-356228</link>
		<pubDate>Thu, 29 Oct 2009 20:11:33 +0000</pubDate>
		<guid>http://www.blog.sethroberts.net/2009/10/28/too-big-to-fail/#comment-356228</guid>
					<description>Haven't you heard of the Three Rivers Dam?</description>
		<content:encoded><![CDATA[<p>Haven&#8217;t you heard of the Three Rivers Dam?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Darrin Thompson</title>
		<link>http://www.blog.sethroberts.net/2009/10/28/too-big-to-fail/#comment-356093</link>
		<pubDate>Thu, 29 Oct 2009 13:15:07 +0000</pubDate>
		<guid>http://www.blog.sethroberts.net/2009/10/28/too-big-to-fail/#comment-356093</guid>
					<description>I want to say that term is "bailout" but that's overloaded by the connotation that these things are necessary or inevitable. The story is all wrong.

"Freedom Torches" would be another one. Not very direct but you get to tell the story of the original PR man promoting cigarettes for mommies. It's got that cynical overtone such a term needs.

Or maybe go the other way with morbidly blank words like, "optional public crisis", "public insurance," or "noncompulsary emergency event."</description>
		<content:encoded><![CDATA[<p>I want to say that term is &#8220;bailout&#8221; but that&#8217;s overloaded by the connotation that these things are necessary or inevitable. The story is all wrong.</p>
<p>&#8220;Freedom Torches&#8221; would be another one. Not very direct but you get to tell the story of the original PR man promoting cigarettes for mommies. It&#8217;s got that cynical overtone such a term needs.</p>
<p>Or maybe go the other way with morbidly blank words like, &#8220;optional public crisis&#8221;, &#8220;public insurance,&#8221; or &#8220;noncompulsary emergency event.&#8221;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Peter McDonnell</title>
		<link>http://www.blog.sethroberts.net/2009/10/28/too-big-to-fail/#comment-356089</link>
		<pubDate>Thu, 29 Oct 2009 13:00:24 +0000</pubDate>
		<guid>http://www.blog.sethroberts.net/2009/10/28/too-big-to-fail/#comment-356089</guid>
					<description>Hi Seth,
I enjoy your blog greatlly. How about "Boondoggle"? as in a boondoggle project, from Wikipedia: "It also refers to government or corporate projects involving large numbers of people and usually heavy expenditure; at some point, the key operators have realized that the project is never going to work, but are reluctant to bring this to the attention of their superiors. Generally there is an aspect of "going through the motions" – for example, continuing research and development – as long as funds are available to keep paying the researchers' and executives' salaries. The situation can be allowed to continue for what seems like unreasonably long periods, as senior management are often reluctant to admit that they allowed a failed project to go on for so long. In many cases, the actual device itself may eventually work, but not well enough to ever recoup its development costs."</description>
		<content:encoded><![CDATA[<p>Hi Seth,<br />
I enjoy your blog greatlly. How about &#8220;Boondoggle&#8221;? as in a boondoggle project, from Wikipedia: &#8220;It also refers to government or corporate projects involving large numbers of people and usually heavy expenditure; at some point, the key operators have realized that the project is never going to work, but are reluctant to bring this to the attention of their superiors. Generally there is an aspect of &#8220;going through the motions&#8221; – for example, continuing research and development – as long as funds are available to keep paying the researchers&#8217; and executives&#8217; salaries. The situation can be allowed to continue for what seems like unreasonably long periods, as senior management are often reluctant to admit that they allowed a failed project to go on for so long. In many cases, the actual device itself may eventually work, but not well enough to ever recoup its development costs.&#8221;
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
