<?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"
	>
<channel>
	<title>Comments on: Someone should have shown Grandma the project plan.</title>
	<atom:link href="http://workitmom.com/bloggers/whostolemystapler/2008/02/07/someone-should-have-shown-grandma-the-project-plan/feed/" rel="self" type="application/rss+xml" />
	<link>http://workitmom.com/bloggers/whostolemystapler/2008/02/07/someone-should-have-shown-grandma-the-project-plan/</link>
	<description>From surviving to thriving in the corporate world.</description>
	<pubDate>Thu, 04 Dec 2008 00:12:12 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Kate</title>
		<link>http://workitmom.com/bloggers/whostolemystapler/2008/02/07/someone-should-have-shown-grandma-the-project-plan/#comment-223</link>
		<dc:creator>Kate</dc:creator>
		<pubDate>Mon, 11 Feb 2008 21:28:58 +0000</pubDate>
		<guid isPermaLink="false">http://workitmom.com/bloggers/whostolemystapler/2008/02/07/someone-should-have-shown-grandma-the-project-plan/#comment-223</guid>
		<description>If you want to delete the big huge one - i posted it on my blog here:  

http://neatokeen.blogspot.com/2008/02/i-told-you-so.html 

so as to free up some space for ya!

glad to hear that grandma is doing better!</description>
		<content:encoded><![CDATA[<p>If you want to delete the big huge one - i posted it on my blog here:  </p>
<p><a href="http://neatokeen.blogspot.com/2008/02/i-told-you-so.html" rel="nofollow">http://neatokeen.blogspot.com/2008/02/i-told-you-so.html</a> </p>
<p>so as to free up some space for ya!</p>
<p>glad to hear that grandma is doing better!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diane</title>
		<link>http://workitmom.com/bloggers/whostolemystapler/2008/02/07/someone-should-have-shown-grandma-the-project-plan/#comment-221</link>
		<dc:creator>Diane</dc:creator>
		<pubDate>Mon, 11 Feb 2008 17:21:05 +0000</pubDate>
		<guid isPermaLink="false">http://workitmom.com/bloggers/whostolemystapler/2008/02/07/someone-should-have-shown-grandma-the-project-plan/#comment-221</guid>
		<description>Just want to say sorry about your grandma.</description>
		<content:encoded><![CDATA[<p>Just want to say sorry about your grandma.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daisy</title>
		<link>http://workitmom.com/bloggers/whostolemystapler/2008/02/07/someone-should-have-shown-grandma-the-project-plan/#comment-219</link>
		<dc:creator>Daisy</dc:creator>
		<pubDate>Mon, 11 Feb 2008 02:21:34 +0000</pubDate>
		<guid isPermaLink="false">http://workitmom.com/bloggers/whostolemystapler/2008/02/07/someone-should-have-shown-grandma-the-project-plan/#comment-219</guid>
		<description>I understand, even though I'm not in your field. I'm an elementary teacher, and nothing, but nothing, is ever predictable. But tests still go as scheduled and report cards are still due on time. Now if only our legislators recognized that...
I wish you good luck with Grandma's health. It's tough to want to be with her, but need to be far away.</description>
		<content:encoded><![CDATA[<p>I understand, even though I&#8217;m not in your field. I&#8217;m an elementary teacher, and nothing, but nothing, is ever predictable. But tests still go as scheduled and report cards are still due on time. Now if only our legislators recognized that&#8230;<br />
I wish you good luck with Grandma&#8217;s health. It&#8217;s tough to want to be with her, but need to be far away.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kate</title>
		<link>http://workitmom.com/bloggers/whostolemystapler/2008/02/07/someone-should-have-shown-grandma-the-project-plan/#comment-216</link>
		<dc:creator>kate</dc:creator>
		<pubDate>Sat, 09 Feb 2008 19:04:53 +0000</pubDate>
		<guid isPermaLink="false">http://workitmom.com/bloggers/whostolemystapler/2008/02/07/someone-should-have-shown-grandma-the-project-plan/#comment-216</guid>
		<description>KathyHowe!  I feel your pain!  You have forced me to write a very long post – I should just put it on my blog and link but that would be far too practical.  Enjoy… 

As a PM I have learned that the best way to handle HUGE unexpected craziness is to communicate communicate communicate.  

But what should be communicated?  (you know you want to know…)

The remaining team members and project manager need to brainstorm and come up with options (at least three!) for mitigating all of the issues that seem uncontrollable.  Easier said that done because there is ALWAYS someone who says ‘that will never work’ ignore them and write it down.  Once you have your options (hire temps, suck it up and push the timelines out, reduce the scope, etc.) you put together a pretty document with your successes, issues, and mitigation options and how each would impact the project.  Also include how doing nothing would impact the project.  Make sure to make it sound scary and expensive.  

Then you let management decide which direction to go with and update them on the progress and document the changes, etc.  

If they still insist it be done on time and on budget then just communicate the status, issues, and brace your self for not making it on time and on budget!  And document over and over that you and they are aware of all the issues and the recommendations made to mitigate even if they weren’t taken.

Luckily (or not?) I work for a company whose management tends to toss wrenches into the project.  A few examples:

•  I know the technical team prefers to purchase X product, but you have to purchase Y instead because they are a business partner even if the product doesn’t work as well.
•  You can’t deploy xyz software update tomorrow, we need to pilot here and there for four weeks first even though we have known about this for the last 6 months and never bothered to tell you.  
•  No you cannot implement that server in the data center for the new application because we are out of space/power/people/cables/etc. for two more months
•  Even though using hardware X is our directive, this software we already purchased is business critical and won’t run on that hardware so you need to figure out how to change it.

The lucky part is that they usually at least allow time and budget changes when something like this comes up.  As long as they know what is going on they are open to mitigation strategies and other options to make it work.  

The big picture goal is to make the company successful, right?  The easiest way to do that is to make sure everyone involved is aware of what is going on so they can help.  Most people really do want to help make you, the project, and the company successful.</description>
		<content:encoded><![CDATA[<p>KathyHowe!  I feel your pain!  You have forced me to write a very long post – I should just put it on my blog and link but that would be far too practical.  Enjoy… </p>
<p>As a PM I have learned that the best way to handle HUGE unexpected craziness is to communicate communicate communicate.  </p>
<p>But what should be communicated?  (you know you want to know…)</p>
<p>The remaining team members and project manager need to brainstorm and come up with options (at least three!) for mitigating all of the issues that seem uncontrollable.  Easier said that done because there is ALWAYS someone who says ‘that will never work’ ignore them and write it down.  Once you have your options (hire temps, suck it up and push the timelines out, reduce the scope, etc.) you put together a pretty document with your successes, issues, and mitigation options and how each would impact the project.  Also include how doing nothing would impact the project.  Make sure to make it sound scary and expensive.  </p>
<p>Then you let management decide which direction to go with and update them on the progress and document the changes, etc.  </p>
<p>If they still insist it be done on time and on budget then just communicate the status, issues, and brace your self for not making it on time and on budget!  And document over and over that you and they are aware of all the issues and the recommendations made to mitigate even if they weren’t taken.</p>
<p>Luckily (or not?) I work for a company whose management tends to toss wrenches into the project.  A few examples:</p>
<p>•  I know the technical team prefers to purchase X product, but you have to purchase Y instead because they are a business partner even if the product doesn’t work as well.<br />
•  You can’t deploy xyz software update tomorrow, we need to pilot here and there for four weeks first even though we have known about this for the last 6 months and never bothered to tell you.<br />
•  No you cannot implement that server in the data center for the new application because we are out of space/power/people/cables/etc. for two more months<br />
•  Even though using hardware X is our directive, this software we already purchased is business critical and won’t run on that hardware so you need to figure out how to change it.</p>
<p>The lucky part is that they usually at least allow time and budget changes when something like this comes up.  As long as they know what is going on they are open to mitigation strategies and other options to make it work.  </p>
<p>The big picture goal is to make the company successful, right?  The easiest way to do that is to make sure everyone involved is aware of what is going on so they can help.  Most people really do want to help make you, the project, and the company successful.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
