<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: How long will that take you? Let Legos lead the way</title>
	<atom:link href="http://nerdguru.wordpress.com/2007/06/07/how-long-will-that-take-you-let-legos-lead-the-way/feed/" rel="self" type="application/rss+xml" />
	<link>http://nerdguru.wordpress.com/2007/06/07/how-long-will-that-take-you-let-legos-lead-the-way/</link>
	<description>By Pete Johnson, Because technical people need good soft skills to get ahead.</description>
	<lastBuildDate>Fri, 05 Jun 2009 15:38:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Anonymous</title>
		<link>http://nerdguru.wordpress.com/2007/06/07/how-long-will-that-take-you-let-legos-lead-the-way/#comment-137</link>
		<dc:creator><![CDATA[Anonymous]]></dc:creator>
		<pubDate>Fri, 08 Jun 2007 13:56:00 +0000</pubDate>
		<guid isPermaLink="false">http://nerdguru.dreamhosters.com/2007/06/07/how-long-will-that-take-you-let-legos-lead-the-way/#comment-137</guid>
		<description><![CDATA[I agree the key to getting better at task estimation is what you said in the last sentence: &quot;repetition&quot;.&lt;br/&gt;&lt;br/&gt;Problems arise when people try to estimate tasks that are new or difficult. In web development, for example, I can sit down and estimate with a fair amount of accuracy how long it takes to put together a struts-based jsp form backed by an ejb call or two. Why can I do this? Because I&#039;ve done about 60 of them in the webapp we develop at work. I have already worked through all the insipid monkey wrenches that have burned through my time in the past like browser incompatibilities, css annoyances and many other time-wasters that I know as well as I know the plot to a repeat sitcom.&lt;br/&gt;&lt;br/&gt;So, what screws me up? Anything new. Last month I had to modify a bunch of VBA macros in an excel worksheet. I had worked on it before about 2 years ago, but not since and had basically &quot;forgotten&quot; VBA. My initial estimate: 2 days. My actual time: 2 weeks.&lt;br/&gt;&lt;br/&gt;I imagine that I would get similar horrific mis-estimates if there was a twist in the web-app, like, for example switching IDE&#039;s, moving to struts 2, using a new javascript library, etc.]]></description>
		<content:encoded><![CDATA[<p>I agree the key to getting better at task estimation is what you said in the last sentence: &#8220;repetition&#8221;.</p>
<p>Problems arise when people try to estimate tasks that are new or difficult. In web development, for example, I can sit down and estimate with a fair amount of accuracy how long it takes to put together a struts-based jsp form backed by an ejb call or two. Why can I do this? Because I&#8217;ve done about 60 of them in the webapp we develop at work. I have already worked through all the insipid monkey wrenches that have burned through my time in the past like browser incompatibilities, css annoyances and many other time-wasters that I know as well as I know the plot to a repeat sitcom.</p>
<p>So, what screws me up? Anything new. Last month I had to modify a bunch of VBA macros in an excel worksheet. I had worked on it before about 2 years ago, but not since and had basically &#8220;forgotten&#8221; VBA. My initial estimate: 2 days. My actual time: 2 weeks.</p>
<p>I imagine that I would get similar horrific mis-estimates if there was a twist in the web-app, like, for example switching IDE&#8217;s, moving to struts 2, using a new javascript library, etc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

