<?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 for James Hallam</title>
	<atom:link href="http://jameshallam.com.au/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://jameshallam.com.au</link>
	<description>More Productive Business</description>
	<lastBuildDate>Tue, 17 Jan 2012 12:00:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>Comment on Positive Thinking Hurts So Good — 5 Tips for Project Success by Toots</title>
		<link>http://jameshallam.com.au/2010/09/27/positive-thinking-hurts-good-5-tips-project-success/comment-page-1/#comment-110</link>
		<dc:creator>Toots</dc:creator>
		<pubDate>Tue, 17 Jan 2012 12:00:51 +0000</pubDate>
		<guid isPermaLink="false">http://jameshallam.com.au/?p=754#comment-110</guid>
		<description>All traps can result from poor lead­er­ship / man­age­ment of the project. At first, when recruit­ing a project team, the indi­vid­u­als must be con­vinced that the project will work. Unclear scope, poor com­mu­ni­ca­tion, no role clar­ity, par­tial com­mit­ment from project mem­bers, stick­ing to it are a few com­mon traps. I found that project time­lines, com­ple­tion dates are rarely lucid and don’t stay on target! Hence, a critical path is really essential.

You can avoid these by review­ing project learn­ings and final­i­sa­tion reports if they’re around, and ask­ing ques­tions. Yes we must be account­able, but project mem­bers also look towards their PM to be account­able for each step they do and take to ensure the project comes out a suc­cess and not a flop!</description>
		<content:encoded><![CDATA[<p>All traps can result from poor lead­er­ship / man­age­ment of the project. At first, when recruit­ing a project team, the indi­vid­u­als must be con­vinced that the project will work. Unclear scope, poor com­mu­ni­ca­tion, no role clar­ity, par­tial com­mit­ment from project mem­bers, stick­ing to it are a few com­mon traps. I found that project time­lines, com­ple­tion dates are rarely lucid and don’t stay on target! Hence, a critical path is really essential.</p>
<p>You can avoid these by review­ing project learn­ings and final­i­sa­tion reports if they’re around, and ask­ing ques­tions. Yes we must be account­able, but project mem­bers also look towards their PM to be account­able for each step they do and take to ensure the project comes out a suc­cess and not a flop!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

