<?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: The Fourth Great Lie</title>
	<atom:link href="http://blogs.gartner.com/donna_fitzgerald/2009/05/11/the-fourth-great-lie/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gartner.com/donna_fitzgerald/2009/05/11/the-fourth-great-lie/</link>
	<description>A Member of The Gartner Blog Network</description>
	<lastBuildDate>Mon, 16 Nov 2009 21:51:41 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: The Nimble PM &#187; The 4th Great Lie (continued)</title>
		<link>http://blogs.gartner.com/donna_fitzgerald/2009/05/11/the-fourth-great-lie/comment-page-1/#comment-64</link>
		<dc:creator>The Nimble PM &#187; The 4th Great Lie (continued)</dc:creator>
		<pubDate>Fri, 26 Jun 2009 00:32:35 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/donna_fitzgerald/?p=31#comment-64</guid>
		<description>[...] my last post I discussed two perspectives that will lead to better project results. In this posting I’ll be [...]</description>
		<content:encoded><![CDATA[<p>[...] my last post I discussed two perspectives that will lead to better project results. In this posting I’ll be [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The 4th Great Lie (Continued)</title>
		<link>http://blogs.gartner.com/donna_fitzgerald/2009/05/11/the-fourth-great-lie/comment-page-1/#comment-51</link>
		<dc:creator>The 4th Great Lie (Continued)</dc:creator>
		<pubDate>Wed, 10 Jun 2009 14:06:29 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/donna_fitzgerald/?p=31#comment-51</guid>
		<description>[...] The Fourth Great Lie Saying Thank You [...]</description>
		<content:encoded><![CDATA[<p>[...] The Fourth Great Lie Saying Thank You [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Donna Fitzgerald</title>
		<link>http://blogs.gartner.com/donna_fitzgerald/2009/05/11/the-fourth-great-lie/comment-page-1/#comment-32</link>
		<dc:creator>Donna Fitzgerald</dc:creator>
		<pubDate>Mon, 11 May 2009 21:32:41 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/donna_fitzgerald/?p=31#comment-32</guid>
		<description>Bill,

What caught my eye in your response was the statement “when faced with problems and issues not covered by the rules.”

There are two responses to situations not covered by the rules.  Make more rules and be creative.  As we know, the PM organizations in the US and in the UK have both taken the approach of making more rules.  In some ways their logic makes sense.  If the real work involved in project management is in the messy 20% of projects then a good method should probably help you manage during the times when things get difficult. The problem is that the messy 20% is really messy and very unique.  To John’s comment about the repeatability of projects (http://stasysinc.com/?p=29 ) when you can’t follow the happy path (which is linear and straightforward) you end up with enough branching possibilities to make a quantum physicist happy.  In my next post I’m going to be covering this as the third key element, which is finally acknowledging that the 20% needs to be handled by its own rules.

Donna</description>
		<content:encoded><![CDATA[<p>Bill,</p>
<p>What caught my eye in your response was the statement “when faced with problems and issues not covered by the rules.”</p>
<p>There are two responses to situations not covered by the rules.  Make more rules and be creative.  As we know, the PM organizations in the US and in the UK have both taken the approach of making more rules.  In some ways their logic makes sense.  If the real work involved in project management is in the messy 20% of projects then a good method should probably help you manage during the times when things get difficult. The problem is that the messy 20% is really messy and very unique.  To John’s comment about the repeatability of projects (<a href="http://stasysinc.com/?p=29" rel="nofollow">http://stasysinc.com/?p=29</a> ) when you can’t follow the happy path (which is linear and straightforward) you end up with enough branching possibilities to make a quantum physicist happy.  In my next post I’m going to be covering this as the third key element, which is finally acknowledging that the 20% needs to be handled by its own rules.</p>
<p>Donna</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Duncan</title>
		<link>http://blogs.gartner.com/donna_fitzgerald/2009/05/11/the-fourth-great-lie/comment-page-1/#comment-31</link>
		<dc:creator>Bill Duncan</dc:creator>
		<pubDate>Mon, 11 May 2009 21:05:57 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/donna_fitzgerald/?p=31#comment-31</guid>
		<description>I agree with your objections to your premise as the premise was stated. However, I think there is another, more powerful rationale for methodologies:
&quot;The likelihood of major disasters will be reduced if we force our project managers to stop every so often and fill out some forms. Filling out the forms requires some minimal amount of thought, and that is better than no thinking at all.&quot;
In my experience, methodologies are there for the guidance of the neophytes and for control of the experienced PMs who have refused to learn. One of my clients once documented the following as a key competency for their project managers:
&quot;Follows the rules except when it is necessary not to.&quot;
Warren Bennis makes essentially the same point in &quot;Managing People is Like Herding Cats.&quot; We want people to follow the rules, but we also want them to be creative when faced with problems and issues not covered by the rules.

Duncan</description>
		<content:encoded><![CDATA[<p>I agree with your objections to your premise as the premise was stated. However, I think there is another, more powerful rationale for methodologies:<br />
&#8220;The likelihood of major disasters will be reduced if we force our project managers to stop every so often and fill out some forms. Filling out the forms requires some minimal amount of thought, and that is better than no thinking at all.&#8221;<br />
In my experience, methodologies are there for the guidance of the neophytes and for control of the experienced PMs who have refused to learn. One of my clients once documented the following as a key competency for their project managers:<br />
&#8220;Follows the rules except when it is necessary not to.&#8221;<br />
Warren Bennis makes essentially the same point in &#8220;Managing People is Like Herding Cats.&#8221; We want people to follow the rules, but we also want them to be creative when faced with problems and issues not covered by the rules.</p>
<p>Duncan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Donna Fitzgerald</title>
		<link>http://blogs.gartner.com/donna_fitzgerald/2009/05/11/the-fourth-great-lie/comment-page-1/#comment-30</link>
		<dc:creator>Donna Fitzgerald</dc:creator>
		<pubDate>Mon, 11 May 2009 19:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/donna_fitzgerald/?p=31#comment-30</guid>
		<description>Thanks for linking back.  I&#039;m always delighted to see where my line of thinking leads others.  You correctly focused on what Gerald Nadler (author of Breakthrough Thinking: The Seven Principles of Creative Problem Solving) calls the uniqueness principle.  There is a certain non-repeatability quotient attached to all projects.  Understanding this non-repeatability and in fact capitalizing on it is what separates good PMs from great PMs.  You also indirectly touched on why communities of practice are so important.  It seems that we never think to question why A and not B when alternative A is presented to us as a best practice from a PMO.  BUT if we&#039;re sitting across a table from someone telling us a story about how they were successful with a project by choosing A, we might ask them why they didn&#039;t chose B.  As you pointed out the true value in knowledge sharing is in knowing why A or B made sense in that specific case rather than in just knowing that A worked.</description>
		<content:encoded><![CDATA[<p>Thanks for linking back.  I&#8217;m always delighted to see where my line of thinking leads others.  You correctly focused on what Gerald Nadler (author of Breakthrough Thinking: The Seven Principles of Creative Problem Solving) calls the uniqueness principle.  There is a certain non-repeatability quotient attached to all projects.  Understanding this non-repeatability and in fact capitalizing on it is what separates good PMs from great PMs.  You also indirectly touched on why communities of practice are so important.  It seems that we never think to question why A and not B when alternative A is presented to us as a best practice from a PMO.  BUT if we&#8217;re sitting across a table from someone telling us a story about how they were successful with a project by choosing A, we might ask them why they didn&#8217;t chose B.  As you pointed out the true value in knowledge sharing is in knowing why A or B made sense in that specific case rather than in just knowing that A worked.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IT For The Small Business</title>
		<link>http://blogs.gartner.com/donna_fitzgerald/2009/05/11/the-fourth-great-lie/comment-page-1/#comment-29</link>
		<dc:creator>IT For The Small Business</dc:creator>
		<pubDate>Mon, 11 May 2009 19:21:17 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/donna_fitzgerald/?p=31#comment-29</guid>
		<description>[...] http://blogs.gartner.com/donna_fitzgerald/2009/05/11/the-fourth-great-lie/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://blogs.gartner.com/donna_fitzgerald/2009/05/11/the-fourth-great-lie/" rel="nofollow">http://blogs.gartner.com/donna_fitzgerald/2009/05/11/the-fourth-great-lie/</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
