<?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: The Missing Dimension in Project Qualitative Risk Analysis</title>
	<atom:link href="http://blog.johnestrella.com/2009/04/the-missing-dimension-in-project-qualitative-risk-analysis/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.johnestrella.com/2009/04/the-missing-dimension-in-project-qualitative-risk-analysis/</link>
	<description>Project Management &#124; Business Analysis &#124; Software Testing</description>
	<pubDate>Sat, 19 May 2012 16:07:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John Estrella</title>
		<link>http://blog.johnestrella.com/2009/04/the-missing-dimension-in-project-qualitative-risk-analysis/comment-page-1/#comment-97</link>
		<dc:creator>John Estrella</dc:creator>
		<pubDate>Wed, 29 Apr 2009 22:02:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.johnestrella.com/?p=199#comment-97</guid>
		<description>Curt, I somewhat agree with you. If you have a list of 25 or so risks, a simple risk register may do the trick. However, for larger projects, it is usually good to prioritize the risks so that you can plan your risk responses accordingly. Otherwise, you may end up spending effort on risks that are not really that important.</description>
		<content:encoded><![CDATA[<p>Curt, I somewhat agree with you. If you have a list of 25 or so risks, a simple risk register may do the trick. However, for larger projects, it is usually good to prioritize the risks so that you can plan your risk responses accordingly. Otherwise, you may end up spending effort on risks that are not really that important.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curt Finch</title>
		<link>http://blog.johnestrella.com/2009/04/the-missing-dimension-in-project-qualitative-risk-analysis/comment-page-1/#comment-96</link>
		<dc:creator>Curt Finch</dc:creator>
		<pubDate>Wed, 29 Apr 2009 21:27:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.johnestrella.com/?p=199#comment-96</guid>
		<description>I think for many projects PMI descriptions of standard risk analysis are kind of overblown.  I'm talking about rolling out a software package here more than building the golden gate bridge.  In many cases a quick and dirty list of forseeable risks with simple mitigation strategies is all you really need.</description>
		<content:encoded><![CDATA[<p>I think for many projects PMI descriptions of standard risk analysis are kind of overblown.  I&#8217;m talking about rolling out a software package here more than building the golden gate bridge.  In many cases a quick and dirty list of forseeable risks with simple mitigation strategies is all you really need.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

