<?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: Planning, Scheduling, and Forecasting</title>
	<link>http://www.reformingprojectmanagement.com/2007/02/20/772/</link>
	<description>The magazine for the project age</description>
	<pubDate>Fri, 08 Aug 2008 20:51:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Robert Ferguson</title>
		<link>http://www.reformingprojectmanagement.com/2007/02/20/772/#comment-13361</link>
		<pubDate>Wed, 21 Feb 2007 13:47:06 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2007/02/20/772/#comment-13361</guid>
					<description>Hal,
Nice comment about forecasting today. In fact both estimation and forecasting require some knowledge (history) of team performance. Last planner uses %ppc as a performance measure. 

If I have knowledge of team performance then the team can make projections about completion and range of error (risk).  

Team level measures must be owned and collected by the team. I suggest we consider performance measures for schedule, throughput, productivity and a quality index. 

The project manager can keep each of the performance measures for each team as a stoplight. A team operating as desired gets green lights. This does not mean perfect but means within the % error inherent in the work and measurement system. A team operating within the bounds of their contingency gets yellow. A team that is operating outside of contingency gets red.

Any red light or three successive yellow lights warrants an investigation and possible change action. Something in the plan is not working or something is happening at the team level that will cause a problem.

Forecasting is important. It is what our sponsors and customers want to know and informing them is an essential element of project success.

Bob Ferguson</description>
		<content:encoded><![CDATA[<p>Hal,<br />
Nice comment about forecasting today. In fact both estimation and forecasting require some knowledge (history) of team performance. Last planner uses %<acronym title="Percent of Promises Complete">PPC</acronym> as a performance measure. </p>
<p>If I have knowledge of team performance then the team can make projections about completion and range of error (risk).  </p>
<p>Team level measures must be owned and collected by the team. I suggest we consider performance measures for schedule, throughput, productivity and a quality index. </p>
<p>The project manager can keep each of the performance measures for each team as a stoplight. A team operating as desired gets green lights. This does not mean perfect but means within the % error inherent in the work and measurement system. A team operating within the bounds of their contingency gets yellow. A team that is operating outside of contingency gets red.</p>
<p>Any red light or three successive yellow lights warrants an investigation and possible change action. Something in the plan is not working or something is happening at the team level that will cause a problem.</p>
<p>Forecasting is important. It is what our sponsors and customers want to know and informing them is an essential element of project success.</p>
<p>Bob Ferguson
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Glen B. Alleman</title>
		<link>http://www.reformingprojectmanagement.com/2007/02/20/772/#comment-13353</link>
		<pubDate>Wed, 21 Feb 2007 05:15:26 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2007/02/20/772/#comment-13353</guid>
					<description>Hal,
I see in your example the source of the comments on "scheduling" of the repairman and the questions to PM's regarding forecasting. The world of project management as a profession is very broad and very deep. With overlap in some cases. The defense experinces I speak of are also found in large construction in the petrochemical industray for example. Finance and insurance enteprise project have similar processes in place for seperating planning from scehduling. 

There are no doubt unlimted counter examples to me experinces. So when you say "project managers and planners haven't been trained to forecast," a qualification of domain may add value, because all the ones I've know over the decades at places like Chevron, Texaco, Bosie Cascade, Duke Power, Salt River, SCE, PG&#38;E, Monsanto, Wells Fargo, Amgen, Exxon, TVA, ... have in most cases acted in ways I describe. 

Isn't it a wonderful things to have such variety?</description>
		<content:encoded><![CDATA[<p>Hal,<br />
I see in your example the source of the comments on &#8220;scheduling&#8221; of the repairman and the questions to PM&#8217;s regarding forecasting. The world of project management as a profession is very broad and very deep. With overlap in some cases. The defense experinces I speak of are also found in large construction in the petrochemical industray for example. Finance and insurance enteprise project have similar processes in place for seperating planning from scehduling. </p>
<p>There are no doubt unlimted counter examples to me experinces. So when you say &#8220;project managers and planners haven&#8217;t been trained to forecast,&#8221; a qualification of domain may add value, because all the ones I&#8217;ve know over the decades at places like Chevron, Texaco, Bosie Cascade, Duke Power, Salt River, SCE, PG&amp;E, Monsanto, Wells Fargo, Amgen, Exxon, <acronym title="Time value analysis, practice of charting value and non-value work on a time scale">TVA</acronym>, &#8230; have in most cases acted in ways I describe. </p>
<p>Isn&#8217;t it a wonderful things to have such variety?
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
