<?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: Are You Measuring What&#8217;s Done or What&#8217;s Left?</title>
	<atom:link href="http://www.jrothman.com/blog/mpd/2004/10/are-you-measuring-whats-done-or-whats-left.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.jrothman.com/blog/mpd/2004/10/are-you-measuring-whats-done-or-whats-left.html</link>
	<description>Management, especially good management, is hard to do. This blog is for people who want to think about how they manage people, projects, and risk.</description>
	<lastBuildDate>Fri, 18 May 2012 15:02:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: David Anderson</title>
		<link>http://www.jrothman.com/blog/mpd/2004/10/are-you-measuring-whats-done-or-whats-left.html/comment-page-1#comment-15</link>
		<dc:creator>David Anderson</dc:creator>
		<pubDate>Tue, 11 Jan 2005 03:53:47 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/?p=8214#comment-15</guid>
		<description>I&#039;m sorry but this just doesn&#039;t resonate with me at all.
The &quot;how much do we still have to do&quot;, is just the other side of the EV coin.
If you&#039;re talking about burn down charts in Scrum (measured in hours or days) then those are just traditional EV charts. There not new.
My view of agile is that you report the working code - the business function that is complete - the value delivered. It&#039;s not EV in the traditional sense but it would resonate with the common lay person interpretation of what &quot;earned value&quot; ought to mean.
Agile isn&#039;t about &quot;on-time, on-budget with agreed function&quot;. It&#039;s about &quot;do the best you possibly can with the time limit and release it as working code.&quot;
You don&#039;t report the what&#039;s left to do, you report the velocity and an estimate of what is likely to be completed within the time limit.</description>
		<content:encoded><![CDATA[<p>I&#8217;m sorry but this just doesn&#8217;t resonate with me at all.<br />
The &#8220;how much do we still have to do&#8221;, is just the other side of the EV coin.<br />
If you&#8217;re talking about burn down charts in Scrum (measured in hours or days) then those are just traditional EV charts. There not new.<br />
My view of agile is that you report the working code &#8211; the business function that is complete &#8211; the value delivered. It&#8217;s not EV in the traditional sense but it would resonate with the common lay person interpretation of what &#8220;earned value&#8221; ought to mean.<br />
Agile isn&#8217;t about &#8220;on-time, on-budget with agreed function&#8221;. It&#8217;s about &#8220;do the best you possibly can with the time limit and release it as working code.&#8221;<br />
You don&#8217;t report the what&#8217;s left to do, you report the velocity and an estimate of what is likely to be completed within the time limit.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

