<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Could Occam&#8217;s Razor Explain Project Failures?</title>
	<link>http://www.reformingprojectmanagement.com/2005/02/13/452/</link>
	<description>The magazine for the project age</description>
	<pubDate>Fri, 16 May 2008 03:00:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Craig M.</title>
		<link>http://www.reformingprojectmanagement.com/2005/02/13/452/#comment-20733</link>
		<pubDate>Mon, 25 Feb 2008 23:48:45 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2005/02/13/452/#comment-20733</guid>
					<description>Occam's Razor applies not only to explain what when wrong, but also what should be done.  Simply put, the question the owner is asking is 'How can I get what I pay for in one try?"  

The owner is worried about not knowing how all of his decisions shake out.  The General can help, but rarely knows the intimate details of all of the trades.  Simple--bring the trades in early, and incentivize them to criticize the design so that change orders during construction are minimized.</description>
		<content:encoded><![CDATA[<p>Occam&#8217;s Razor applies not only to explain what when wrong, but also what should be done.  Simply put, the question the owner is asking is &#8216;How can I get what I pay for in one try?&#8221;  </p>
<p>The owner is worried about not knowing how all of his decisions shake out.  The General can help, but rarely knows the intimate details of all of the trades.  Simple&#8211;bring the trades in early, and incentivize them to criticize the design so that change orders during construction are minimized.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Donn Brown, PMP</title>
		<link>http://www.reformingprojectmanagement.com/2005/02/13/452/#comment-2381</link>
		<pubDate>Fri, 20 Jan 2006 04:19:27 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2005/02/13/452/#comment-2381</guid>
					<description>Occam's Razor is what wins you the bid! In my industry I have to estimate what it will take to provide a potential client a deliverable. The more complex and detailed your project plan becomes, the more costs that get added to each task. In my industry, this will put you out of work. 

Understanding the market and presenting a plan that has a well defined scope is the best approach. If one goes into a project with the ability to adapt, they are better prepared to handle the changes that can occur on a project. PM's must understand that the "best case scenerio" only works when you have total control of all the outside factors. Allowing for slack and seriously considering outside risks will confort all stakeholders of your project............

Projects typically fail because the attitudes of the team members declines during those unexpected obstacles. A PM should continually be thinking about Murphy's Law, and what the team can do to mitigate for those unexpected events.................</description>
		<content:encoded><![CDATA[<p>Occam&#8217;s Razor is what wins you the bid! In my industry I have to estimate what it will take to provide a potential client a deliverable. The more complex and detailed your project plan becomes, the more costs that get added to each task. In my industry, this will put you out of work. </p>
<p>Understanding the market and presenting a plan that has a well defined scope is the best approach. If one goes into a project with the ability to adapt, they are better prepared to handle the changes that can occur on a project. PM&#8217;s must understand that the &#8220;best case scenerio&#8221; only works when you have total control of all the outside factors. Allowing for slack and seriously considering outside risks will confort all stakeholders of your project&#8230;&#8230;&#8230;&#8230;</p>
<p>Projects typically fail because the attitudes of the team members declines during those unexpected obstacles. A PM should continually be thinking about Murphy&#8217;s Law, and what the team can do to mitigate for those unexpected events&#8230;&#8230;&#8230;&#8230;&#8230;..
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Chui Tey</title>
		<link>http://www.reformingprojectmanagement.com/2005/02/13/452/#comment-1959</link>
		<pubDate>Tue, 29 Nov 2005 11:34:25 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2005/02/13/452/#comment-1959</guid>
					<description>You've hit the nail on the head there.  Project governance determines outcome.  At every point in a project,  a conscious decision must be made whether to go ahead, adjust or kill the project.  Inability to recognize a significant deviation from plan has already occurred leads to disasters like the Columbia space shuttle.
</description>
		<content:encoded><![CDATA[<p>You&#8217;ve hit the nail on the head there.  Project governance determines outcome.  At every point in a project,  a conscious decision must be made whether to go ahead, adjust or kill the project.  Inability to recognize a significant deviation from plan has already occurred leads to disasters like the Columbia space shuttle.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Sebastian Scheible</title>
		<link>http://www.reformingprojectmanagement.com/2005/02/13/452/#comment-291</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2005/02/13/452/#comment-291</guid>
					<description>        Perhaps the Pter principle might add a facet to explaining failures. http://en.wikipedia.org/wiki/Peter_principle
      </description>
		<content:encoded><![CDATA[<p>Perhaps the Pter principle might add a facet to explaining failures. <a href="http://en.wikipedia.org/wiki/Peter_principle" rel="nofollow">http://en.wikipedia.org/wiki/Peter_principle</a>
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
