<?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: Obstacles to Project Communication</title>
	<atom:link href="http://www.pmhut.com/obstacles-to-project-communication/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/obstacles-to-project-communication</link>
	<description></description>
	<pubDate>Sat, 11 Feb 2012 20:42:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: PM Hut &#187; Portents of Project Failure</title>
		<link>http://www.pmhut.com/obstacles-to-project-communication/comment-page-1#comment-581</link>
		<dc:creator>PM Hut &#187; Portents of Project Failure</dc:creator>
		<pubDate>Sun, 30 Mar 2008 05:01:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/obstacles-to-project-communication#comment-581</guid>
		<description>[...] Chronic buck-passing: A typical case of this might be where a team member says, ”I coudn&#8217;t finish on time because X didn&#8217;t give me what he was supposed to last week.” Project roles and responsibilities should be defined in the plan, and I&#8217;m assuming that this is the case (if not you have bigger problems!). In a situation where responsibilities are defined, buck-passing is usually a consequence of communication breakdown across a project interface. This has to be handled by smoothing out the obstacles to communication. [...]</description>
		<content:encoded><![CDATA[<p>[...] Chronic buck-passing: A typical case of this might be where a team member says, ”I coudn&#8217;t finish on time because X didn&#8217;t give me what he was supposed to last week.” Project roles and responsibilities should be defined in the plan, and I&#8217;m assuming that this is the case (if not you have bigger problems!). In a situation where responsibilities are defined, buck-passing is usually a consequence of communication breakdown across a project interface. This has to be handled by smoothing out the obstacles to communication. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

