<?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: 30 Random Things About Software Project Estimates</title>
	<atom:link href="http://utpal.net/blog/2009/08/19/30-random-things-about-software-project-estimates/feed/" rel="self" type="application/rss+xml" />
	<link>http://utpal.net/blog/2009/08/19/30-random-things-about-software-project-estimates/</link>
	<description>          &#160;On Projects, Leadership &#38; Self-Help</description>
	<lastBuildDate>Thu, 09 Sep 2010 03:35:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Utpal Vaishnav</title>
		<link>http://utpal.net/blog/2009/08/19/30-random-things-about-software-project-estimates/comment-page-1/#comment-270</link>
		<dc:creator>Utpal Vaishnav</dc:creator>
		<pubDate>Tue, 25 Aug 2009 19:09:42 +0000</pubDate>
		<guid isPermaLink="false">http://utpal.net/blog/?p=469#comment-270</guid>
		<description>Thanks for the addition Tanmay.

I believe whether we should factor Inefficiency or not is a debatable point. 

While I totally agree that factoring inefficiencies is a huge waste, I think we should rationalize and allowed to be considered it in certain kind of engagements in some cases. 

For example software companies that operates in non-metro cities of India who offer comparatively cheap rates. They usually estimate almost all the projects considering their people&#039;s capabilities and if the estimate (which is influenced by their people&#039;s inefficiencies) is acceptable to the other party, which means cheap rates with less efficient people,  the battle begins. 

If organizations take a call in such situations and play to their people&#039;s strengths, nobody can resist them to be successful.

Cheers!
Utpal</description>
		<content:encoded><![CDATA[<p>Thanks for the addition Tanmay.</p>
<p>I believe whether we should factor Inefficiency or not is a debatable point. </p>
<p>While I totally agree that factoring inefficiencies is a huge waste, I think we should rationalize and allowed to be considered it in certain kind of engagements in some cases. </p>
<p>For example software companies that operates in non-metro cities of India who offer comparatively cheap rates. They usually estimate almost all the projects considering their people&#8217;s capabilities and if the estimate (which is influenced by their people&#8217;s inefficiencies) is acceptable to the other party, which means cheap rates with less efficient people,  the battle begins. </p>
<p>If organizations take a call in such situations and play to their people&#8217;s strengths, nobody can resist them to be successful.</p>
<p>Cheers!<br />
Utpal</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tanmay Vora</title>
		<link>http://utpal.net/blog/2009/08/19/30-random-things-about-software-project-estimates/comment-page-1/#comment-267</link>
		<dc:creator>Tanmay Vora</dc:creator>
		<pubDate>Fri, 21 Aug 2009 13:47:20 +0000</pubDate>
		<guid isPermaLink="false">http://utpal.net/blog/?p=469#comment-267</guid>
		<description>Great List - I have one addition though:

Don&#039;t factor inefficiency of your team in estimation. People who estimate tend to look around for people who might work on this project and also try to factor their inefficiencies into the estimate. That is a huge waste.

Estimates are always based on efficiency (strength) of your resources and not on inefficiencies (weakness). Play to their strengths!

Cheers!

Tanmay</description>
		<content:encoded><![CDATA[<p>Great List &#8211; I have one addition though:</p>
<p>Don&#8217;t factor inefficiency of your team in estimation. People who estimate tend to look around for people who might work on this project and also try to factor their inefficiencies into the estimate. That is a huge waste.</p>
<p>Estimates are always based on efficiency (strength) of your resources and not on inefficiencies (weakness). Play to their strengths!</p>
<p>Cheers!</p>
<p>Tanmay</p>
]]></content:encoded>
	</item>
</channel>
</rss>
