<?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>Agile101 - Agile Project Management and Digital Publishing &#187; Risks and Issues</title>
	<atom:link href="http://agile101.net/category/project-management/agile-risk-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://agile101.net</link>
	<description>Agile Project Management, Programme Management and Digital Publishing</description>
	<lastBuildDate>Thu, 17 Nov 2011 05:58:30 +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>12 Principles of Risk Management (PMBOK &#8211; with an Agile slant)</title>
		<link>http://agile101.net/2009/07/28/12-principles-of-risk-management-pmbok-with-an-agile-slant/</link>
		<comments>http://agile101.net/2009/07/28/12-principles-of-risk-management-pmbok-with-an-agile-slant/#comments</comments>
		<pubDate>Tue, 28 Jul 2009 21:38:59 +0000</pubDate>
		<dc:creator>Tara L Hamilton-Whitaker</dc:creator>
				<category><![CDATA[Risks and Issues]]></category>
		<category><![CDATA[Agile Project Management]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[Software Project Management]]></category>

		<guid isPermaLink="false">http://agile101.net/?p=436</guid>
		<description><![CDATA[The Project Management Body of Knowledge ("PMBOK") describes 12 Principles of Risk Management.  I've taken the headings and summarised the main messages from an Agile perspective...]]></description>
		<wfw:commentRss>http://agile101.net/2009/07/28/12-principles-of-risk-management-pmbok-with-an-agile-slant/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Agile Risk Management &#8211; Identifying Risks (1 of 4)</title>
		<link>http://agile101.net/2009/07/27/agile-risk-management-identifying-risks-step-1-of-4/</link>
		<comments>http://agile101.net/2009/07/27/agile-risk-management-identifying-risks-step-1-of-4/#comments</comments>
		<pubDate>Mon, 27 Jul 2009 11:57:49 +0000</pubDate>
		<dc:creator>Tara L Hamilton-Whitaker</dc:creator>
				<category><![CDATA[Risks and Issues]]></category>
		<category><![CDATA[Agile Project Management]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[Software Project Management]]></category>

		<guid isPermaLink="false">http://agile101.net/?p=467</guid>
		<description><![CDATA[Risk identification is the first stage in the Agile Risk Management process. This stage is followed by Risk Assessment, Risk Response and Risk Review.]]></description>
		<wfw:commentRss>http://agile101.net/2009/07/27/agile-risk-management-identifying-risks-step-1-of-4/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Agile Risk Management &#8211; Assessing Risks (2 of 4)</title>
		<link>http://agile101.net/2009/07/27/agile-risk-management-assessing-risks-step-2-of-4/</link>
		<comments>http://agile101.net/2009/07/27/agile-risk-management-assessing-risks-step-2-of-4/#comments</comments>
		<pubDate>Mon, 27 Jul 2009 11:56:40 +0000</pubDate>
		<dc:creator>Tara L Hamilton-Whitaker</dc:creator>
				<category><![CDATA[Risks and Issues]]></category>
		<category><![CDATA[Agile Project Management]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[Software Project Management]]></category>

		<guid isPermaLink="false">http://agile101.net/?p=470</guid>
		<description><![CDATA[Risk Assessment is the second stage in the Agile Risk Management process. This stage is preceeded by Risk Identification, and followed by Risk Response and Risk Review.]]></description>
		<wfw:commentRss>http://agile101.net/2009/07/27/agile-risk-management-assessing-risks-step-2-of-4/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Agile Risk Management &#8211; Risk Response (3 of 4)</title>
		<link>http://agile101.net/2009/07/27/agile-risk-management-risk-response-step-3-of-4/</link>
		<comments>http://agile101.net/2009/07/27/agile-risk-management-risk-response-step-3-of-4/#comments</comments>
		<pubDate>Mon, 27 Jul 2009 11:54:37 +0000</pubDate>
		<dc:creator>Tara L Hamilton-Whitaker</dc:creator>
				<category><![CDATA[Risks and Issues]]></category>
		<category><![CDATA[Agile Project Management]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[Software Project Management]]></category>

		<guid isPermaLink="false">http://agile101.net/?p=472</guid>
		<description><![CDATA[Risk Response is the third stage in the Agile Risk Management process. This stage is preceeded by Risk Identification and Risk Assessment and followed by Risk Review.]]></description>
		<wfw:commentRss>http://agile101.net/2009/07/27/agile-risk-management-risk-response-step-3-of-4/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Agile Risk Management &#8211; Risk Review (4 of 4)</title>
		<link>http://agile101.net/2009/07/27/agile-risk-management-risk-review-step-4-of-4/</link>
		<comments>http://agile101.net/2009/07/27/agile-risk-management-risk-review-step-4-of-4/#comments</comments>
		<pubDate>Mon, 27 Jul 2009 11:53:48 +0000</pubDate>
		<dc:creator>Tara L Hamilton-Whitaker</dc:creator>
				<category><![CDATA[Risks and Issues]]></category>
		<category><![CDATA[Agile Project Management]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[Software Project Management]]></category>

		<guid isPermaLink="false">http://agile101.net/?p=474</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://agile101.net/2009/07/27/agile-risk-management-risk-review-step-4-of-4/";</script>var dzone_style="2";Risk Review is the final stage in the Agile Risk Management process. This stage is preceeded by Risk Identification,&#160;Risk Assessment and Risk Response. A Risk is an uncertain event that will impact your chosen path should it be realised. Risks are events that are not currently affecting you – they haven’t happened yet.&#160; Once [...]]]></description>
		<wfw:commentRss>http://agile101.net/2009/07/27/agile-risk-management-risk-review-step-4-of-4/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Agile Risk Management for Projects and Programmes</title>
		<link>http://agile101.net/2009/07/27/agile-risk-management-for-projects-and-programmes/</link>
		<comments>http://agile101.net/2009/07/27/agile-risk-management-for-projects-and-programmes/#comments</comments>
		<pubDate>Mon, 27 Jul 2009 00:38:43 +0000</pubDate>
		<dc:creator>Tara L Hamilton-Whitaker</dc:creator>
				<category><![CDATA[!]]></category>
		<category><![CDATA[Risks and Issues]]></category>
		<category><![CDATA[Agile Software Development]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[Software Project Management]]></category>

		<guid isPermaLink="false">http://agile101.net/?p=429</guid>
		<description><![CDATA[Risks are traditionally identified, assessed, responded to and monitored by a Project Manager. In Agile working environments the responsibility for risk management is shared by all involved. There don’t seem to be any official guidelines on how to manage risks within an Agile environment, so I’ll combine my personal views/learning with notes/ideas I’ve found scattered around the web.]]></description>
		<wfw:commentRss>http://agile101.net/2009/07/27/agile-risk-management-for-projects-and-programmes/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Agile Risk Management &#8211; The difference between Risks and Issues</title>
		<link>http://agile101.net/2009/07/26/agile-risk-management-the-difference-between-risks-and-issues/</link>
		<comments>http://agile101.net/2009/07/26/agile-risk-management-the-difference-between-risks-and-issues/#comments</comments>
		<pubDate>Sun, 26 Jul 2009 21:58:10 +0000</pubDate>
		<dc:creator>Tara L Hamilton-Whitaker</dc:creator>
				<category><![CDATA[!]]></category>
		<category><![CDATA[Risks and Issues]]></category>
		<category><![CDATA[Agile Project Management]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[Software Project Management]]></category>

		<guid isPermaLink="false">http://agile101.net/?p=426</guid>
		<description><![CDATA[A Risk is an uncertain event that could impact your chosen path should it be realised. Risks are events that are not currently affecting you - they haven't happened yet.  Once a risk is realised, it has the potential to become an Issue.]]></description>
		<wfw:commentRss>http://agile101.net/2009/07/26/agile-risk-management-the-difference-between-risks-and-issues/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Agile Issue Management for Projects and Programmes</title>
		<link>http://agile101.net/2009/07/26/agile-issue-management-for-projects-and-programmes/</link>
		<comments>http://agile101.net/2009/07/26/agile-issue-management-for-projects-and-programmes/#comments</comments>
		<pubDate>Sun, 26 Jul 2009 01:34:15 +0000</pubDate>
		<dc:creator>Tara L Hamilton-Whitaker</dc:creator>
				<category><![CDATA[!]]></category>
		<category><![CDATA[Risks and Issues]]></category>
		<category><![CDATA[Agile Issue Management]]></category>
		<category><![CDATA[Agile Project Management]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Software Project Management]]></category>

		<guid isPermaLink="false">http://agile101.net/?p=406</guid>
		<description><![CDATA[Scrum is great at handling immediate issues or in this case, they're more commonly referred to as 'Impediments'... ]]></description>
		<wfw:commentRss>http://agile101.net/2009/07/26/agile-issue-management-for-projects-and-programmes/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Minimising the impact of Sprint disruptions</title>
		<link>http://agile101.net/2009/07/10/minimising-the-impact-of-sprint-disruptions/</link>
		<comments>http://agile101.net/2009/07/10/minimising-the-impact-of-sprint-disruptions/#comments</comments>
		<pubDate>Fri, 10 Jul 2009 18:52:48 +0000</pubDate>
		<dc:creator>Tara L Hamilton-Whitaker</dc:creator>
				<category><![CDATA[Risks and Issues]]></category>
		<category><![CDATA[Agile Project Management]]></category>
		<category><![CDATA[Lean Six Sigma]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Software Project Management]]></category>
		<category><![CDATA[Sprint Planning]]></category>

		<guid isPermaLink="false">http://agile101.wordpress.com/?p=111</guid>
		<description><![CDATA[One of the biggest challenges we've faced is trying to balance project work or product development with business-as-usual (BAU) work that can't necessarily be anticipated - how do you manage the risk of disruption?]]></description>
		<wfw:commentRss>http://agile101.net/2009/07/10/minimising-the-impact-of-sprint-disruptions/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Managing Scrum projects alongside BAU</title>
		<link>http://agile101.net/2009/07/08/managing-scrum-projects-alongside-bau/</link>
		<comments>http://agile101.net/2009/07/08/managing-scrum-projects-alongside-bau/#comments</comments>
		<pubDate>Wed, 08 Jul 2009 16:34:06 +0000</pubDate>
		<dc:creator>taraleewhitaker</dc:creator>
				<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Risks and Issues]]></category>
		<category><![CDATA[Lean]]></category>
		<category><![CDATA[Scrum]]></category>

		<guid isPermaLink="false">http://agile101.wordpress.com/?p=32</guid>
		<description><![CDATA[The most practical application of Scrum (i.e. the easiest to manage!) exists at the interface between those that own individual products and those that deliver the incremental enhancements to those products.  In a multi-purpose team environment (i.e. where the team delivering your predictable roadmap is also the team required to address live defects - BAU), it becomes more challenging to commit to a sprint of work (without interruption) because you can't just leave a critical live defect... live ...]]></description>
		<wfw:commentRss>http://agile101.net/2009/07/08/managing-scrum-projects-alongside-bau/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

