<?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: Earned Value in a Nutshell</title>
	<atom:link href="http://www.agilekiwi.com/earnedvalue/earned-value-in-a-nutshell/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.agilekiwi.com/earnedvalue/earned-value-in-a-nutshell/</link>
	<description>The neglected essentials of software development</description>
	<lastBuildDate>Fri, 03 Feb 2012 07:28:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Apples and Oranges</title>
		<link>http://www.agilekiwi.com/earnedvalue/earned-value-in-a-nutshell/comment-page-1/#comment-377</link>
		<dc:creator>Apples and Oranges</dc:creator>
		<pubDate>Fri, 20 May 2011 02:31:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.agilekiwi.com/?p=268#comment-377</guid>
		<description>[...] Value teaches us that the only valid measure is to compare actual cost with actual progress.&#160;&#160; This may seem a bit like “comparing [...]</description>
		<content:encoded><![CDATA[<p>[...] Value teaches us that the only valid measure is to compare actual cost with actual progress.&#160;&#160; This may seem a bit like “comparing [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Rusk</title>
		<link>http://www.agilekiwi.com/earnedvalue/earned-value-in-a-nutshell/comment-page-1/#comment-299</link>
		<dc:creator>John Rusk</dc:creator>
		<pubDate>Mon, 29 Nov 2010 07:39:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.agilekiwi.com/?p=268#comment-299</guid>
		<description>Vadali,

No, Earned Value does not give cost variance (&quot;are we on budget?&quot;) and progress variance (&quot;are we on time?&quot;) in a _single_ number.  Instead, there are two numbers, one for cost variance and one for schedule variance.

My &quot;rule 1&quot; above is really about cost variance.  I focussed on cost variance on this page beause that is where Earned Value most out-performs the alternatives.

You can find more details on cost and schedule variance in my encylopedia article, which should be on sale here shortly: http://www.informaworld.com/smpp/content~db=all~content=a929423176~frm=titlelink  (Currently, online purchase is disabled, but they tell me that is just a temporary problem).</description>
		<content:encoded><![CDATA[<p>Vadali,</p>
<p>No, Earned Value does not give cost variance (&#8220;are we on budget?&#8221;) and progress variance (&#8220;are we on time?&#8221;) in a _single_ number.  Instead, there are two numbers, one for cost variance and one for schedule variance.</p>
<p>My &#8220;rule 1&#8243; above is really about cost variance.  I focussed on cost variance on this page beause that is where Earned Value most out-performs the alternatives.</p>
<p>You can find more details on cost and schedule variance in my encylopedia article, which should be on sale here shortly: <a href="http://www.informaworld.com/smpp/content~db=all~content=a929423176~frm=titlelink" rel="nofollow">http://www.informaworld.com/smpp/content~db=all~content=a929423176~frm=titlelink</a>  (Currently, online purchase is disabled, but they tell me that is just a temporary problem).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vadali</title>
		<link>http://www.agilekiwi.com/earnedvalue/earned-value-in-a-nutshell/comment-page-1/#comment-298</link>
		<dc:creator>Vadali</dc:creator>
		<pubDate>Sat, 27 Nov 2010 20:35:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.agilekiwi.com/?p=268#comment-298</guid>
		<description>Hi John,
Your article gave me good input to start understanding EVM. I want to know is Earned value in single unique number which projects cost variance as well as progress variance.Pl elaborate.

vadali</description>
		<content:encoded><![CDATA[<p>Hi John,<br />
Your article gave me good input to start understanding EVM. I want to know is Earned value in single unique number which projects cost variance as well as progress variance.Pl elaborate.</p>
<p>vadali</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Rusk</title>
		<link>http://www.agilekiwi.com/earnedvalue/earned-value-in-a-nutshell/comment-page-1/#comment-29</link>
		<dc:creator>John Rusk</dc:creator>
		<pubDate>Mon, 31 May 2010 06:12:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.agilekiwi.com/?p=268#comment-29</guid>
		<description>Many thanks Paul.  I&#039;ve re-written much of the rule 2 section, above, to reflect your feedback re the orginal wording being too fatalistic. (I completely agree.  It was :-)

Your article sounds interesting, I&#039;ll check it out.</description>
		<content:encoded><![CDATA[<p>Many thanks Paul.  I&#8217;ve re-written much of the rule 2 section, above, to reflect your feedback re the orginal wording being too fatalistic. (I completely agree.  It was :-)</p>
<p>Your article sounds interesting, I&#8217;ll check it out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dr. Paul D. Giammalvo</title>
		<link>http://www.agilekiwi.com/earnedvalue/earned-value-in-a-nutshell/comment-page-1/#comment-28</link>
		<dc:creator>Dr. Paul D. Giammalvo</dc:creator>
		<pubDate>Mon, 31 May 2010 02:01:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.agilekiwi.com/?p=268#comment-28</guid>
		<description>Hi John,
Your first rule is as good a summary of EVM as any, but your second rule is somewhat fatalistic sounding.   The whole idea behind using EVM as a management tool is to enable us to identify whether our project is headed in the wrong direction early enough to take corrective action to FIX it.....  So rule 2 might be better modified to read &quot;Assume whatever happened in the past will continue unless we take action to change the outcome for the better&quot;.

You may find this article I wrote some years back.  Like you, I think Earned Value is made far, far more complicated than it need be (as only Government bureaucrats are able to do) than it need be and have argued for years that each and everyone of us uses the fundamental concepts underlying earned value (&quot;Quantum Meruit&quot;) each time we go to the green grocer. http://www.pmforum.org/library/papers/2007/PDFs/Giammalvo-5-07.pdf

BR,
Dr. PDG, Jakarta
http://www.build-project-management-competency.com</description>
		<content:encoded><![CDATA[<p>Hi John,<br />
Your first rule is as good a summary of EVM as any, but your second rule is somewhat fatalistic sounding.   The whole idea behind using EVM as a management tool is to enable us to identify whether our project is headed in the wrong direction early enough to take corrective action to FIX it&#8230;..  So rule 2 might be better modified to read &#8220;Assume whatever happened in the past will continue unless we take action to change the outcome for the better&#8221;.</p>
<p>You may find this article I wrote some years back.  Like you, I think Earned Value is made far, far more complicated than it need be (as only Government bureaucrats are able to do) than it need be and have argued for years that each and everyone of us uses the fundamental concepts underlying earned value (&#8220;Quantum Meruit&#8221;) each time we go to the green grocer. <a href="http://www.pmforum.org/library/papers/2007/PDFs/Giammalvo-5-07.pdf" rel="nofollow">http://www.pmforum.org/library/papers/2007/PDFs/Giammalvo-5-07.pdf</a></p>
<p>BR,<br />
Dr. PDG, Jakarta<br />
<a href="http://www.build-project-management-competency.com" rel="nofollow">http://www.build-project-management-competency.com</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

