<?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: Critical Lesson in Estimation</title>
	<atom:link href="http://stevenmsmith.com/critical-lesson-in-estimation/feed/" rel="self" type="application/rss+xml" />
	<link>http://stevenmsmith.com/critical-lesson-in-estimation/</link>
	<description>Accelerating Team Productivity</description>
	<lastBuildDate>Thu, 19 Apr 2012 17:51:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Esther Estimate</title>
		<link>http://stevenmsmith.com/critical-lesson-in-estimation/comment-page-1/#comment-197</link>
		<dc:creator>Esther Estimate</dc:creator>
		<pubDate>Sun, 20 Apr 2008 19:35:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevenmsmith.com/wordpress/?p=38#comment-197</guid>
		<description>rather...

People who will do the work should do the estimation as well.</description>
		<content:encoded><![CDATA[<p>rather&#8230;</p>
<p>People who will do the work should do the estimation as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven M. Smith</title>
		<link>http://stevenmsmith.com/critical-lesson-in-estimation/comment-page-1/#comment-139</link>
		<dc:creator>Steven M. Smith</dc:creator>
		<pubDate>Tue, 26 Jun 2007 21:28:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevenmsmith.com/wordpress/?p=38#comment-139</guid>
		<description>Arnon,

I suspect you already know.

I looked at your website, which I now wish I would have looked at before my first reply. I see you are very experienced.

I suspect you have experience about happens when inexperienced people make estimates. 

My experience is that inexperienced people do their best when making estimates. Unfortunately, they tend to underestimate.

I don&#039;t think anyone should be surprised.

Warm regards,
-Steve</description>
		<content:encoded><![CDATA[<p>Arnon,</p>
<p>I suspect you already know.</p>
<p>I looked at your website, which I now wish I would have looked at before my first reply. I see you are very experienced.</p>
<p>I suspect you have experience about happens when inexperienced people make estimates. </p>
<p>My experience is that inexperienced people do their best when making estimates. Unfortunately, they tend to underestimate.</p>
<p>I don&#8217;t think anyone should be surprised.</p>
<p>Warm regards,<br />
-Steve</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven M. Smith</title>
		<link>http://stevenmsmith.com/critical-lesson-in-estimation/comment-page-1/#comment-138</link>
		<dc:creator>Steven M. Smith</dc:creator>
		<pubDate>Tue, 26 Jun 2007 15:52:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevenmsmith.com/wordpress/?p=38#comment-138</guid>
		<description>Hi Arnon,

Don&#039;t Hide the Estimate&#039;s Variability.

The forecast from an inexperienced IT person are typically worse than the forecasts of an inexperienced meteorologist. Why? The forecasts of meteorologists are grounded in probability. They talk about the chance of rain rather than saying it will rain tomorrow. Inexperienced IT people typically use point estimates, such as, &quot;We will deliver on August 2nd,&quot; which prevents their customers from seeing the inherent variability of an estimate.

Meteorologists are also trained on how to forecast while IT people, in my experience, typically receive little training on estimation. And if they do receive training, their company&#039;s culture may prevent them from practicing what they learn.

Meteorologists also have data and models to aid their predictions. IT people, in my experience, rarely have data about previous projects and typically have zero models for making estimates.

I believe estimation is an art as well as a science. People need experience in order to make solid estimates.

If inexperienced people must make the estimate, I suggest avoiding point estimates entirely. Like a meteorologist, create a probability based forecast. I like a graph with the x-axis being time and the cumulative probability of delivery on the y-axis. The graph is dynamic rather than static. As you learn more, the probability change.

I&#039;ve notice that many groups are afraid to share their uncertainty with their customers until they must. I don&#039;t recommend that approach. But if, for whatever reason, you must hide the estimate&#039;s variability from your customer, that doesn&#039;t stop you from making it visible internally.

You learn to be a better estimator by practicing. If you hide the variability from yourself, it&#039;s poor practice.

Thank you for the question. And I wish you and your group success with your efforts.

Best regards,
-Steve</description>
		<content:encoded><![CDATA[<p>Hi Arnon,</p>
<p>Don&#8217;t Hide the Estimate&#8217;s Variability.</p>
<p>The forecast from an inexperienced IT person are typically worse than the forecasts of an inexperienced meteorologist. Why? The forecasts of meteorologists are grounded in probability. They talk about the chance of rain rather than saying it will rain tomorrow. Inexperienced IT people typically use point estimates, such as, &#8220;We will deliver on August 2nd,&#8221; which prevents their customers from seeing the inherent variability of an estimate.</p>
<p>Meteorologists are also trained on how to forecast while IT people, in my experience, typically receive little training on estimation. And if they do receive training, their company&#8217;s culture may prevent them from practicing what they learn.</p>
<p>Meteorologists also have data and models to aid their predictions. IT people, in my experience, rarely have data about previous projects and typically have zero models for making estimates.</p>
<p>I believe estimation is an art as well as a science. People need experience in order to make solid estimates.</p>
<p>If inexperienced people must make the estimate, I suggest avoiding point estimates entirely. Like a meteorologist, create a probability based forecast. I like a graph with the x-axis being time and the cumulative probability of delivery on the y-axis. The graph is dynamic rather than static. As you learn more, the probability change.</p>
<p>I&#8217;ve notice that many groups are afraid to share their uncertainty with their customers until they must. I don&#8217;t recommend that approach. But if, for whatever reason, you must hide the estimate&#8217;s variability from your customer, that doesn&#8217;t stop you from making it visible internally.</p>
<p>You learn to be a better estimator by practicing. If you hide the variability from yourself, it&#8217;s poor practice.</p>
<p>Thank you for the question. And I wish you and your group success with your efforts.</p>
<p>Best regards,<br />
-Steve</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arnon Rotem-Gal-Oz</title>
		<link>http://stevenmsmith.com/critical-lesson-in-estimation/comment-page-1/#comment-136</link>
		<dc:creator>Arnon Rotem-Gal-Oz</dc:creator>
		<pubDate>Tue, 26 Jun 2007 10:17:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevenmsmith.com/wordpress/?p=38#comment-136</guid>
		<description>Inexperienced people: What happens when the people who would actually have to perform the task are those inexperienced folks - what does that mean for the educated estimates?...</description>
		<content:encoded><![CDATA[<p>Inexperienced people: What happens when the people who would actually have to perform the task are those inexperienced folks &#8211; what does that mean for the educated estimates?&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

