<?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: Why The Customer Always Wants His Stuff Tomorrow</title>
	<atom:link href="http://www.projectshrink.com/why-the-customer-always-wants-his-stuff-tomorrow-35.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.projectshrink.com/why-the-customer-always-wants-his-stuff-tomorrow-35.html</link>
	<description>Welcome To Shrinkonia.</description>
	<lastBuildDate>Sun, 20 May 2012 21:13:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Oren Cohen-Shwartz</title>
		<link>http://www.projectshrink.com/why-the-customer-always-wants-his-stuff-tomorrow-35.html#comment-57</link>
		<dc:creator>Oren Cohen-Shwartz</dc:creator>
		<pubDate>Thu, 02 Aug 2007 08:03:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/why-the-customer-always-wants-his-stuff-tomorrow-35.html#comment-57</guid>
		<description>Customers want the stuff tomorrow because they need it ASAP.
One can&#039;t blame the customer urgency.
Having a real customer on hand is fantastic for the company to R&amp;D.
Smart Project Manager participate his team with the customer information.
All the team members need to know the big picture: Customer name, location,  needs etc.
My assumption is based on that people want to be involved, contribute and create successful software for the customer.
Knowing for whom you are working for grant focus and feeling of accomplishments. In this kind of atmosphere it is much more easy to make employees agreed with harsh deadlines.</description>
		<content:encoded><![CDATA[<p>Customers want the stuff tomorrow because they need it ASAP.<br />
One can&#8217;t blame the customer urgency.<br />
Having a real customer on hand is fantastic for the company to R&amp;D.<br />
Smart Project Manager participate his team with the customer information.<br />
All the team members need to know the big picture: Customer name, location,  needs etc.<br />
My assumption is based on that people want to be involved, contribute and create successful software for the customer.<br />
Knowing for whom you are working for grant focus and feeling of accomplishments. In this kind of atmosphere it is much more easy to make employees agreed with harsh deadlines.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ann Brown</title>
		<link>http://www.projectshrink.com/why-the-customer-always-wants-his-stuff-tomorrow-35.html#comment-56</link>
		<dc:creator>Ann Brown</dc:creator>
		<pubDate>Mon, 30 Jul 2007 21:23:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/why-the-customer-always-wants-his-stuff-tomorrow-35.html#comment-56</guid>
		<description>Same thing happens in supply chain management when people do not trust the process - they hoard, over order, under promise etc. until the whole process is completely undermined.

Customers demand delivery &quot;next Tuesday&quot; as they believe that only the squeaky wheel will get attention. PM promise &quot;as soon as I can&quot; to put them off...and also because they believe that there&#039;s not point in guaranteeing a time as no-one is working to the plan anway.

What a sad situation and how unhappy for customers and suppliers...and downright miserbale for the project manager.

Good project managers (and organizations) work to build trust in the process of specifications to delivery. And the trust must be with the customer and within the team. Project Manager as relationship builder - what a concept!</description>
		<content:encoded><![CDATA[<p>Same thing happens in supply chain management when people do not trust the process &#8211; they hoard, over order, under promise etc. until the whole process is completely undermined.</p>
<p>Customers demand delivery &#8220;next Tuesday&#8221; as they believe that only the squeaky wheel will get attention. PM promise &#8220;as soon as I can&#8221; to put them off&#8230;and also because they believe that there&#8217;s not point in guaranteeing a time as no-one is working to the plan anway.</p>
<p>What a sad situation and how unhappy for customers and suppliers&#8230;and downright miserbale for the project manager.</p>
<p>Good project managers (and organizations) work to build trust in the process of specifications to delivery. And the trust must be with the customer and within the team. Project Manager as relationship builder &#8211; what a concept!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Snik</title>
		<link>http://www.projectshrink.com/why-the-customer-always-wants-his-stuff-tomorrow-35.html#comment-55</link>
		<dc:creator>Snik</dc:creator>
		<pubDate>Mon, 30 Jul 2007 16:35:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/why-the-customer-always-wants-his-stuff-tomorrow-35.html#comment-55</guid>
		<description>With an &#039;unreasonably&#039; short deadline, I think that the guys at the bottom of the stack who actually have to do the work immediately start to doubt the seriousness or competence of the decision makers. That is the start of a downward trend in trust and respect. Of course, if the workforce were already on that downward slope, a deadline or two makes little difference.
With a more generous deadline than &#039;necessary&#039; a motivated workforce almost feels compelled to refine, tweak, improve and enhance a project that could otherwise be very simply, quickly and efficiently completed. But as you stated, if the workforce was never very motivated in the first place, then all the time in the world would be of little help to the project.
This article seems to make a lot of sense.</description>
		<content:encoded><![CDATA[<p>With an &#8216;unreasonably&#8217; short deadline, I think that the guys at the bottom of the stack who actually have to do the work immediately start to doubt the seriousness or competence of the decision makers. That is the start of a downward trend in trust and respect. Of course, if the workforce were already on that downward slope, a deadline or two makes little difference.<br />
With a more generous deadline than &#8216;necessary&#8217; a motivated workforce almost feels compelled to refine, tweak, improve and enhance a project that could otherwise be very simply, quickly and efficiently completed. But as you stated, if the workforce was never very motivated in the first place, then all the time in the world would be of little help to the project.<br />
This article seems to make a lot of sense.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bas</title>
		<link>http://www.projectshrink.com/why-the-customer-always-wants-his-stuff-tomorrow-35.html#comment-54</link>
		<dc:creator>Bas</dc:creator>
		<pubDate>Sun, 29 Jul 2007 11:08:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/why-the-customer-always-wants-his-stuff-tomorrow-35.html#comment-54</guid>
		<description>Pawel Brodzinski wrote a response to this posting on his great blog. Definitely worth checking out:

http://blog.brodzinski.com/2007/07/setting-deadlines.html</description>
		<content:encoded><![CDATA[<p>Pawel Brodzinski wrote a response to this posting on his great blog. Definitely worth checking out:</p>
<p><a href="http://blog.brodzinski.com/2007/07/setting-deadlines.html" rel="nofollow">http://blog.brodzinski.com/2007/07/setting-deadlines.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

