<?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: The art of estimating</title>
	<atom:link href="http://jonkruger.com/blog/2008/08/31/the-art-of-estimating/feed/" rel="self" type="application/rss+xml" />
	<link>http://jonkruger.com/blog/2008/08/31/the-art-of-estimating/</link>
	<description></description>
	<pubDate>Sat, 31 Jul 2010 18:56:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tim</title>
		<link>http://jonkruger.com/blog/2008/08/31/the-art-of-estimating/comment-page-1/#comment-3103</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Sat, 13 Sep 2008 13:17:47 +0000</pubDate>
		<guid isPermaLink="false">http://jonkruger.com/blog/2008/08/31/the-art-of-estimating/#comment-3103</guid>
		<description>Great post, Jon.

One way to help with the "being held to your estimates" portion of working with the project sponsors is to offer a range. A realistic range, but giving a range at the high level opens you up to get back with better details after the team does its estimates. I'm not saying we shouldn't be held to them, but it's easier to be successful with a 70-90 hour estimate than an 80 hour estimate.

Also, when agiling it up, when you encounter something that's going to drastically effect your estimate, bring it up sooner than later. Like you said, your client may not like the news, but at least having the information allows them to plan for it. (Or they may like if the change brings you in well under your estimate.)</description>
		<content:encoded><![CDATA[<p>Great post, Jon.</p>
<p>One way to help with the &#8220;being held to your estimates&#8221; portion of working with the project sponsors is to offer a range. A realistic range, but giving a range at the high level opens you up to get back with better details after the team does its estimates. I&#8217;m not saying we shouldn&#8217;t be held to them, but it&#8217;s easier to be successful with a 70-90 hour estimate than an 80 hour estimate.</p>
<p>Also, when agiling it up, when you encounter something that&#8217;s going to drastically effect your estimate, bring it up sooner than later. Like you said, your client may not like the news, but at least having the information allows them to plan for it. (Or they may like if the change brings you in well under your estimate.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
