<?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 for The Other Man&#039;s Opinion!</title>
	<atom:link href="http://stasysinc.com/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://stasysinc.com</link>
	<description>The views of a senior geek!</description>
	<lastBuildDate>Mon, 11 May 2009 21:34:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>Comment on Are successful projects easily repeatable &#8211; Maybe not! by Donna Fitzgerald</title>
		<link>http://stasysinc.com/?p=29&#038;cpage=1#comment-40</link>
		<dc:creator>Donna Fitzgerald</dc:creator>
		<pubDate>Mon, 11 May 2009 21:34:26 +0000</pubDate>
		<guid isPermaLink="false">http://stasysinc.com/?p=29#comment-40</guid>
		<description>Thanks for linking back. I’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’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’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’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’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’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>
</channel>
</rss>
