<?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: Information: The Key to Project Management Success</title>
	<atom:link href="http://pmtips.net/information-key-project-management-success/feed/" rel="self" type="application/rss+xml" />
	<link>http://pmtips.net/information-key-project-management-success/</link>
	<description>Guidance for Real Life Projects</description>
	<lastBuildDate>Wed, 08 Sep 2010 22:36:43 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Carolyn Urban</title>
		<link>http://pmtips.net/information-key-project-management-success/comment-page-1/#comment-2146</link>
		<dc:creator>Carolyn Urban</dc:creator>
		<pubDate>Wed, 20 May 2009 15:44:31 +0000</pubDate>
		<guid isPermaLink="false">http://pmtips.net/?p=1634#comment-2146</guid>
		<description>Couldn’t agree more – accurate information has always been critical, but in this economy it is paramount. In our software implementation projects, we try to use typical IT project ‘governance’ (in a lightweight way) to direct focus on these key elements:

·Continuous review and enhancement of the project documentation
·An explicit governance schedule
·Clear roles and responsibilities for decision making, issue escalation, and dispute management
·Allocation of  resources and expenditures in response to prioritized needs
·Continuous evaluation of performance, cost, satisfaction and effectiveness
·Ongoing communication among all stakeholders</description>
		<content:encoded><![CDATA[<p>Couldn’t agree more – accurate information has always been critical, but in this economy it is paramount. In our software implementation projects, we try to use typical IT project ‘governance’ (in a lightweight way) to direct focus on these key elements:</p>
<p>·Continuous review and enhancement of the project documentation<br />
·An explicit governance schedule<br />
·Clear roles and responsibilities for decision making, issue escalation, and dispute management<br />
·Allocation of  resources and expenditures in response to prioritized needs<br />
·Continuous evaluation of performance, cost, satisfaction and effectiveness<br />
·Ongoing communication among all stakeholders</p>
]]></content:encoded>
	</item>
</channel>
</rss>
