<?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#"
	
	>
<channel>
	<title>
	Comments on: How do you estimate that which you&#8217;ve never done?	</title>
	<atom:link href="https://www.robg3d.com/2015/01/how-do-you-estimate-that-which-youve-never-done/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.robg3d.com/2015/01/how-do-you-estimate-that-which-youve-never-done/</link>
	<description>Blog of Rob Galanakis (@robgalanakis)</description>
	<lastBuildDate>Fri, 30 Jan 2015 01:27:39 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.4.2</generator>
	<item>
		<title>
		By: robert		</title>
		<link>https://www.robg3d.com/2015/01/how-do-you-estimate-that-which-youve-never-done/#comment-236422</link>

		<dc:creator><![CDATA[robert]]></dc:creator>
		<pubDate>Fri, 30 Jan 2015 01:27:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.robg3d.com/?p=1789#comment-236422</guid>

					<description><![CDATA[There are always estimates. The difference lies in coarseness. And you can, and you should! keep constantly adjusting estimates. Project planning doesn&#039;t just happen and it&#039;s over. It&#039;s an ongoing proces of monitoring and adjustments.

Many people make the mistake of thinking the first estimate needs to be accurate, which is rather stupid, becasue it&#039;s rather difficult, especially with anything RnD type projects. So start coards. Can you do it in one year? How about a month? a week? a day? At some point uncertainty sets in. Then you have your first estimate. Then do whatever it takes to remove uncertainty so you can refine your estimate. If it&#039;s prototypes and exploration, then go that&#039;s what it takes.

Regarding past behavior: Generally a good gauge, except when your team changes or the nature of the project does and you end up comparing apples with pears. Othewise it&#039;s a good approach, if you bothered to collect some project metrics and post mortems.]]></description>
			<content:encoded><![CDATA[<p>There are always estimates. The difference lies in coarseness. And you can, and you should! keep constantly adjusting estimates. Project planning doesn&#8217;t just happen and it&#8217;s over. It&#8217;s an ongoing proces of monitoring and adjustments.</p>
<p>Many people make the mistake of thinking the first estimate needs to be accurate, which is rather stupid, becasue it&#8217;s rather difficult, especially with anything RnD type projects. So start coards. Can you do it in one year? How about a month? a week? a day? At some point uncertainty sets in. Then you have your first estimate. Then do whatever it takes to remove uncertainty so you can refine your estimate. If it&#8217;s prototypes and exploration, then go that&#8217;s what it takes.</p>
<p>Regarding past behavior: Generally a good gauge, except when your team changes or the nature of the project does and you end up comparing apples with pears. Othewise it&#8217;s a good approach, if you bothered to collect some project metrics and post mortems.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
