<?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: Agile Risk Management</title>
	<atom:link href="http://www.pmhut.com/agile-risk-management/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/agile-risk-management</link>
	<description></description>
	<pubDate>Sat, 11 Feb 2012 04:07:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Patrick Weaver</title>
		<link>http://www.pmhut.com/agile-risk-management/comment-page-1#comment-881</link>
		<dc:creator>Patrick Weaver</dc:creator>
		<pubDate>Sat, 07 Mar 2009 23:01:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/agile-risk-management#comment-881</guid>
		<description>Your view the PMBOK risk management processes don’t include the treatment of risk could not be more wrong!  What the PMBOK dose not assume is a bunch of people sitting a meeting doing ‘risk management’ can change the project.

The outputs from ‘Plan Risk Responses’ (PMBOK® Guide 4th Edition) are updates to the project procurement process to deal with any contract related changes to manage risk and updates to virtually every section of the project management plan to change the future shape of the project to minimise threats and maximise opportunities.

Having a bright idea in a risk management meeting to do something is of absolutely no value unless the idea is translated in to action via the project plans and become budget line items and schedule tasks for people to perform.

Similarly your view that PMBOK risk management is a ‘one off’ is completely wrong. Risk management is an iterative process in the PMBOK as much as in your Agile scenario above.</description>
		<content:encoded><![CDATA[<p>Your view the PMBOK risk management processes don’t include the treatment of risk could not be more wrong!  What the PMBOK dose not assume is a bunch of people sitting a meeting doing ‘risk management’ can change the project.</p>
<p>The outputs from ‘Plan Risk Responses’ (PMBOK® Guide 4th Edition) are updates to the project procurement process to deal with any contract related changes to manage risk and updates to virtually every section of the project management plan to change the future shape of the project to minimise threats and maximise opportunities.</p>
<p>Having a bright idea in a risk management meeting to do something is of absolutely no value unless the idea is translated in to action via the project plans and become budget line items and schedule tasks for people to perform.</p>
<p>Similarly your view that PMBOK risk management is a ‘one off’ is completely wrong. Risk management is an iterative process in the PMBOK as much as in your Agile scenario above.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

