<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Project Management Collaboration and Communication Tools</title>
	<atom:link href="http://fearnoproject.com/2010/07/16/project-management-collaboration-and-communication-tools/feed/" rel="self" type="application/rss+xml" />
	<link>http://fearnoproject.com/2010/07/16/project-management-collaboration-and-communication-tools/</link>
	<description>Thoughts, experience, tips and tricks on issues affecting project managers and project management</description>
	<lastBuildDate>Fri, 27 Jan 2012 04:26:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: PM Colors – Greening project management &#171; Fear No Project &#8211; A Project Management Blog</title>
		<link>http://fearnoproject.com/2010/07/16/project-management-collaboration-and-communication-tools/#comment-553</link>
		<dc:creator><![CDATA[PM Colors – Greening project management &#171; Fear No Project &#8211; A Project Management Blog]]></dc:creator>
		<pubDate>Thu, 02 Sep 2010 11:47:28 +0000</pubDate>
		<guid isPermaLink="false">http://fearnoproject.com/?p=504#comment-553</guid>
		<description><![CDATA[[...] : don’t print email, tag it and use an electronic reader with highlighting capability, use collaborative tools, and make “green” part of proposal and contract [...]]]></description>
		<content:encoded><![CDATA[<p>[...] : don’t print email, tag it and use an electronic reader with highlighting capability, use collaborative tools, and make “green” part of proposal and contract [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pawel Brodzinski</title>
		<link>http://fearnoproject.com/2010/07/16/project-management-collaboration-and-communication-tools/#comment-485</link>
		<dc:creator><![CDATA[Pawel Brodzinski]]></dc:creator>
		<pubDate>Fri, 23 Jul 2010 11:17:03 +0000</pubDate>
		<guid isPermaLink="false">http://fearnoproject.com/?p=504#comment-485</guid>
		<description><![CDATA[To some point I agree. Communication is always a problem and we should work constantly on improving it. After all it is &lt;a href=&quot;http://blog.brodzinski.com/2009/06/is-it-possible-to-over-communicate-in.html&quot; rel=&quot;nofollow&quot;&gt;almost impossible to over-communicate in project teams&lt;/a&gt;.

A thing I don&#039;t agree with is your approach to tools. I may be biased since you mention SharePoint, Live Messenger and Google Wave which all suck in my opinion. Anyway, I believe we should keep our toolboxes as simple as possible. No video shared via SharePoint will match value of simple face to face discussion. Neither will Wave thread.

What more, it is so much simpler to take a look at a whiteboard where you can see current project status (presented in this way or another) than to run an application, dig through lists of tasks, charts and reports.

In my current team we use bug tracker/tasks list (one tool) and shared repository and that&#039;s basically all software tools we use. I would say that if you can stop using some tool and it doesn&#039;t do much harm to your team you should. Or exchange it with something more trivial. Like a whiteboard and markers or a handful of sticky notes.]]></description>
		<content:encoded><![CDATA[<p>To some point I agree. Communication is always a problem and we should work constantly on improving it. After all it is <a href="http://blog.brodzinski.com/2009/06/is-it-possible-to-over-communicate-in.html" rel="nofollow">almost impossible to over-communicate in project teams</a>.</p>
<p>A thing I don&#8217;t agree with is your approach to tools. I may be biased since you mention SharePoint, Live Messenger and Google Wave which all suck in my opinion. Anyway, I believe we should keep our toolboxes as simple as possible. No video shared via SharePoint will match value of simple face to face discussion. Neither will Wave thread.</p>
<p>What more, it is so much simpler to take a look at a whiteboard where you can see current project status (presented in this way or another) than to run an application, dig through lists of tasks, charts and reports.</p>
<p>In my current team we use bug tracker/tasks list (one tool) and shared repository and that&#8217;s basically all software tools we use. I would say that if you can stop using some tool and it doesn&#8217;t do much harm to your team you should. Or exchange it with something more trivial. Like a whiteboard and markers or a handful of sticky notes.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

