<?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: Let&#8217;s Be Prudent</title>
	<link>http://www.reformingprojectmanagement.com/2003/09/07/246/</link>
	<description>The magazine for the project age</description>
	<pubDate>Sat, 11 Oct 2008 15:28:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Garrie Hankins
        </title>
		<link>http://www.reformingprojectmanagement.com/2003/09/07/246/#comment-43</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2003/09/07/246/#comment-43</guid>
					<description>
        Project success is always a subjective judgment of the customer, project team and stakeholders. 

I believe that the key to project success is in managing the expectations of your customer.

From project initiation to closing the PM must struggle to keep the expectations of all project stakeholders grounded in reality.

All of us have requests made of project team that are entirely unrealistic (unstructured requirements and unrealistic dates being the most common). These issues are ‘project killers’ and must be addressed. As soon as the unrealistic demand is placed on the project the PM is responsible for communicating this to the customer and all stakeholders.

I can feel at this point the question “But what if the customer refuses to accept the PM’s explanation of the problem and continues to believe that the impossible is doable?” 

This is where your project change control and communications plan kicks in. The PM must do an assessment of the risk (which is what unrealistic expectations are) and communicate it to all the project stakeholders. 

At this point, one of the project stakeholders is bound to take this up as an issue that needs to be addressed. If no one objects and everyone sticks their head in the sand then they have accepted the risk. 

When the project does not meet expectations due to refusal to address the unrealistic expectations of the customer, the PM should bring out the risk assessment and point to the failure to address the risk as the cause. 

This may not help very much politically. But when the PM has properly documented the failure to address the risk, the organization will have an opportunity to learn from the mistake.
      </description>
		<content:encoded><![CDATA[<p>Project success is always a subjective judgment of the customer, project team and stakeholders. </p>
<p>I believe that the key to project success is in managing the expectations of your customer.</p>
<p>From project initiation to closing the PM must struggle to keep the expectations of all project stakeholders grounded in reality.</p>
<p>All of us have requests made of project team that are entirely unrealistic (unstructured requirements and unrealistic dates being the most common). These issues are ‘project killers’ and must be addressed. As soon as the unrealistic demand is placed on the project the PM is responsible for communicating this to the customer and all stakeholders.</p>
<p>I can feel at this point the question “But what if the customer refuses to accept the PM’s explanation of the problem and continues to believe that the impossible is doable?” </p>
<p>This is where your project change control and communications plan kicks in. The PM must do an assessment of the risk (which is what unrealistic expectations are) and communicate it to all the project stakeholders. </p>
<p>At this point, one of the project stakeholders is bound to take this up as an issue that needs to be addressed. If no one objects and everyone sticks their head in the sand then they have accepted the risk. </p>
<p>When the project does not meet expectations due to refusal to address the unrealistic expectations of the customer, the PM should bring out the risk assessment and point to the failure to address the risk as the cause. </p>
<p>This may not help very much politically. But when the PM has properly documented the failure to address the risk, the organization will have an opportunity to learn from the mistake.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
