<?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: Why Manage Risks Formally?</title>
	<atom:link href="http://www.pmhut.com/why-manage-risks-formally/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/why-manage-risks-formally</link>
	<description></description>
	<pubDate>Fri, 25 May 2012 03:54:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Glen B. Alleman</title>
		<link>http://www.pmhut.com/why-manage-risks-formally/comment-page-1#comment-705</link>
		<dc:creator>Glen B. Alleman</dc:creator>
		<pubDate>Wed, 09 Jul 2008 14:35:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/why-manage-risks-formally#comment-705</guid>
		<description>Karl,
The tradeoff between "managing" the risk and not manageing the risk - from a cost perspective needs some clarification. Not spending money is the risk management choice of "ignore." The trade space for that decision is actually in the risk management guidelines. While it may be zero cost in terms of mitigation or retirement, the conseqential cost is not zero - as you state.
I'd suggest the first example of subcontractor deliveries is easily mitigated with fine controlled deliverables management rather than multiple vendors - which woudl increase the risk, since managing each is now required, along with confusion in requirements and inconsistent deliverables.
One approach built into the schedule is to include the "plan b" impacts at the point of occurance. As well retirement work can be inline as well.
Including active risk management as part of project management is the current paradigm for projects with any substantial risk elements. "What you can't see won't hurt you" is not a strategy for success.

Glen B. Alleman
VP, Program Planning and Controls
Defense and Space
Lewis &amp; Fowler, Denver Colorado</description>
		<content:encoded><![CDATA[<p>Karl,<br />
The tradeoff between &#8220;managing&#8221; the risk and not manageing the risk - from a cost perspective needs some clarification. Not spending money is the risk management choice of &#8220;ignore.&#8221; The trade space for that decision is actually in the risk management guidelines. While it may be zero cost in terms of mitigation or retirement, the conseqential cost is not zero - as you state.<br />
I&#8217;d suggest the first example of subcontractor deliveries is easily mitigated with fine controlled deliverables management rather than multiple vendors - which woudl increase the risk, since managing each is now required, along with confusion in requirements and inconsistent deliverables.<br />
One approach built into the schedule is to include the &#8220;plan b&#8221; impacts at the point of occurance. As well retirement work can be inline as well.<br />
Including active risk management as part of project management is the current paradigm for projects with any substantial risk elements. &#8220;What you can&#8217;t see won&#8217;t hurt you&#8221; is not a strategy for success.</p>
<p>Glen B. Alleman<br />
VP, Program Planning and Controls<br />
Defense and Space<br />
Lewis &amp; Fowler, Denver Colorado</p>
]]></content:encoded>
	</item>
</channel>
</rss>

