<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>PMServicesNW &#187; Project Support</title>
	<atom:link href="http://www.pmservicesnw.com/tag/project-support/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pmservicesnw.com</link>
	<description>Free project management information and downloads</description>
	<lastBuildDate>Tue, 03 May 2011 02:22:21 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
		<item>
		<title>Six common reasons of why projects fail</title>
		<link>http://www.pmservicesnw.com/2010/09/six-common-reasons-of-why-projects-fail/</link>
		<comments>http://www.pmservicesnw.com/2010/09/six-common-reasons-of-why-projects-fail/#comments</comments>
		<pubDate>Sat, 25 Sep 2010 03:49:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Business Change]]></category>
		<category><![CDATA[PMO Services]]></category>
		<category><![CDATA[Project Management Consultancy]]></category>
		<category><![CDATA[Project Support]]></category>
		<category><![CDATA[Technical Change]]></category>

		<guid isPermaLink="false">http://www.pmservicesnw.com/?p=1612</guid>
		<description><![CDATA[To be able to understand project delivery it is important to understand one or two reasons why projects fail. From experience having being commissioned to troubleshoot projects and recommending turnaround strategies here are my top six. 1. Failure to capture and agree business case requirements, therefore not understanding the full set of project deliverables and project objectives. 2. The knock-on effect of misunderstanding what the project business case is meant to deliver leads to poor planning with the plan not reflecting the business case expected outcomes. Plans are nothing but planning is everything. A failure at this early stage will most likely result in the project plagued by mounting issues because not only will planning be incomplete, but also the project will generate more inherent issues and risks. To mitigate the risk and resolve issues will put pressure on the change management process to overcome the deficiencies of planning leading to additional costs and added project complexity. 3. A lack of documentation defining the scope and detail of key deliverables. Documents are key to understanding the what, how, when, who, and precise details in design. Without them a Project Manager will not be able to know the true scope of [...]]]></description>
		<wfw:commentRss>http://www.pmservicesnw.com/2010/09/six-common-reasons-of-why-projects-fail/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

