<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>LOG.ae &#187; Vicki Wrona</title>
	<atom:link href="http://log.ae/author/vicki/feed/" rel="self" type="application/rss+xml" />
	<link>http://log.ae</link>
	<description>Delivering Quality Logistics Information Since 1947</description>
	<lastBuildDate>Wed, 05 Oct 2011 14:44:18 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>The Risk Management Process</title>
		<link>http://log.ae/2008/05/01/the-risk-management-process/</link>
		<comments>http://log.ae/2008/05/01/the-risk-management-process/#comments</comments>
		<pubDate>Thu, 01 May 2008 07:29:03 +0000</pubDate>
		<dc:creator>Vicki Wrona</dc:creator>
				<category><![CDATA[Guest Column]]></category>
		<category><![CDATA[Issue 7 May 2008]]></category>

		<guid isPermaLink="false">http://log.ae/2008/05/08/the-risk-management-process/</guid>
		<description><![CDATA[Some experts have said that a strong risk management process can decrease problems on a project by as much as 80 or 90 per cent. In combination with solid project management practices &#8212; having a well-defined scope, incorporating input from the appropriate stakeholders, following a good change management process, and keeping open the lines of [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Flog.ae%2F2008%2F05%2F01%2Fthe-risk-management-process%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Flog.ae%2F2008%2F05%2F01%2Fthe-risk-management-process%2F&amp;source=Log_MiddleEast&amp;style=normal" height="61" width="50" /><br />
			</a>
		</div>
<p>Some experts have said that a strong risk management process can decrease problems on a project by as much as 80 or 90 per cent. In combination with solid project management practices &#8212; having a well-defined scope, incorporating input from the appropriate stakeholders, following a good change</p>
<p><span id="more-109"></span><br />
management process, and keeping open the lines of communication &#8212; a good risk management process is critical in cutting down on surprises, or unexpected project risks.
</p>
<p><strong><em>Step one </em></strong>of the risk management process is to have each person involved in the planning process individually list at least 10 potential risk items. Often with this step, team members will assume that certain project risks are already known, and therefore do not need to be listed.</p>
<p><strong><em>Step two </em></strong>of the risk management process is to collect the lists of project risks and compile them into a single list with the duplicates removed.</p>
<p><strong><em>Step three </em></strong>of the risk management process is to assess the probability (or likelihood), the impact (or consequence) and the detectability of each item on the master list. This can be</p>
<p>done by assigning to each item on the list a numerical rating such as on a scale of 1 to 4 or a subjective term such as high, medium, or low.</p>
<p><strong><em>Step four </em></strong>of the risk management process is to break the planning team into subgroups and to give a portion of the master list to each subgroup. Each subgroup can then identify the triggers (warning signs) for its assigned list of project risks. All triggers should be noted, even minor ones. Normally there will be at least three triggers for each risk.</p>
<p><strong><em>Step five </em></strong>of the risk management process is for those same subgroups to identify possible preventive actions for the threats and enhancement actions for the opportunities.</p>
<p><strong><em>Step six </em></strong>of the risk management process is for the subgroups to then create a contingency plan for most but not all project risks &#8211; a plan that includes the actions one would take if a trigger or a risk were to occur. This plan will be created for those risks scoring above a certain cut-off point, which is determined after looking at the total scores for all risks.</p>
<p><strong><em>Step seven</em></strong>, the final step in planning the risk management process, is to determine the owner of each risk on the list. The owner is the person who is responsible for watching out for triggers and then for responding appropriately if the triggers do in fact occur by implementing the pre-approved and now established contingency plan.    <br />Rather than start this risk management process from scratch for every new project, it can be followed once to establish a list of generic project risks and triggers, skipping step three. Then, a team simply has to add project-specific risks and triggers and assess the probability, impact, and detectability for each risk, saving a great amount of time and helping to ingrain a risk mentality into your project culture.</p>
<p><em>By Viki Wrona     <br />President, Forward Momentum, LLC, a consulting and training company, and an instructor with Westlake Training and Development</em></p>
]]></content:encoded>
			<wfw:commentRss>http://log.ae/2008/05/01/the-risk-management-process/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

