<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Earned Value Management Systems Will Keep Us Out of Trouble&#8230;Don&#8217;t Count on It!</title>
	<link>http://www.reformingprojectmanagement.com/2004/11/09/431/</link>
	<description>The magazine for the project age</description>
	<pubDate>Sun, 12 Oct 2008 19:32:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Hal</title>
		<link>http://www.reformingprojectmanagement.com/2004/11/09/431/#comment-2186</link>
		<pubDate>Fri, 30 Dec 2005 17:34:27 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2004/11/09/431/#comment-2186</guid>
					<description>I've been involved with numerous planned maintenance projects at power stations.  I can't imagine doing a shut-down without an EVMS approach.  My posting addressed the vast majority of projects.  Most projects are managed with Excel.  And those projects don't need more than that.  But we may not have appropriate protocols for conforming to SOX.  We need an approach that captures the developing network of commitments on the project.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been involved with numerous planned maintenance projects at power stations.  I can&#8217;t imagine doing a shut-down without an EVMS approach.  My posting addressed the vast majority of projects.  Most projects are managed with Excel.  And those projects don&#8217;t need more than that.  But we may not have appropriate protocols for conforming to SOX.  We need an approach that captures the developing network of commitments on the project.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Wayne Abba</title>
		<link>http://www.reformingprojectmanagement.com/2004/11/09/431/#comment-2183</link>
		<pubDate>Fri, 30 Dec 2005 16:53:27 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2004/11/09/431/#comment-2183</guid>
					<description>A company using EVM certainly should use EV projections as one method to estimate revenue... that's just common sense that takes on more meaning with SOX.  And EVM is a path to better controls.  But there's a larger point.  Hal, I must disagree with your definition of EVM.  It is definitely not "a system designed for authorizing payments from the customer."  One could get that impression if one's experience was limited to very complex US govt contracts.  That's where I cut my teeth (disclaimer - I was responsible for US defense EVM implementation from 1982-99).  Its purpose always has been to provide an effective way to integrate resources, schedule and technical performance management and measurement.  But in govt, the "reporting" or "oversight" aspects tend to be overemphasized.

Way back in 1993, I saw a presentation titled "Real Time Earned Value: Controlling a Maintenance Shutdown at Australian Paper Manufacturers, Maryvale Mill," by Len Miller, Director, LMA Partnership Pty Ltd.  His take -- "During the hurly-burly of a maintenance shutdown, management control can be made easy using earned value graphical techniques.  This proven technique can help analyse performance and take away a lot of uncertainty and sleepless nights often associated with a major plant shutdown."

He goes on to describe "simple, clear, easy to read information" with results "obtained and processed within hours... quick turnaround times and faster feedback to the people who need it most results in a project that runs more smoothly.  Tensions are reduced when staff are confident in the knowledge that progress is being achieved."

A 10-day maintenance shutdown is not a complex project.  The value of EVM has been shown again and again around the world.  Its essential elements are explained in PMI's new Practice Standard for Earned Value Management (available free of charge to PMI members; others may purchase thru the PMI web site).  I always encourage EVM be used as intended -- as a management tool -- with reporting a natural by-product.</description>
		<content:encoded><![CDATA[<p>A company using EVM certainly should use EV projections as one method to estimate revenue&#8230; that&#8217;s just common sense that takes on more meaning with SOX.  And EVM is a path to better controls.  But there&#8217;s a larger point.  Hal, I must disagree with your definition of EVM.  It is definitely not &#8220;a system designed for authorizing payments from the customer.&#8221;  One could get that impression if one&#8217;s experience was limited to very complex US govt contracts.  That&#8217;s where I cut my teeth (disclaimer - I was responsible for US defense EVM implementation from 1982-99).  Its purpose always has been to provide an effective way to integrate resources, schedule and technical performance management and measurement.  But in govt, the &#8220;reporting&#8221; or &#8220;oversight&#8221; aspects tend to be overemphasized.</p>
<p>Way back in 1993, I saw a presentation titled &#8220;Real Time Earned Value: Controlling a Maintenance Shutdown at Australian Paper Manufacturers, Maryvale Mill,&#8221; by Len Miller, Director, LMA Partnership Pty Ltd.  His take &#8212; &#8220;During the hurly-burly of a maintenance shutdown, management control can be made easy using earned value graphical techniques.  This proven technique can help analyse performance and take away a lot of uncertainty and sleepless nights often associated with a major plant shutdown.&#8221;</p>
<p>He goes on to describe &#8220;simple, clear, easy to read information&#8221; with results &#8220;obtained and processed within hours&#8230; quick turnaround times and faster feedback to the people who need it most results in a project that runs more smoothly.  Tensions are reduced when staff are confident in the knowledge that progress is being achieved.&#8221;</p>
<p>A 10-day maintenance shutdown is not a complex project.  The value of EVM has been shown again and again around the world.  Its essential elements are explained in <acronym title="Project Management Institute">PMI</acronym>&#8217;s new Practice Standard for Earned Value Management (available free of charge to <acronym title="Project Management Institute">PMI</acronym> members; others may purchase thru the <acronym title="Project Management Institute">PMI</acronym> web site).  I always encourage EVM be used as intended &#8212; as a management tool &#8212; with reporting a natural by-product.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Donavan McDonough - Spreadshee
        </title>
		<link>http://www.reformingprojectmanagement.com/2004/11/09/431/#comment-260</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2004/11/09/431/#comment-260</guid>
					<description>
        There is a culprit that is getting away virtually undetected and that is spreadsheet risks, errors and fraud.

The Sarbox Act does little to address this weakness directly. It may put some internal controls in place but it does not necessarily stop Excel from being used for mission critical projects.
      </description>
		<content:encoded><![CDATA[<p>There is a culprit that is getting away virtually undetected and that is spreadsheet risks, errors and fraud.</p>
<p>The Sarbox Act does little to address this weakness directly. It may put some internal controls in place but it does not necessarily stop Excel from being used for mission critical projects.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Hal
        </title>
		<link>http://www.reformingprojectmanagement.com/2004/11/09/431/#comment-261</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2004/11/09/431/#comment-261</guid>
					<description>
        I couldn't help myself...
      </description>
		<content:encoded><![CDATA[<p>I couldn&#8217;t help myself&#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: David Waller
        </title>
		<link>http://www.reformingprojectmanagement.com/2004/11/09/431/#comment-262</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2004/11/09/431/#comment-262</guid>
					<description>
        Hal, I agree with you.  We have far too many top-down controls and too little emphasis on getting the right people, treating them right(training, empowerment, good processes); giving them worthwhile (ie strategy related) work to do and exercising management best practices.
      </description>
		<content:encoded><![CDATA[<p>Hal, I agree with you.  We have far too many top-down controls and too little emphasis on getting the right people, treating them right(training, empowerment, good processes); giving them worthwhile (ie strategy related) work to do and exercising management best practices.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
