<?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: Agile estimation &#8211; story points vs. hours</title>
	<atom:link href="http://epistemologic.com/2006/10/25/agile-estimation-story-points-vs-hours/feed/" rel="self" type="application/rss+xml" />
	<link>http://epistemologic.com/2006/10/25/agile-estimation-story-points-vs-hours/</link>
	<description>Amit Rathore's blog about software project management</description>
	<lastBuildDate>Thu, 24 Nov 2011 09:34:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Geoff Corey</title>
		<link>http://epistemologic.com/2006/10/25/agile-estimation-story-points-vs-hours/#comment-8251</link>
		<dc:creator><![CDATA[Geoff Corey]]></dc:creator>
		<pubDate>Tue, 11 Jan 2011 19:51:26 +0000</pubDate>
		<guid isPermaLink="false">http://epistemologic.wordpress.com/2006/10/25/agile-estimation-story-points-vs-hours/#comment-8251</guid>
		<description><![CDATA[It is amazing how this issue won&#039;t die.  Long thread on LinkedIn group arguing this very point.  Prompting me to write a similar article with more detail on how to do story point estimates and iteration/release planning.

I love the formula and may add that to the article.  I will fully cite your article of course! 

Good work!]]></description>
		<content:encoded><![CDATA[<p>It is amazing how this issue won&#8217;t die.  Long thread on LinkedIn group arguing this very point.  Prompting me to write a similar article with more detail on how to do story point estimates and iteration/release planning.</p>
<p>I love the formula and may add that to the article.  I will fully cite your article of course! </p>
<p>Good work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Riel</title>
		<link>http://epistemologic.com/2006/10/25/agile-estimation-story-points-vs-hours/#comment-8166</link>
		<dc:creator><![CDATA[Riel]]></dc:creator>
		<pubDate>Thu, 22 Jul 2010 16:56:35 +0000</pubDate>
		<guid isPermaLink="false">http://epistemologic.wordpress.com/2006/10/25/agile-estimation-story-points-vs-hours/#comment-8166</guid>
		<description><![CDATA[Can you explain why this statement is true?

&quot;the only thing that can be “estimated” here is C&quot;

To me it seems it would be even easier to estimate S and K (developer skill and domain knowledge).

I realize this does not change the wisdom of your post.

RIELmanriquez.com]]></description>
		<content:encoded><![CDATA[<p>Can you explain why this statement is true?</p>
<p>&#8220;the only thing that can be “estimated” here is C&#8221;</p>
<p>To me it seems it would be even easier to estimate S and K (developer skill and domain knowledge).</p>
<p>I realize this does not change the wisdom of your post.</p>
<p>RIELmanriquez.com</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sonali</title>
		<link>http://epistemologic.com/2006/10/25/agile-estimation-story-points-vs-hours/#comment-8137</link>
		<dc:creator><![CDATA[Sonali]]></dc:creator>
		<pubDate>Tue, 06 Apr 2010 13:26:00 +0000</pubDate>
		<guid isPermaLink="false">http://epistemologic.wordpress.com/2006/10/25/agile-estimation-story-points-vs-hours/#comment-8137</guid>
		<description><![CDATA[Very interesting post . This is the exactly same situation we are running into where team wants to do the estimate in hours as they feel this is what they can do best rather than estimating in story points which only factors the complexity &amp; not the time(hrs). And from their point of view how they should determine the complexity itself is not very clear so they feel reluctant about the story point estimates.
I must appreciate the formula that you have used to describe why use story points. Quite helpful.

http://twitter.com/sonalibhasin]]></description>
		<content:encoded><![CDATA[<p>Very interesting post . This is the exactly same situation we are running into where team wants to do the estimate in hours as they feel this is what they can do best rather than estimating in story points which only factors the complexity &amp; not the time(hrs). And from their point of view how they should determine the complexity itself is not very clear so they feel reluctant about the story point estimates.<br />
I must appreciate the formula that you have used to describe why use story points. Quite helpful.</p>
<p><a href="http://twitter.com/sonalibhasin" rel="nofollow">http://twitter.com/sonalibhasin</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

