<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Obstacles to Project Communication</title>
	<link>http://www.pmhut.com/obstacles-to-project-communication</link>
	<description>The Project Manager's Hut</description>
	<pubDate>Tue, 07 Oct 2008 12:55:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.3</generator>

	<item>
		<title>By: PM Hut &#187; Portents of Project Failure</title>
		<link>http://www.pmhut.com/obstacles-to-project-communication#comment-4701</link>
		<author>PM Hut &#187; Portents of Project Failure</author>
		<pubDate>Sun, 30 Mar 2008 05:01:40 +0000</pubDate>
		<guid>http://www.pmhut.com/obstacles-to-project-communication#comment-4701</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>[&#8230;] 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. [&#8230;]</p>
]]></content:encoded>
				</item>
</channel>
</rss>
