<?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: Fundamentals of Range Estimating in Project Management</title>
	<atom:link href="http://www.pmhut.com/fundamentals-of-range-estimating-in-project-management/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/fundamentals-of-range-estimating-in-project-management</link>
	<description></description>
	<pubDate>Tue, 22 May 2012 19:56:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Glen B Alleman</title>
		<link>http://www.pmhut.com/fundamentals-of-range-estimating-in-project-management/comment-page-1#comment-18958</link>
		<dc:creator>Glen B Alleman</dc:creator>
		<pubDate>Wed, 17 Mar 2010 15:46:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4994#comment-18958</guid>
		<description>Bill,

It is absolutely clear. 

It is also clear that range estimates have VERY serious systemic problems on real projects.

Ignoring this usually results in very unpleasant surprises in practice.</description>
		<content:encoded><![CDATA[<p>Bill,</p>
<p>It is absolutely clear. </p>
<p>It is also clear that range estimates have VERY serious systemic problems on real projects.</p>
<p>Ignoring this usually results in very unpleasant surprises in practice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Duncan</title>
		<link>http://www.pmhut.com/fundamentals-of-range-estimating-in-project-management/comment-page-1#comment-18951</link>
		<dc:creator>Bill Duncan</dc:creator>
		<pubDate>Wed, 17 Mar 2010 11:43:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4994#comment-18951</guid>
		<description>Glen -- I thought it was clear in the article that by "range estimates" covered distributions. Triangular distributions are illustrated and discussed in the article.</description>
		<content:encoded><![CDATA[<p>Glen &#8212; I thought it was clear in the article that by &#8220;range estimates&#8221; covered distributions. Triangular distributions are illustrated and discussed in the article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Glen B Alleman</title>
		<link>http://www.pmhut.com/fundamentals-of-range-estimating-in-project-management/comment-page-1#comment-18922</link>
		<dc:creator>Glen B Alleman</dc:creator>
		<pubDate>Wed, 17 Mar 2010 04:19:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4994#comment-18922</guid>
		<description>Dina,

All credible PM applications provide abilities to have ranges. Not sure what software would not.</description>
		<content:encoded><![CDATA[<p>Dina,</p>
<p>All credible PM applications provide abilities to have ranges. Not sure what software would not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dina Garfinkel, PMP</title>
		<link>http://www.pmhut.com/fundamentals-of-range-estimating-in-project-management/comment-page-1#comment-18917</link>
		<dc:creator>Dina Garfinkel, PMP</dc:creator>
		<pubDate>Wed, 17 Mar 2010 02:28:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4994#comment-18917</guid>
		<description>Great lesson here on ranged estimates. But to correct you on this one point: 

"I tried range estimates once before, but my project management software only has room for one estimate!"

There IS a PM software that allows for ranged estimates. LiquidPlanner (http://www.liquidplanner.com/) was built around the whole concept of ranged estimates, giving the PM the ability to make a truly reliable project schedule. In fact, the CEO of LiquidPlanner, Charles Seybold, just made an excellent blog post about the power of data with analyzing a ranged estimate here: http://bit.ly/9YcbxS</description>
		<content:encoded><![CDATA[<p>Great lesson here on ranged estimates. But to correct you on this one point: </p>
<p>&#8220;I tried range estimates once before, but my project management software only has room for one estimate!&#8221;</p>
<p>There IS a PM software that allows for ranged estimates. LiquidPlanner (http://www.liquidplanner.com/) was built around the whole concept of ranged estimates, giving the PM the ability to make a truly reliable project schedule. In fact, the CEO of LiquidPlanner, Charles Seybold, just made an excellent blog post about the power of data with analyzing a ranged estimate here: <a href="http://bit.ly/9YcbxS" rel="nofollow">http://bit.ly/9YcbxS</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Glen B Alleman</title>
		<link>http://www.pmhut.com/fundamentals-of-range-estimating-in-project-management/comment-page-1#comment-18912</link>
		<dc:creator>Glen B Alleman</dc:creator>
		<pubDate>Wed, 17 Mar 2010 00:12:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4994#comment-18912</guid>
		<description>Bill,

While range estimates are a starting point, they have been discouraged and sometimes disallowed in several project domains.

In their place are probability distributions (Triangle is good in the absence of any underlying historical data), and the variance spreads around the Most Likely value for cost or duration.

See DID 81650 as a guide.

The primary reason for this the well documented estimating bias of asking for upper and lower limits. The research started in the Naval Research Laboratory and is now used in oil&amp;gas well reserves, DoD, DOE, and DHS cost and schedule estimates.

There is a significant variance between the numbers dependency on what order they are asked. There are three permutations of how the numbers are captured. laboratory studies and field confirmation shows up to 27% variance in the elicited values, depending on the sequence.

Glen B. Alleman
VP, Program Planning and Controls
Aerospace and Defense Business Sector

References available on request...</description>
		<content:encoded><![CDATA[<p>Bill,</p>
<p>While range estimates are a starting point, they have been discouraged and sometimes disallowed in several project domains.</p>
<p>In their place are probability distributions (Triangle is good in the absence of any underlying historical data), and the variance spreads around the Most Likely value for cost or duration.</p>
<p>See DID 81650 as a guide.</p>
<p>The primary reason for this the well documented estimating bias of asking for upper and lower limits. The research started in the Naval Research Laboratory and is now used in oil&amp;gas well reserves, DoD, DOE, and DHS cost and schedule estimates.</p>
<p>There is a significant variance between the numbers dependency on what order they are asked. There are three permutations of how the numbers are captured. laboratory studies and field confirmation shows up to 27% variance in the elicited values, depending on the sequence.</p>
<p>Glen B. Alleman<br />
VP, Program Planning and Controls<br />
Aerospace and Defense Business Sector</p>
<p>References available on request&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

