<?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: Not Managing Perceptions: The 10th Waste of Project Management</title>
	<link>http://www.reformingprojectmanagement.com/2008/01/11/854/</link>
	<description>The magazine for the project age</description>
	<pubDate>Wed, 08 Oct 2008 08:45:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Claude Emond</title>
		<link>http://www.reformingprojectmanagement.com/2008/01/11/854/#comment-20709</link>
		<pubDate>Wed, 16 Jan 2008 23:20:22 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2008/01/11/854/#comment-20709</guid>
					<description>Diana, you sure give a good example of the problems caused in an organization by different perceptions of success. I ran into a very similar «sad» situation during one of my PM workshops for a Processed Food Company (mainly milk transformation). They have on the Canadian market now one of the most successful new soft cheese produced from raw milk: the star of their new products. However, the «new product development» project manager who delivered this wonder with his team was blamed for not respecting the initial schedule and budget. My feeling and that of the people reporting this situation to me was that, if he had focused on delivering the initial «constraints» (that is what schedule and budget are, not «objectives») instead of on delivering a market winner (which was the initial intention, the real objective to preserve), he would have been a hero.... and the marketing people, stuck with pushing a bad cheese on the market, would have been the ones blamed. Two different internal stakeholders, measured using two different success criteria that are not mutually exclusive but are often considered as such. Very sad indeed...So the final user, me (the consumer), will thanks this project manager for this fabulous cheese if ever I meet him.</description>
		<content:encoded><![CDATA[<p>Diana, you sure give a good example of the problems caused in an organization by different perceptions of success. I ran into a very similar «sad» situation during one of my PM workshops for a Processed Food Company (mainly milk transformation). They have on the Canadian market now one of the most successful new soft cheese produced from raw milk: the star of their new products. However, the «new product development» project manager who delivered this wonder with his team was blamed for not respecting the initial schedule and budget. My feeling and that of the people reporting this situation to me was that, if he had focused on delivering the initial «constraints» (that is what schedule and budget are, not «objectives») instead of on delivering a market winner (which was the initial intention, the real objective to preserve), he would have been a hero&#8230;. and the marketing people, stuck with pushing a bad cheese on the market, would have been the ones blamed. Two different internal stakeholders, measured using two different success criteria that are not mutually exclusive but are often considered as such. Very sad indeed&#8230;So the final user, me (the consumer), will thanks this project manager for this fabulous cheese if ever I meet him.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Diana Hutchinson</title>
		<link>http://www.reformingprojectmanagement.com/2008/01/11/854/#comment-20706</link>
		<pubDate>Mon, 14 Jan 2008 15:54:38 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2008/01/11/854/#comment-20706</guid>
					<description>As a project manager, I'm always interested in the statistics about how many projects are successful, and what exactly does success mean, anyway?  I heard a speaker last week who stated the "Big Dig" and "DIA" (Denver Airport) were both total failures.  From a cost/schedule point of view these projects definitely missed the mark.  But I had to disagree with his conclusion, that they were total failures.  Both projects produced something of worth in my mind.  
Thanks to Claude for a good reminder of the importance of working closely with all the stakeholders to make sure my projects will be in those considered a success.</description>
		<content:encoded><![CDATA[<p>As a project manager, I&#8217;m always interested in the statistics about how many projects are successful, and what exactly does success mean, anyway?  I heard a speaker last week who stated the &#8220;Big Dig&#8221; and &#8220;DIA&#8221; (Denver Airport) were both total failures.  From a cost/schedule point of view these projects definitely missed the mark.  But I had to disagree with his conclusion, that they were total failures.  Both projects produced something of worth in my mind.<br />
Thanks to Claude for a good reminder of the importance of working closely with all the stakeholders to make sure my projects will be in those considered a success.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
