<?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: Five Dangers of Poor Project Communication</title>
	<atom:link href="http://www.pmhut.com/five-dangers-of-poor-project-communication/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/five-dangers-of-poor-project-communication</link>
	<description></description>
	<pubDate>Tue, 22 May 2012 19:39:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dina Garfinkel, PMP</title>
		<link>http://www.pmhut.com/five-dangers-of-poor-project-communication/comment-page-1#comment-14562</link>
		<dc:creator>Dina Garfinkel, PMP</dc:creator>
		<pubDate>Wed, 30 Dec 2009 19:13:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4475#comment-14562</guid>
		<description>All good points! I love the idea of purchasing traffic lights to let people know whether they can approach you or not. Those desk visits can start with a project related question but easily drift to something totally irrelevant. Not to say it's not pleasant to chat with nice people, bit it can be a huge time suck. 

As for points 1 and 2, I suggest using LiquidPlanner (http://www.liquidplanner.com/) for project communication. LP is a great place to share documents, notes on specifics of the project, and just in general keep all relevant details in one place where all team members (and clients) can access it at any time.</description>
		<content:encoded><![CDATA[<p>All good points! I love the idea of purchasing traffic lights to let people know whether they can approach you or not. Those desk visits can start with a project related question but easily drift to something totally irrelevant. Not to say it&#8217;s not pleasant to chat with nice people, bit it can be a huge time suck. </p>
<p>As for points 1 and 2, I suggest using LiquidPlanner (http://www.liquidplanner.com/) for project communication. LP is a great place to share documents, notes on specifics of the project, and just in general keep all relevant details in one place where all team members (and clients) can access it at any time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Revv</title>
		<link>http://www.pmhut.com/five-dangers-of-poor-project-communication/comment-page-1#comment-14540</link>
		<dc:creator>Revv</dc:creator>
		<pubDate>Wed, 30 Dec 2009 11:00:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4475#comment-14540</guid>
		<description>Nice read! My pick of the lot would be point 4 :) No amount of efficiency can actually solve this one since you are being efficient on something that's gonna change.</description>
		<content:encoded><![CDATA[<p>Nice read! My pick of the lot would be point 4 :) No amount of efficiency can actually solve this one since you are being efficient on something that&#8217;s gonna change.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

