<?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: Decoding the DNA of Failed Technology Projects - Conclusion</title>
	<atom:link href="http://www.pmhut.com/decoding-the-dna-of-failed-technology-projects-conclusion/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/decoding-the-dna-of-failed-technology-projects-conclusion</link>
	<description></description>
	<pubDate>Sun, 12 Feb 2012 04:31:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mike Greer</title>
		<link>http://www.pmhut.com/decoding-the-dna-of-failed-technology-projects-conclusion/comment-page-1#comment-1142</link>
		<dc:creator>Mike Greer</dc:creator>
		<pubDate>Thu, 26 Feb 2009 17:55:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/decoding-the-dna-of-failed-technology-projects-conclusion#comment-1142</guid>
		<description>Nice article! I particularly like this: "The urgent need in many organizations lies in going beyond that basic level of knowledge and developing the more advanced insights to be able to see the symptoms of project failure and the strategies for securing success."

One of the tough things about developing these insights is that the most meaningful ones are home-grown, rising out of unique circumstances in the organization's market or culture. Developing these home-grown insights requires some rear-view introspection... figuring out what went wrong and what needs to be changed on future projects. That's why project Post Mortem project analyses, followed by distributing a set of Lessons Learned are so important.

I've got a freebie set (several pages) of Post Mortem questions that you can use to jump start this process in your organization. It's at:
http://www.michaelgreer.com/postmortem.htm</description>
		<content:encoded><![CDATA[<p>Nice article! I particularly like this: &#8220;The urgent need in many organizations lies in going beyond that basic level of knowledge and developing the more advanced insights to be able to see the symptoms of project failure and the strategies for securing success.&#8221;</p>
<p>One of the tough things about developing these insights is that the most meaningful ones are home-grown, rising out of unique circumstances in the organization&#8217;s market or culture. Developing these home-grown insights requires some rear-view introspection&#8230; figuring out what went wrong and what needs to be changed on future projects. That&#8217;s why project Post Mortem project analyses, followed by distributing a set of Lessons Learned are so important.</p>
<p>I&#8217;ve got a freebie set (several pages) of Post Mortem questions that you can use to jump start this process in your organization. It&#8217;s at:<br />
<a href="http://www.michaelgreer.com/postmortem.htm" rel="nofollow">http://www.michaelgreer.com/postmortem.htm</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

