<?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: Planning a Project Post-Mortem</title>
	<atom:link href="http://www.pmhut.com/planning-a-project-post-mortem/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/planning-a-project-post-mortem</link>
	<description></description>
	<pubDate>Wed, 23 May 2012 17:01:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Phil Simon</title>
		<link>http://www.pmhut.com/planning-a-project-post-mortem/comment-page-1#comment-12607</link>
		<dc:creator>Phil Simon</dc:creator>
		<pubDate>Fri, 27 Nov 2009 11:09:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=3708#comment-12607</guid>
		<description>Gina

Good post. I couldn't agree more with this:

&lt;b&gt;A project post-mortem is one of the most valuable methods available for analyzing weaknesses in a project lifecycle. It gives team members an outlet for their feedback, and provides new perspectives to the Project Manager, who is sometimes too close to the process to assess it objectively.&lt;/b&gt;

What do you do, though, when senior management doesn't want to hear the bad?</description>
		<content:encoded><![CDATA[<p>Gina</p>
<p>Good post. I couldn&#8217;t agree more with this:</p>
<p><b>A project post-mortem is one of the most valuable methods available for analyzing weaknesses in a project lifecycle. It gives team members an outlet for their feedback, and provides new perspectives to the Project Manager, who is sometimes too close to the process to assess it objectively.</b></p>
<p>What do you do, though, when senior management doesn&#8217;t want to hear the bad?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Planning a Project Post-Mortem - Part II - PM Hut</title>
		<link>http://www.pmhut.com/planning-a-project-post-mortem/comment-page-1#comment-9198</link>
		<dc:creator>Planning a Project Post-Mortem - Part II - PM Hut</dc:creator>
		<pubDate>Sun, 20 Sep 2009 05:13:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=3708#comment-9198</guid>
		<description>[...] Planning a Project Post-Mortem - Part II [...]</description>
		<content:encoded><![CDATA[<p>[...] Planning a Project Post-Mortem - Part II [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://www.pmhut.com/planning-a-project-post-mortem/comment-page-1#comment-8990</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Fri, 11 Sep 2009 02:11:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=3708#comment-8990</guid>
		<description>Hi Gina. I've been in a few project Post Implementation Reviews (PIRs) myself and I know how it can quickly descend into the blame game. The survey idea is good in that it avoids conflict and bias.

I came up with 5 tips to help anybody wanting to derive a successful PIR session
http://blog.myprogo.com/progo-document-templates/5-tips-for-successful-project-post-mortems/</description>
		<content:encoded><![CDATA[<p>Hi Gina. I&#8217;ve been in a few project Post Implementation Reviews (PIRs) myself and I know how it can quickly descend into the blame game. The survey idea is good in that it avoids conflict and bias.</p>
<p>I came up with 5 tips to help anybody wanting to derive a successful PIR session<br />
<a href="http://blog.myprogo.com/progo-document-templates/5-tips-for-successful-project-post-mortems/" rel="nofollow">http://blog.myprogo.com/progo-document-templates/5-tips-for-successful-project-post-mortems/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Greer</title>
		<link>http://www.pmhut.com/planning-a-project-post-mortem/comment-page-1#comment-8951</link>
		<dc:creator>Mike Greer</dc:creator>
		<pubDate>Wed, 09 Sep 2009 13:06:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=3708#comment-8951</guid>
		<description>I absolutely agree about the importance of a project post-mortem. And I'd like to add that I've seen such post-mortems used in several organizations as the very beginnings of an ongoing conversation about how PM, in general, might be improved. Here's the typical scenario: 1. One or two people with some PM savvy become aware that there is a problem with the local PM practices.
2. Senior management denies there is such a problem.
3. The PM-savvy people who know there is a problem suggest that they conduct a couple of post-mortems, selecting projects that have had difficulty.
4. The post-mortem flushes out a whole bunch of PM issues and challenges that need to be addressed.
5. The organization is now on a path toward addressing these challenges. 

If you fancy yourself as a "change agent" advocating for PM, then I highly recommend the post-mortem as a gentle, yet powerful, tool that will allow the locals to identify their own PM problems and begin seeking (for themselves) ways to improve. It's great! No external motivation needed!

P.S. -- One of the most popular pages at my website is this free tool "Project 'Post Mortem' Review Questions." It contains 37 questions that can get you started constructing your own Post Mortem review. Here's the URL:
http://www.michaelgreer.com/postmortem.htm</description>
		<content:encoded><![CDATA[<p>I absolutely agree about the importance of a project post-mortem. And I&#8217;d like to add that I&#8217;ve seen such post-mortems used in several organizations as the very beginnings of an ongoing conversation about how PM, in general, might be improved. Here&#8217;s the typical scenario: 1. One or two people with some PM savvy become aware that there is a problem with the local PM practices.<br />
2. Senior management denies there is such a problem.<br />
3. The PM-savvy people who know there is a problem suggest that they conduct a couple of post-mortems, selecting projects that have had difficulty.<br />
4. The post-mortem flushes out a whole bunch of PM issues and challenges that need to be addressed.<br />
5. The organization is now on a path toward addressing these challenges. </p>
<p>If you fancy yourself as a &#8220;change agent&#8221; advocating for PM, then I highly recommend the post-mortem as a gentle, yet powerful, tool that will allow the locals to identify their own PM problems and begin seeking (for themselves) ways to improve. It&#8217;s great! No external motivation needed!</p>
<p>P.S. &#8212; One of the most popular pages at my website is this free tool &#8220;Project &#8216;Post Mortem&#8217; Review Questions.&#8221; It contains 37 questions that can get you started constructing your own Post Mortem review. Here&#8217;s the URL:<br />
<a href="http://www.michaelgreer.com/postmortem.htm" rel="nofollow">http://www.michaelgreer.com/postmortem.htm</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

