<?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: Agile Estimation and the Cone of Uncertainty</title>
	<atom:link href="http://agile101.net/2009/08/18/agile-estimation-and-the-cone-of-uncertainty/feed/" rel="self" type="application/rss+xml" />
	<link>http://agile101.net/2009/08/18/agile-estimation-and-the-cone-of-uncertainty/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=agile-estimation-and-the-cone-of-uncertainty</link>
	<description>Agile Project Management, Programme Management and Digital Publishing</description>
	<lastBuildDate>Thu, 22 Jul 2010 09:14:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Agile Requirements in a Waterfall World &#124; Diary of a Software Manager</title>
		<link>http://agile101.net/2009/08/18/agile-estimation-and-the-cone-of-uncertainty/comment-page-1/#comment-1311</link>
		<dc:creator>Agile Requirements in a Waterfall World &#124; Diary of a Software Manager</dc:creator>
		<pubDate>Sat, 27 Mar 2010 01:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://agile101.net/?p=1070#comment-1311</guid>
		<description>[...] read an interesting post about this topic recently. The argument here is that since your estimates get more accurate as you [...]</description>
		<content:encoded><![CDATA[<p>[...] read an interesting post about this topic recently. The argument here is that since your estimates get more accurate as you [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Perfume</title>
		<link>http://agile101.net/2009/08/18/agile-estimation-and-the-cone-of-uncertainty/comment-page-1/#comment-1302</link>
		<dc:creator>Perfume</dc:creator>
		<pubDate>Wed, 17 Mar 2010 02:01:22 +0000</pubDate>
		<guid isPermaLink="false">http://agile101.net/?p=1070#comment-1302</guid>
		<description>Sup 

I respect the design of your articles, long but not and informative, yet you get a lot of them. Keeps me wishing to learn more. I will be sure to check each of them! 

Goodbye</description>
		<content:encoded><![CDATA[<p>Sup </p>
<p>I respect the design of your articles, long but not and informative, yet you get a lot of them. Keeps me wishing to learn more. I will be sure to check each of them! </p>
<p>Goodbye</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Sanderson</title>
		<link>http://agile101.net/2009/08/18/agile-estimation-and-the-cone-of-uncertainty/comment-page-1/#comment-510</link>
		<dc:creator>Adam Sanderson</dc:creator>
		<pubDate>Tue, 08 Sep 2009 23:23:48 +0000</pubDate>
		<guid isPermaLink="false">http://agile101.net/?p=1070#comment-510</guid>
		<description>Hey, I&#039;m a developer over at LiquidPlanner (we make project planning software based on uncertain estimates).  

One approach that I think is really helpful is to estimate not just in hours, but in ranges.  If you have a lot of uncertainty  start with a large range (maybe this story will take 3 to 6 days).  As you work on it, and gather more information, you can narrow those estimates down to smaller ranges as time goes by.  

This model really helps communicate both the uncertainty, and the size of a story to stakeholders, and  it helps everyone get a sense of progress as people narrow those estimates down.</description>
		<content:encoded><![CDATA[<p>Hey, I&#8217;m a developer over at LiquidPlanner (we make project planning software based on uncertain estimates).  </p>
<p>One approach that I think is really helpful is to estimate not just in hours, but in ranges.  If you have a lot of uncertainty  start with a large range (maybe this story will take 3 to 6 days).  As you work on it, and gather more information, you can narrow those estimates down to smaller ranges as time goes by.  </p>
<p>This model really helps communicate both the uncertainty, and the size of a story to stakeholders, and  it helps everyone get a sense of progress as people narrow those estimates down.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith Braithwaite</title>
		<link>http://agile101.net/2009/08/18/agile-estimation-and-the-cone-of-uncertainty/comment-page-1/#comment-508</link>
		<dc:creator>Keith Braithwaite</dc:creator>
		<pubDate>Tue, 08 Sep 2009 22:10:38 +0000</pubDate>
		<guid isPermaLink="false">http://agile101.net/?p=1070#comment-508</guid>
		<description>I&#039;d be interested to know what you think of these two stories about estimation and scale: http://peripateticaxiom.blogspot.com/2009/09/observations-on-estimation.html

I tend to avoid trying to estimate epics because the results are too imprecise to be useful, and also to avoid trying to estimate tasks as the results are too precise to be safe.

My understanding of the cone is that it prompts us to avoid doing estimation until later, at any scale. What I don&#039;t quite get about your diagram is that it seems to suggest that we go down the cone once for the refinement of an epic to stories to tasks...but then what? Do we start again with another cone? Or, do we see our ability to estimate at a given scale improve over the lifetime of a whole project? My experience suggests the latter.</description>
		<content:encoded><![CDATA[<p>I&#8217;d be interested to know what you think of these two stories about estimation and scale: <a href="http://peripateticaxiom.blogspot.com/2009/09/observations-on-estimation.html" rel="nofollow">http://peripateticaxiom.blogspot.com/2009/09/observations-on-estimation.html</a></p>
<p>I tend to avoid trying to estimate epics because the results are too imprecise to be useful, and also to avoid trying to estimate tasks as the results are too precise to be safe.</p>
<p>My understanding of the cone is that it prompts us to avoid doing estimation until later, at any scale. What I don&#8217;t quite get about your diagram is that it seems to suggest that we go down the cone once for the refinement of an epic to stories to tasks&#8230;but then what? Do we start again with another cone? Or, do we see our ability to estimate at a given scale improve over the lifetime of a whole project? My experience suggests the latter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FabriceAimetti</title>
		<link>http://agile101.net/2009/08/18/agile-estimation-and-the-cone-of-uncertainty/comment-page-1/#comment-195</link>
		<dc:creator>FabriceAimetti</dc:creator>
		<pubDate>Fri, 21 Aug 2009 15:12:39 +0000</pubDate>
		<guid isPermaLink="false">http://agile101.net/?p=1070#comment-195</guid>
		<description>Hello. I have translated in french your excellent article : &lt;a href=&quot;http://www.fabrice-aimetti.fr/dotclear/index.php?post/2009/08/21/Estimation-Agile-et-Cone-d-incertitude&quot; rel=&quot;nofollow&quot;&gt;Estimation Agile et Cône d&#039;incertitude&lt;/a&gt;. Regards, Fabrice.</description>
		<content:encoded><![CDATA[<p>Hello. I have translated in french your excellent article : <a href="http://www.fabrice-aimetti.fr/dotclear/index.php?post/2009/08/21/Estimation-Agile-et-Cone-d-incertitude" rel="nofollow">Estimation Agile et Cône d&#8217;incertitude</a>. Regards, Fabrice.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
