<?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; Metrics</title>
	<atom:link href="http://neverletdown.net/topics/metrics/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>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 sense? I see several problems with thinking about risk in this way. Numbers [...]]]></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>Project Signaling</title>
		<link>http://neverletdown.net/2009/09/project-signaling/</link>
		<comments>http://neverletdown.net/2009/09/project-signaling/#comments</comments>
		<pubDate>Wed, 16 Sep 2009 02:38:49 +0000</pubDate>
		<dc:creator>Michael Keeling</dc:creator>
				<category><![CDATA[Metrics]]></category>
		<category><![CDATA[binary metric]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[signal]]></category>
		<category><![CDATA[software engineering]]></category>
		<category><![CDATA[trigger]]></category>
		<category><![CDATA[tripwire]]></category>
		<category><![CDATA[Van Halen]]></category>

		<guid isPermaLink="false">http://neverletdown.net/?p=90</guid>
		<description><![CDATA[Van Halen may have known more about project management than most program managers. Van Halen’s legendary "No Brown M&#38;Ms Rider" is simultaneously the greatest example of rock star excess and project signaling I’ve ever seen. As David Lee Rot]]></description>
			<content:encoded><![CDATA[Van Halen may have known more about project management than most program managers.  Van Halen’s legendary "No Brown M&amp;Ms Rider" is simultaneously the greatest example of rock star excess and project signaling I’ve ever seen.  As David Lee Rot]]></content:encoded>
			<wfw:commentRss>http://neverletdown.net/2009/09/project-signaling/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Binary is a Metric Too</title>
		<link>http://neverletdown.net/2009/09/binary-is-a-metric-too/</link>
		<comments>http://neverletdown.net/2009/09/binary-is-a-metric-too/#comments</comments>
		<pubDate>Tue, 01 Sep 2009 21:07:51 +0000</pubDate>
		<dc:creator>Michael Keeling</dc:creator>
				<category><![CDATA[Engineering]]></category>
		<category><![CDATA[Metrics]]></category>
		<category><![CDATA[anlaysis]]></category>
		<category><![CDATA[control]]></category>
		<category><![CDATA[data]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[measurement]]></category>
		<category><![CDATA[measures]]></category>
		<category><![CDATA[software engineering]]></category>
		<category><![CDATA[Tom DeMarco]]></category>

		<guid isPermaLink="false">http://neverletdown.net/?p=76</guid>
		<description><![CDATA[Software developers are, in their heart of hearts, dataphiles - people who are absolutely in love with data. When was the last time you had a passionate discussion about frame rates, hardware benchmarks, gadget specs, sports statistics, dungeons and]]></description>
			<content:encoded><![CDATA[Software developers are, in their heart of hearts, dataphiles - people who are absolutely in love with data.  When was the last time you had a passionate discussion about frame rates, hardware benchmarks, gadget specs, sports statistics, dungeons and]]></content:encoded>
			<wfw:commentRss>http://neverletdown.net/2009/09/binary-is-a-metric-too/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

