<?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: Earning up: Agile &#8216;burn ups&#8217; in an economic turndown</title>
	<atom:link href="http://alterlabs.com/general/articles/earning-up-agile-burn-ups-in-an-economic-turndown/feed/" rel="self" type="application/rss+xml" />
	<link>http://alterlabs.com/general/articles/earning-up-agile-burn-ups-in-an-economic-turndown/</link>
	<description>Results through imagination</description>
	<lastBuildDate>Mon, 15 Mar 2010 02:56:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Alistair Cockburn</title>
		<link>http://alterlabs.com/general/articles/earning-up-agile-burn-ups-in-an-economic-turndown/comment-page-1/#comment-28117</link>
		<dc:creator>Alistair Cockburn</dc:creator>
		<pubDate>Sat, 16 May 2009 15:42:29 +0000</pubDate>
		<guid isPermaLink="false">http://alterlabs.com/uncategorized/earning-up-agile-burn-ups-in-an-economic-turndown/#comment-28117</guid>
		<description>Nice article. The hard question is, &quot;how do we find that business value?&quot; Usual agile features and stories are too fine-grained for most people to attach $ value to.  In &quot;Software by Numbers&quot;, Mark Denne and Jane Cleland-Huang introduce the term &quot;minimum marketable feature&quot; as something coarse-grained enough to do that with. I still haven&#039;t seen someone pull this off in real life. 

Little historical note... It&#039;s quite possible that burn charts did indeed arise from &quot;the peyote induced hallucinations of a band of innovative Project Management and Architecture shamans&quot; (lovely image :)... I, for example, never heard of EVM until I&#039;d been using burn charts for 5 years. Then, when I finally arose from my peyote-induced stupor and was shown one of these things, recognized it was the same thing. I have no idea whether or when the Scrum inventors first saw EVM. However, I&#039;m always looking for bridges to make it easier for people who already know something to apply that in the peyote universe (as opposed to people who try to maximize the difference), so I try to maximize the overlap between them in descriptions. 

Again, nice job - please post or email me if/when you can show an anonymized but real-project version. 

Alistair</description>
		<content:encoded><![CDATA[<p>Nice article. The hard question is, &#8220;how do we find that business value?&#8221; Usual agile features and stories are too fine-grained for most people to attach $ value to.  In &#8220;Software by Numbers&#8221;, Mark Denne and Jane Cleland-Huang introduce the term &#8220;minimum marketable feature&#8221; as something coarse-grained enough to do that with. I still haven&#8217;t seen someone pull this off in real life. </p>
<p>Little historical note&#8230; It&#8217;s quite possible that burn charts did indeed arise from &#8220;the peyote induced hallucinations of a band of innovative Project Management and Architecture shamans&#8221; (lovely image :)&#8230; I, for example, never heard of EVM until I&#8217;d been using burn charts for 5 years. Then, when I finally arose from my peyote-induced stupor and was shown one of these things, recognized it was the same thing. I have no idea whether or when the Scrum inventors first saw EVM. However, I&#8217;m always looking for bridges to make it easier for people who already know something to apply that in the peyote universe (as opposed to people who try to maximize the difference), so I try to maximize the overlap between them in descriptions. </p>
<p>Again, nice job &#8211; please post or email me if/when you can show an anonymized but real-project version. </p>
<p>Alistair</p>
]]></content:encoded>
	</item>
</channel>
</rss>
