<?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: My Theory on Why IT Projects Fail</title>
	<atom:link href="http://www.pmhut.com/my-theory-on-why-it-projects-fail/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/my-theory-on-why-it-projects-fail</link>
	<description></description>
	<pubDate>Sat, 11 Feb 2012 20:00:27 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andy</title>
		<link>http://www.pmhut.com/my-theory-on-why-it-projects-fail/comment-page-1#comment-40361</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Mon, 18 Apr 2011 20:31:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/my-theory-on-why-it-projects-fail#comment-40361</guid>
		<description>Surely the declaration of a successful project is defined in any software development contract?  I would be very surprised otherwise (I am assuming of course you are discussing large projects here).  Also, your 3 statements are just targeted at the developers responsibilities, what about the clients commitment to the project?

My experience is that on large projects the contract is often negotiated between client and developer with little or no technical intervention with the sole aim of winning the contract.  Where technical input is sought it often conflicts with pre-negotiated upper management cost/time projections and therefore ignored.  The seeds of disaster are thus sown.</description>
		<content:encoded><![CDATA[<p>Surely the declaration of a successful project is defined in any software development contract?  I would be very surprised otherwise (I am assuming of course you are discussing large projects here).  Also, your 3 statements are just targeted at the developers responsibilities, what about the clients commitment to the project?</p>
<p>My experience is that on large projects the contract is often negotiated between client and developer with little or no technical intervention with the sole aim of winning the contract.  Where technical input is sought it often conflicts with pre-negotiated upper management cost/time projections and therefore ignored.  The seeds of disaster are thus sown.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Simon</title>
		<link>http://www.pmhut.com/my-theory-on-why-it-projects-fail/comment-page-1#comment-15091</link>
		<dc:creator>Phil Simon</dc:creator>
		<pubDate>Fri, 08 Jan 2010 00:44:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/my-theory-on-why-it-projects-fail#comment-15091</guid>
		<description>Jorge

Good post. I'd agree with all of your reasons but why isn't data quality on there? As I'm sure you know, so many projects are doomed from day one because once organizations get around to trying to test the build of a new system, the data is in such horrible shape that the project is irrevocably harmed.

ps</description>
		<content:encoded><![CDATA[<p>Jorge</p>
<p>Good post. I&#8217;d agree with all of your reasons but why isn&#8217;t data quality on there? As I&#8217;m sure you know, so many projects are doomed from day one because once organizations get around to trying to test the build of a new system, the data is in such horrible shape that the project is irrevocably harmed.</p>
<p>ps</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The CHAOS Report 2009 on IT Project Failure - PM Hut</title>
		<link>http://www.pmhut.com/my-theory-on-why-it-projects-fail/comment-page-1#comment-4026</link>
		<dc:creator>The CHAOS Report 2009 on IT Project Failure - PM Hut</dc:creator>
		<pubDate>Tue, 16 Jun 2009 15:38:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/my-theory-on-why-it-projects-fail#comment-4026</guid>
		<description>[...] stated before that we have to consider the CHAOS Report results in a recent article on my theory on why IT projects fail. But we, PMs, already know that all these measurements work in tandem and need to keep this in [...]</description>
		<content:encoded><![CDATA[<p>[...] stated before that we have to consider the CHAOS Report results in a recent article on my theory on why IT projects fail. But we, PMs, already know that all these measurements work in tandem and need to keep this in [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

