<?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: The Power of Gossip</title>
	<atom:link href="http://blog.brodzinski.com/2007/09/power-of-gossip.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.brodzinski.com/2007/09/power-of-gossip.html</link>
	<description>Dealing with software projects in real life</description>
	<lastBuildDate>Thu, 29 Jul 2010 10:46:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Pawel Brodzinski</title>
		<link>http://blog.brodzinski.com/2007/09/power-of-gossip.html#comment-1922</link>
		<dc:creator>Pawel Brodzinski</dc:creator>
		<pubDate>Tue, 18 Sep 2007 07:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2007/09/the-power-of-gossip.html#comment-1922</guid>
		<description>Interesting perspective. I haven&#039;t looked at gossips that way. Probably it was so because I usually had a chance (and guts) to present information directly with no risk of executing the messenger.</description>
		<content:encoded><![CDATA[<p>Interesting perspective. I haven&#8217;t looked at gossips that way. Probably it was so because I usually had a chance (and guts) to present information directly with no risk of executing the messenger.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig</title>
		<link>http://blog.brodzinski.com/2007/09/power-of-gossip.html#comment-1921</link>
		<dc:creator>Craig</dc:creator>
		<pubDate>Tue, 18 Sep 2007 07:11:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2007/09/the-power-of-gossip.html#comment-1921</guid>
		<description>Yes, good article.&lt;br/&gt;&lt;br/&gt;You can use gossip to your advantage also.  When setting up stakeholdes for decisions or managing change into the organsaition you can use gossip as a softener, to unfreeze thinking and getnthem ready for what is coming.</description>
		<content:encoded><![CDATA[<p>Yes, good article.</p>
<p>You can use gossip to your advantage also.  When setting up stakeholdes for decisions or managing change into the organsaition you can use gossip as a softener, to unfreeze thinking and getnthem ready for what is coming.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pawel Brodzinski</title>
		<link>http://blog.brodzinski.com/2007/09/power-of-gossip.html#comment-1920</link>
		<dc:creator>Pawel Brodzinski</dc:creator>
		<pubDate>Wed, 12 Sep 2007 16:06:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2007/09/the-power-of-gossip.html#comment-1920</guid>
		<description>People often talk off the record about things which won&#039;t be repeated in front of their bosses. One of reasons is natural fear of people who are &quot;more important.&quot; Another thing is atmosphere in the organization - when the messenger with bad news is executed you&#039;ll never hear all of the team&#039;s fears.</description>
		<content:encoded><![CDATA[<p>People often talk off the record about things which won&#8217;t be repeated in front of their bosses. One of reasons is natural fear of people who are &#8220;more important.&#8221; Another thing is atmosphere in the organization &#8211; when the messenger with bad news is executed you&#8217;ll never hear all of the team&#8217;s fears.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barry Gilbert</title>
		<link>http://blog.brodzinski.com/2007/09/power-of-gossip.html#comment-1919</link>
		<dc:creator>Barry Gilbert</dc:creator>
		<pubDate>Wed, 12 Sep 2007 14:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2007/09/the-power-of-gossip.html#comment-1919</guid>
		<description>Pawel&lt;br/&gt;Great piece, it certainly struck a chord with me. Working for many years in the Requirements Management area I could only hope stake holders would communicate ideas and issues to the project leads and developers as quickly as they would gossip about what they watched last night on TV or where they went drinking.&lt;br/&gt;I also find it odd that people can chat “off the record” near the coffee machine about what’s  going wrong, but never repeat the comments in a meeting. Only confessing up when the project is delivered that actually the need they had previously documented had changed or simply gone away! Actually no one ever admitted that –they simply blamed everyone else for mis-interpreting the requirement.</description>
		<content:encoded><![CDATA[<p>Pawel<br />Great piece, it certainly struck a chord with me. Working for many years in the Requirements Management area I could only hope stake holders would communicate ideas and issues to the project leads and developers as quickly as they would gossip about what they watched last night on TV or where they went drinking.<br />I also find it odd that people can chat “off the record” near the coffee machine about what’s  going wrong, but never repeat the comments in a meeting. Only confessing up when the project is delivered that actually the need they had previously documented had changed or simply gone away! Actually no one ever admitted that –they simply blamed everyone else for mis-interpreting the requirement.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
