<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Project Failure Analysis Patterns (Part 2)</title>
	<link>http://www.managementbits.com/2008/01/07/project-failure-analysis-patterns-part-2/</link>
	<description>Reflections on Software Engineering and Software Technical Support Management</description>
	<pubDate>Thu, 09 Sep 2010 08:07:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Dmitry Vostokov</title>
		<link>http://www.managementbits.com/2008/01/07/project-failure-analysis-patterns-part-2/#comment-8</link>
		<dc:creator>Dmitry Vostokov</dc:creator>
		<pubDate>Tue, 08 Jan 2008 14:27:15 +0000</pubDate>
		<guid>http://www.managementbits.com/2008/01/07/project-failure-analysis-patterns-part-2/#comment-8</guid>
		<description>Incremental and iterative processes coupled with appropriate tools mitigate risks of artifact corruption if documentation is updated with each project iteration</description>
		<content:encoded><![CDATA[<p>Incremental and iterative processes coupled with appropriate tools mitigate risks of artifact corruption if documentation is updated with each project iteration</p>
]]></content:encoded>
	</item>
</channel>
</rss>
