<?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: Closing a Project - Post Project Review</title>
	<atom:link href="http://www.pmhut.com/closing-a-project-post-project-review/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/closing-a-project-post-project-review</link>
	<description></description>
	<pubDate>Mon, 21 May 2012 14:26:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rajendra P. Adhikari</title>
		<link>http://www.pmhut.com/closing-a-project-post-project-review/comment-page-1#comment-48858</link>
		<dc:creator>Rajendra P. Adhikari</dc:creator>
		<pubDate>Sat, 23 Jul 2011 18:15:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=5336#comment-48858</guid>
		<description>The articles are found very useful and clear. I found this site as a best site for both - new to Project Management as well as to the practiotiners also.</description>
		<content:encoded><![CDATA[<p>The articles are found very useful and clear. I found this site as a best site for both - new to Project Management as well as to the practiotiners also.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Perry</title>
		<link>http://www.pmhut.com/closing-a-project-post-project-review/comment-page-1#comment-20960</link>
		<dc:creator>Perry</dc:creator>
		<pubDate>Wed, 12 May 2010 16:13:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=5336#comment-20960</guid>
		<description>It seems the closing phase of the project is easy to ignore, after all everyone wants to get on to their new project and no one wants to hash over the problems of the last one. Unfortunately, the next project could benefit from the information gathered during the closing of previous projects. 

I have used a few different tactics to gather the project closing information that have worked. 

1 -don't wait until the project is over, do a review of key phases, or of issue resolutions
2- break the review teams into smaller groups to get the information faster. 
3 - do as much as possible through surveys, or other online to give people the opportunity to do it on their own schedule. 

thanks for the post.</description>
		<content:encoded><![CDATA[<p>It seems the closing phase of the project is easy to ignore, after all everyone wants to get on to their new project and no one wants to hash over the problems of the last one. Unfortunately, the next project could benefit from the information gathered during the closing of previous projects. </p>
<p>I have used a few different tactics to gather the project closing information that have worked. </p>
<p>1 -don&#8217;t wait until the project is over, do a review of key phases, or of issue resolutions<br />
2- break the review teams into smaller groups to get the information faster.<br />
3 - do as much as possible through surveys, or other online to give people the opportunity to do it on their own schedule. </p>
<p>thanks for the post.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

