<?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: How Do Story Points Relate to Hours?</title>
	<atom:link href="http://blog.mountaingoatsoftware.com/how-do-story-points-relate-to-hours/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.mountaingoatsoftware.com/how-do-story-points-relate-to-hours</link>
	<description>Succeeding With Agile®</description>
	<lastBuildDate>Fri, 10 Feb 2012 03:51:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Commenter</title>
		<link>http://blog.mountaingoatsoftware.com/how-do-story-points-relate-to-hours/comment-page-1#comment-272099</link>
		<dc:creator>Commenter</dc:creator>
		<pubDate>Thu, 29 Sep 2011 11:25:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mountaingoatsoftware.com/?p=81#comment-272099</guid>
		<description>Sorry, when I said task, I meant PBI. Didn&#039;t know task was a term used in Agile for something else.</description>
		<content:encoded><![CDATA[<p>Sorry, when I said task, I meant PBI. Didn&#8217;t know task was a term used in Agile for something else.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cohn</title>
		<link>http://blog.mountaingoatsoftware.com/how-do-story-points-relate-to-hours/comment-page-1#comment-272084</link>
		<dc:creator>Mike Cohn</dc:creator>
		<pubDate>Thu, 29 Sep 2011 10:54:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mountaingoatsoftware.com/?p=81#comment-272084</guid>
		<description>Hi Anonymous Commenter--
Teams don&#039;t estimate the number of story points in a task. They estimate story points in a story (or any product backlog item).</description>
		<content:encoded><![CDATA[<p>Hi Anonymous Commenter&#8211;<br />
Teams don&#8217;t estimate the number of story points in a task. They estimate story points in a story (or any product backlog item).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Commenter</title>
		<link>http://blog.mountaingoatsoftware.com/how-do-story-points-relate-to-hours/comment-page-1#comment-272045</link>
		<dc:creator>Commenter</dc:creator>
		<pubDate>Thu, 29 Sep 2011 09:16:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mountaingoatsoftware.com/?p=81#comment-272045</guid>
		<description>Well, I&#039;m none the wiser! When estimating the number of story points in a task, what do people do? Try and guess how many days the task will take, presumably, since duration is what matters when fitting things into an available duration. Then, when estimating how many hours it&#039;ll take, they have to have a notion of story-points per hour.

In fact they needed that notional value when guessing the story point figure.

Seems like there&#039;s a lot of tap-dancing around to avoid reality?</description>
		<content:encoded><![CDATA[<p>Well, I&#8217;m none the wiser! When estimating the number of story points in a task, what do people do? Try and guess how many days the task will take, presumably, since duration is what matters when fitting things into an available duration. Then, when estimating how many hours it&#8217;ll take, they have to have a notion of story-points per hour.</p>
<p>In fact they needed that notional value when guessing the story point figure.</p>
<p>Seems like there&#8217;s a lot of tap-dancing around to avoid reality?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dibby</title>
		<link>http://blog.mountaingoatsoftware.com/how-do-story-points-relate-to-hours/comment-page-1#comment-267336</link>
		<dc:creator>Dibby</dc:creator>
		<pubDate>Sun, 18 Sep 2011 13:57:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mountaingoatsoftware.com/?p=81#comment-267336</guid>
		<description>Really useful, I am  trying to convince my team points and time are different.</description>
		<content:encoded><![CDATA[<p>Really useful, I am  trying to convince my team points and time are different.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cohn</title>
		<link>http://blog.mountaingoatsoftware.com/how-do-story-points-relate-to-hours/comment-page-1#comment-255582</link>
		<dc:creator>Mike Cohn</dc:creator>
		<pubDate>Mon, 22 Aug 2011 02:25:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mountaingoatsoftware.com/?p=81#comment-255582</guid>
		<description>Hi Carolina--
I&#039;m glad you found this post helpful. Thanks for letting me know.</description>
		<content:encoded><![CDATA[<p>Hi Carolina&#8211;<br />
I&#8217;m glad you found this post helpful. Thanks for letting me know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carolina</title>
		<link>http://blog.mountaingoatsoftware.com/how-do-story-points-relate-to-hours/comment-page-1#comment-254771</link>
		<dc:creator>Carolina</dc:creator>
		<pubDate>Sat, 20 Aug 2011 15:17:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mountaingoatsoftware.com/?p=81#comment-254771</guid>
		<description>Thx for this article, it`s going to help me a lot. I have to explain to the business the relation between points and time, because they some times thing that those are the same. 

Thanks a lot!</description>
		<content:encoded><![CDATA[<p>Thx for this article, it`s going to help me a lot. I have to explain to the business the relation between points and time, because they some times thing that those are the same. </p>
<p>Thanks a lot!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cohn</title>
		<link>http://blog.mountaingoatsoftware.com/how-do-story-points-relate-to-hours/comment-page-1#comment-216695</link>
		<dc:creator>Mike Cohn</dc:creator>
		<pubDate>Mon, 06 Jun 2011 16:47:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mountaingoatsoftware.com/?p=81#comment-216695</guid>
		<description>Hi Fun--
Yes, I&#039;d seen that Agile Estimating and Planning did well in that book survey. I&#039;m quite proud (still) of that book. 

As you may have seen, there is a lot of discussion in the comments of &lt;a href=&quot;http://blog.mountaingoatsoftware.com/its-effort-not-complexity&quot; rel=&quot;nofollow&quot;&gt;&quot;It&#039;s Effort, Not Complexity&quot;&lt;/a&gt; about the fact that complexity can influence the estimate but only to the extent the complexity influences the effort involved.</description>
		<content:encoded><![CDATA[<p>Hi Fun&#8211;<br />
Yes, I&#8217;d seen that Agile Estimating and Planning did well in that book survey. I&#8217;m quite proud (still) of that book. </p>
<p>As you may have seen, there is a lot of discussion in the comments of <a href="http://blog.mountaingoatsoftware.com/its-effort-not-complexity" rel="nofollow">&#8220;It&#8217;s Effort, Not Complexity&#8221;</a> about the fact that complexity can influence the estimate but only to the extent the complexity influences the effort involved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fun Chiat</title>
		<link>http://blog.mountaingoatsoftware.com/how-do-story-points-relate-to-hours/comment-page-1#comment-216663</link>
		<dc:creator>Fun Chiat</dc:creator>
		<pubDate>Mon, 06 Jun 2011 15:16:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mountaingoatsoftware.com/?p=81#comment-216663</guid>
		<description>Did you know your book Agile Estimating and Planning is number 1:
http://www.noop.nl/2010/08/top-100-agile-books.html
When will we see Part 2?    :)

I love your other analogy on complexity. Licking 1000+ stamps and brain surgery may have same story points or effort but can we see the contrast in complexity?

While I like to describe points as size, I need to think in industry standard terms. I should use Effort and Duration.</description>
		<content:encoded><![CDATA[<p>Did you know your book Agile Estimating and Planning is number 1:<br />
<a href="http://www.noop.nl/2010/08/top-100-agile-books.html" rel="nofollow">http://www.noop.nl/2010/08/top-100-agile-books.html</a><br />
When will we see Part 2?    <img src='http://blog.mountaingoatsoftware.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>I love your other analogy on complexity. Licking 1000+ stamps and brain surgery may have same story points or effort but can we see the contrast in complexity?</p>
<p>While I like to describe points as size, I need to think in industry standard terms. I should use Effort and Duration.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cohn</title>
		<link>http://blog.mountaingoatsoftware.com/how-do-story-points-relate-to-hours/comment-page-1#comment-216354</link>
		<dc:creator>Mike Cohn</dc:creator>
		<pubDate>Sun, 05 Jun 2011 22:29:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mountaingoatsoftware.com/?p=81#comment-216354</guid>
		<description>Hi Fun--
I&#039;m glad you&#039;ve enjoyed the Agile Estimating and Planning book. Thanks for letting me know and hopefully sometime we can meet in person.

To use the two industry standard terms there are really two things we are interested in: Effort and Duration. We use story points as an estimate of Effort. You are right that a &quot;measure of size [effort] does not fluctuate.&quot; I use the example of moving a pile of rocks from one place to another. The effort of doing that (perhaps measured as kilograms moved x the distance moved) is the same whether I do it or my young daughter does it.  

What changes will be duration--if I do it the duration will be shorter than if my young daughter does it. The easiest way to think of calculating duration is as Effort (in Story Points) divided by Velocity (in Story Points). If we think of teams of one person, my velocity will be higher than my daughters so my duration is shorter.

So, I think the points you are making are valid except I&#039;d change &quot;effort&quot; in a few of your sentences to be duration. Think of duration as the amount of time elapsed on a clock or calendar. Your team on the road example fits when about duration.</description>
		<content:encoded><![CDATA[<p>Hi Fun&#8211;<br />
I&#8217;m glad you&#8217;ve enjoyed the Agile Estimating and Planning book. Thanks for letting me know and hopefully sometime we can meet in person.</p>
<p>To use the two industry standard terms there are really two things we are interested in: Effort and Duration. We use story points as an estimate of Effort. You are right that a &#8220;measure of size [effort] does not fluctuate.&#8221; I use the example of moving a pile of rocks from one place to another. The effort of doing that (perhaps measured as kilograms moved x the distance moved) is the same whether I do it or my young daughter does it.  </p>
<p>What changes will be duration&#8211;if I do it the duration will be shorter than if my young daughter does it. The easiest way to think of calculating duration is as Effort (in Story Points) divided by Velocity (in Story Points). If we think of teams of one person, my velocity will be higher than my daughters so my duration is shorter.</p>
<p>So, I think the points you are making are valid except I&#8217;d change &#8220;effort&#8221; in a few of your sentences to be duration. Think of duration as the amount of time elapsed on a clock or calendar. Your team on the road example fits when about duration.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fun Chiat</title>
		<link>http://blog.mountaingoatsoftware.com/how-do-story-points-relate-to-hours/comment-page-1#comment-214633</link>
		<dc:creator>Fun Chiat</dc:creator>
		<pubDate>Thu, 02 Jun 2011 15:44:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mountaingoatsoftware.com/?p=81#comment-214633</guid>
		<description>Hi Mike, I am fan of your book Agile Estimation and Planning. I do not have enough good karma of seeing in you person but I am happy to see you are responding to this topic as at May 28 2011. I live in Malaysia.

My mind is cracking under the ideas posted here and I find myself challenging personal assumptions. I have been assuming story points are pure relative size of backlog items one another. Only from a team, can we have and measure effort. Different circumstances require different effort. Storypoints which is a measure of size do not fluctuate.

Are there 2 separate principles here, one is size and the other is the effort?

Suppose a road is estimated 1 mile long. It may not be worth it but if we want exact accuracy we can measure it with long tape: say 1.2135 miles
However, the team who traverse this road may take different effort. Sometimes 20 minutes. They got thirsty, they stop by a restaurant, end up 25 minutes. Or they don&#039;t mind sweating and sprinting, it takes 10 minutes.

Is there a 3rd principle  cost, the need for a drink at restaurant, we didn&#039;t know there is a toll gate in addition to the effort?

So if we give just story point and effort principle a relationship, wouldn&#039;t it be velocity? Can help me check if my understanding is correct?</description>
		<content:encoded><![CDATA[<p>Hi Mike, I am fan of your book Agile Estimation and Planning. I do not have enough good karma of seeing in you person but I am happy to see you are responding to this topic as at May 28 2011. I live in Malaysia.</p>
<p>My mind is cracking under the ideas posted here and I find myself challenging personal assumptions. I have been assuming story points are pure relative size of backlog items one another. Only from a team, can we have and measure effort. Different circumstances require different effort. Storypoints which is a measure of size do not fluctuate.</p>
<p>Are there 2 separate principles here, one is size and the other is the effort?</p>
<p>Suppose a road is estimated 1 mile long. It may not be worth it but if we want exact accuracy we can measure it with long tape: say 1.2135 miles<br />
However, the team who traverse this road may take different effort. Sometimes 20 minutes. They got thirsty, they stop by a restaurant, end up 25 minutes. Or they don&#8217;t mind sweating and sprinting, it takes 10 minutes.</p>
<p>Is there a 3rd principle  cost, the need for a drink at restaurant, we didn&#8217;t know there is a toll gate in addition to the effort?</p>
<p>So if we give just story point and effort principle a relationship, wouldn&#8217;t it be velocity? Can help me check if my understanding is correct?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

