<?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: A Few Issues Every Project Manager Should Prepare For</title>
	<atom:link href="http://www.pmhut.com/a-few-issues-every-project-manager-should-prepare-for/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/a-few-issues-every-project-manager-should-prepare-for</link>
	<description></description>
	<pubDate>Thu, 17 May 2012 03:02:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tom van Lamoen</title>
		<link>http://www.pmhut.com/a-few-issues-every-project-manager-should-prepare-for/comment-page-1#comment-943</link>
		<dc:creator>Tom van Lamoen</dc:creator>
		<pubDate>Tue, 28 Oct 2008 12:50:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/a-few-issues-every-project-manager-should-prepare-for#comment-943</guid>
		<description>&gt; Failing to Report Critical Problems at First Notice

I think another reallly important reason why this happens is that team members just don't see the problem as critical. This can either be because they are not up-to-date on project progress, critical paths, priorities etc, or because they don't interpret the problem correct.

So it's key to keep your team informed (with information they need) and to have correct people for the job.</description>
		<content:encoded><![CDATA[<p>&gt; Failing to Report Critical Problems at First Notice</p>
<p>I think another reallly important reason why this happens is that team members just don&#8217;t see the problem as critical. This can either be because they are not up-to-date on project progress, critical paths, priorities etc, or because they don&#8217;t interpret the problem correct.</p>
<p>So it&#8217;s key to keep your team informed (with information they need) and to have correct people for the job.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LouisvillePM</title>
		<link>http://www.pmhut.com/a-few-issues-every-project-manager-should-prepare-for/comment-page-1#comment-942</link>
		<dc:creator>LouisvillePM</dc:creator>
		<pubDate>Tue, 28 Oct 2008 11:27:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/a-few-issues-every-project-manager-should-prepare-for#comment-942</guid>
		<description>Julian,

Great post!  After experiencing "Critical Members Leaving the Team" myself on a couple of projects, (and it doesn't feel good BTW), I think it should be assessed as a risk at the start of every project.

I think that a general mitigation strategy up front can save a lot of guess work down the road.

-chris</description>
		<content:encoded><![CDATA[<p>Julian,</p>
<p>Great post!  After experiencing &#8220;Critical Members Leaving the Team&#8221; myself on a couple of projects, (and it doesn&#8217;t feel good BTW), I think it should be assessed as a risk at the start of every project.</p>
<p>I think that a general mitigation strategy up front can save a lot of guess work down the road.</p>
<p>-chris</p>
]]></content:encoded>
	</item>
</channel>
</rss>

