<?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>Reflections on Software Engineering &#187; Risk Management</title>
	<atom:link href="http://neverletdown.net/topics/risk-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://neverletdown.net</link>
	<description>by Michael Keeling</description>
	<lastBuildDate>Wed, 14 Sep 2011 02:23:54 +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>Choosing a Software Design Strategy</title>
		<link>http://neverletdown.net/2010/08/choosing-a-software-design-strategy/</link>
		<comments>http://neverletdown.net/2010/08/choosing-a-software-design-strategy/#comments</comments>
		<pubDate>Mon, 02 Aug 2010 22:01:36 +0000</pubDate>
		<dc:creator>Michael Keeling</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[ACDM]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[emergent design]]></category>
		<category><![CDATA[science of the artificial]]></category>
		<category><![CDATA[software design]]></category>
		<category><![CDATA[software engineering]]></category>

		<guid isPermaLink="false">http://neverletdown.net/?p=384</guid>
		<description><![CDATA[I was reading an article from the Joel on Software archives and was struck by this quote from The Project Aardvark Spec: I can&#8217;t tell you how strongly I believe in Big Design Up Front, which the proponents of Extreme Programming consider anathema. I have consistently saved time and made better products by using BDUF [...]]]></description>
			<content:encoded><![CDATA[I was reading an article from the Joel on Software archives and was struck by this quote from The Project Aardvark Spec:
I can't tell you how strongly I believe in Big Design Up Front, which the proponents of Extreme Programming consider anathema. I]]></content:encoded>
			<wfw:commentRss>http://neverletdown.net/2010/08/choosing-a-software-design-strategy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Reality of Risk Exposure</title>
		<link>http://neverletdown.net/2010/05/the-reality-of-risk-exposure/</link>
		<comments>http://neverletdown.net/2010/05/the-reality-of-risk-exposure/#comments</comments>
		<pubDate>Sun, 16 May 2010 02:31:24 +0000</pubDate>
		<dc:creator>Michael Keeling</dc:creator>
				<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[analysis]]></category>
		<category><![CDATA[impact]]></category>
		<category><![CDATA[Metrics]]></category>
		<category><![CDATA[probability]]></category>
		<category><![CDATA[Small team Risk Evaluation workshop]]></category>
		<category><![CDATA[software engineering]]></category>
		<category><![CDATA[SRE]]></category>
		<category><![CDATA[studio]]></category>

		<guid isPermaLink="false">http://neverletdown.net/?p=295</guid>
		<description><![CDATA[Over the past few weeks I’ve been thinking a lot about risk exposure in the context of managing projects. Exposure is a technique used almost universally when managing risks, yet as I’ve already discussed, exposure can cause major problems becau]]></description>
			<content:encoded><![CDATA[Over the past few weeks I’ve been thinking a lot about risk exposure in the context of managing projects.  Exposure is a technique used almost universally when managing risks, yet as I’ve already discussed, exposure can cause major problems becau]]></content:encoded>
			<wfw:commentRss>http://neverletdown.net/2010/05/the-reality-of-risk-exposure/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Closer Look at Risk Burndown</title>
		<link>http://neverletdown.net/2010/05/a-closer-look-at-risk-burndown/</link>
		<comments>http://neverletdown.net/2010/05/a-closer-look-at-risk-burndown/#comments</comments>
		<pubDate>Sun, 02 May 2010 02:17:34 +0000</pubDate>
		<dc:creator>Michael Keeling</dc:creator>
				<category><![CDATA[Metrics]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[burndown]]></category>
		<category><![CDATA[measurement]]></category>
		<category><![CDATA[measures]]></category>
		<category><![CDATA[software engineering]]></category>
		<category><![CDATA[tracking]]></category>

		<guid isPermaLink="false">http://neverletdown.net/?p=265</guid>
		<description><![CDATA[I like the idea of the risk burndown chart. Burndown is an effective and satisfying visual indicator of progress and it’s relatively easy to calculate to boot. But does looking at a project’s risks through the lens of a burndown chart make sens]]></description>
			<content:encoded><![CDATA[I like the idea of the risk burndown chart.  Burndown is an effective and satisfying visual indicator of progress and it’s relatively easy to calculate to boot.  But does looking at a project’s risks through the lens of a burndown chart make sens]]></content:encoded>
			<wfw:commentRss>http://neverletdown.net/2010/05/a-closer-look-at-risk-burndown/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SWOT vs. Risk Management</title>
		<link>http://neverletdown.net/2010/02/swot-vs-risk-management/</link>
		<comments>http://neverletdown.net/2010/02/swot-vs-risk-management/#comments</comments>
		<pubDate>Tue, 16 Feb 2010 04:43:34 +0000</pubDate>
		<dc:creator>Michael Keeling</dc:creator>
				<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[planning]]></category>
		<category><![CDATA[software engineering]]></category>
		<category><![CDATA[swot]]></category>
		<category><![CDATA[team building]]></category>
		<category><![CDATA[threshold of success]]></category>

		<guid isPermaLink="false">http://neverletdown.net/?p=174</guid>
		<description><![CDATA[I was recently asked by a coworker how software risk management is different from traditional SWOT analysis. SWOT is a technique commonly used for strategic planning where the strengths, weaknesses, opportunities, and threats facing a group are comp]]></description>
			<content:encoded><![CDATA[I was recently asked by a coworker how software risk management is different from traditional SWOT analysis.  SWOT is a technique commonly used for strategic planning where the strengths, weaknesses, opportunities, and threats facing a group are comp]]></content:encoded>
			<wfw:commentRss>http://neverletdown.net/2010/02/swot-vs-risk-management/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Threshold of Success</title>
		<link>http://neverletdown.net/2010/01/threshold-of-success/</link>
		<comments>http://neverletdown.net/2010/01/threshold-of-success/#comments</comments>
		<pubDate>Sat, 16 Jan 2010 04:06:21 +0000</pubDate>
		<dc:creator>Michael Keeling</dc:creator>
				<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[goals]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[planning]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[software engineering]]></category>

		<guid isPermaLink="false">http://neverletdown.net/?p=153</guid>
		<description><![CDATA[When I was a kid my brother and I used to play a game called Make Believe. My favorite variant of the game was simple. Together we would build some kind of fortress and then one person gets the fort and the other person tries to invade the fort. I]]></description>
			<content:encoded><![CDATA[When I was a kid my brother and I used to play a game called Make Believe.  My favorite variant of the game was simple.  Together we would build some kind of fortress and then one person gets the fort and the other person tries to invade the fort.  I]]></content:encoded>
			<wfw:commentRss>http://neverletdown.net/2010/01/threshold-of-success/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

