<?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 Importance of the Risk Log</title>
	<atom:link href="http://www.pmhut.com/the-importance-of-the-risk-log/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/the-importance-of-the-risk-log</link>
	<description></description>
	<pubDate>Sat, 11 Feb 2012 16:30:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Laura Bamberg</title>
		<link>http://www.pmhut.com/the-importance-of-the-risk-log/comment-page-1#comment-18856</link>
		<dc:creator>Laura Bamberg</dc:creator>
		<pubDate>Mon, 15 Mar 2010 14:28:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4971#comment-18856</guid>
		<description>Olga is dead-on. It's great that a PM spends the time to come up w/ the risks - but that's a waste of time if you don't actually deal w/ them! Put them in your plan. Schedule them!</description>
		<content:encoded><![CDATA[<p>Olga is dead-on. It&#8217;s great that a PM spends the time to come up w/ the risks - but that&#8217;s a waste of time if you don&#8217;t actually deal w/ them! Put them in your plan. Schedule them!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Olga Sa</title>
		<link>http://www.pmhut.com/the-importance-of-the-risk-log/comment-page-1#comment-18769</link>
		<dc:creator>Olga Sa</dc:creator>
		<pubDate>Sun, 14 Mar 2010 03:55:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4971#comment-18769</guid>
		<description>Thank you Kerry for bringing up this subject! I am myself trying to work out the ideal framework when it comes to risk management. I have also discussed this topic with my mentor and he shared with me the process that is in place at his company, which is a risk-averse.

The risk management there starts with the brainstorming from the whole team; everyone is invited to contribute to the list of possible risks. The risks are put on sticky notes and also assigned the probability and impact. For those risks with high impact and high probability, the team tries to come up with a solution to move it down on the impact/probability graph. That’s all just prep work, however, but the biggest challenge is to actually keep these risks in mind.

I found that both PMI and my mentor suggest to actually put the mitigating strategy into the project plan. That helps to keep risks visible as you mentioned yourself that you always keep an eye on the plan and upcoming tasks. Ideally the rest of the risk log should also be reviewed periodically and included in the status updates. Of course sometimes there are risks that we did not foresee; those become lessons learned.

In an ideal feedback loop, lessons learned also serve as a base for the risk  brainstorming session of future projects.

I would be interested to hear how others deal with risk management on their projects.</description>
		<content:encoded><![CDATA[<p>Thank you Kerry for bringing up this subject! I am myself trying to work out the ideal framework when it comes to risk management. I have also discussed this topic with my mentor and he shared with me the process that is in place at his company, which is a risk-averse.</p>
<p>The risk management there starts with the brainstorming from the whole team; everyone is invited to contribute to the list of possible risks. The risks are put on sticky notes and also assigned the probability and impact. For those risks with high impact and high probability, the team tries to come up with a solution to move it down on the impact/probability graph. That’s all just prep work, however, but the biggest challenge is to actually keep these risks in mind.</p>
<p>I found that both PMI and my mentor suggest to actually put the mitigating strategy into the project plan. That helps to keep risks visible as you mentioned yourself that you always keep an eye on the plan and upcoming tasks. Ideally the rest of the risk log should also be reviewed periodically and included in the status updates. Of course sometimes there are risks that we did not foresee; those become lessons learned.</p>
<p>In an ideal feedback loop, lessons learned also serve as a base for the risk  brainstorming session of future projects.</p>
<p>I would be interested to hear how others deal with risk management on their projects.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

