<?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:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for </title>
	<atom:link href="http://agilefaq.net/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://agilefaq.net</link>
	<description>Facts From The Trenches</description>
	<lastBuildDate>Mon, 23 Mar 2009 20:45:22 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on What is a story point ? by Jacob Karma</title>
		<link>http://agilefaq.net/2007/11/13/what-is-a-story-point/#comment-117</link>
		<dc:creator>Jacob Karma</dc:creator>
		<pubDate>Mon, 23 Mar 2009 20:45:22 +0000</pubDate>
		<guid isPermaLink="false">http://agilefaq.wordpress.com/2007/11/13/what-is-a-story-point/#comment-117</guid>
		<description>Hi, I just wanted to mention that we have never used story points - and I still don&#039;t see the value of them. Your post does a good job of explaining what they are, and thank you - but I would love to hear your thoughts on what the whole &#039;point&#039; is.</description>
		<content:encoded><![CDATA[<p>Hi, I just wanted to mention that we have never used story points &#8211; and I still don&#8217;t see the value of them. Your post does a good job of explaining what they are, and thank you &#8211; but I would love to hear your thoughts on what the whole &#8216;point&#8217; is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on About by GettingAgile.com &#187; Blog Archive &#187; What is a team ground rule or team working agreement</title>
		<link>http://agilefaq.net/about/#comment-103</link>
		<dc:creator>GettingAgile.com &#187; Blog Archive &#187; What is a team ground rule or team working agreement</dc:creator>
		<pubDate>Fri, 02 Jan 2009 23:49:15 +0000</pubDate>
		<guid isPermaLink="false">http://agilefaq.net/test/#comment-103</guid>
		<description>[...] Agile FAQ has provided some information on what team working agreements and ground rules are in this [...]</description>
		<content:encoded><![CDATA[<p>[...] Agile FAQ has provided some information on what team working agreements and ground rules are in this [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What is a story point ? by editor</title>
		<link>http://agilefaq.net/2007/11/13/what-is-a-story-point/#comment-102</link>
		<dc:creator>editor</dc:creator>
		<pubDate>Sun, 14 Dec 2008 16:53:43 +0000</pubDate>
		<guid isPermaLink="false">http://agilefaq.wordpress.com/2007/11/13/what-is-a-story-point/#comment-102</guid>
		<description>Ian, 

Story points are very useful way to estimate at a gross level / release level. Most useful at a release planning level. In a sprint planning I use it as a tool that can make the planning process efficient. 

After the capacity plan is done, the team has an idea. I generally ask the team to pick the first few prioritized stories and size them quickly. This starts a communication in sprint planning between the scrum team and product owner. I think this is the biggest benefit i get out of using story points and sizing. 

Instead of this if we use time, the conversation take a different turn. I think in the end it does not matter if a small take 40 hours or a large takes 30 hours. What matters is team used the card and conversation to build  software in the two or three weeks and delivers value to the product owner.</description>
		<content:encoded><![CDATA[<p>Ian, </p>
<p>Story points are very useful way to estimate at a gross level / release level. Most useful at a release planning level. In a sprint planning I use it as a tool that can make the planning process efficient. </p>
<p>After the capacity plan is done, the team has an idea. I generally ask the team to pick the first few prioritized stories and size them quickly. This starts a communication in sprint planning between the scrum team and product owner. I think this is the biggest benefit i get out of using story points and sizing. </p>
<p>Instead of this if we use time, the conversation take a different turn. I think in the end it does not matter if a small take 40 hours or a large takes 30 hours. What matters is team used the card and conversation to build  software in the two or three weeks and delivers value to the product owner.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What is a story point ? by Ian Suttle</title>
		<link>http://agilefaq.net/2007/11/13/what-is-a-story-point/#comment-101</link>
		<dc:creator>Ian Suttle</dc:creator>
		<pubDate>Wed, 26 Nov 2008 18:15:09 +0000</pubDate>
		<guid isPermaLink="false">http://agilefaq.wordpress.com/2007/11/13/what-is-a-story-point/#comment-101</guid>
		<description>Thanks for the post.  While I agree calculating story points to hours is interesting it&#039;s also a bit inaccurate as story points are a relative means of estimating.  I might estimate something to be a 20 and it takes me 4 hours, and estimate another thing as an 8 and it takes me 6 hours.  28 total points / 10 hours = 2.8 hours / point using your formula.  If I apply that to just one story I&#039;m likely not accurate.  For instance, if I wanted to say I have a story which I estimate a 20 and believe I&#039;ll spend 2.8 hours / story point, I&#039;ll plan for this story to take 56 hours.  But in the example earlier it really took 4.  Why?  Because it&#039;s relative and by giving it a 20 I&#039;m saying either a) I don&#039;t know enough about the story to be more accurate, b) there&#039;s a lot of risk involved, or c) it&#039;s a lot of work.  Story points should really be used for longer term estimating (I believe Mike Cohn suggests the same) and not short term.  It&#039;s a trending tool of sorts.  If I really need to know how many hours or days something will take I&#039;ll break it down and try to get an estimate in hours or days for that task.  Let me know what you think about my &lt;a href=&quot;http://www.iansuttle.com/blog/post/Betting-on-Story-Points.aspx&quot; rel=&quot;nofollow&quot;&gt;post on story points&lt;/a&gt;.

Thanks again!
Ian</description>
		<content:encoded><![CDATA[<p>Thanks for the post.  While I agree calculating story points to hours is interesting it&#8217;s also a bit inaccurate as story points are a relative means of estimating.  I might estimate something to be a 20 and it takes me 4 hours, and estimate another thing as an 8 and it takes me 6 hours.  28 total points / 10 hours = 2.8 hours / point using your formula.  If I apply that to just one story I&#8217;m likely not accurate.  For instance, if I wanted to say I have a story which I estimate a 20 and believe I&#8217;ll spend 2.8 hours / story point, I&#8217;ll plan for this story to take 56 hours.  But in the example earlier it really took 4.  Why?  Because it&#8217;s relative and by giving it a 20 I&#8217;m saying either a) I don&#8217;t know enough about the story to be more accurate, b) there&#8217;s a lot of risk involved, or c) it&#8217;s a lot of work.  Story points should really be used for longer term estimating (I believe Mike Cohn suggests the same) and not short term.  It&#8217;s a trending tool of sorts.  If I really need to know how many hours or days something will take I&#8217;ll break it down and try to get an estimate in hours or days for that task.  Let me know what you think about my <a href="http://www.iansuttle.com/blog/post/Betting-on-Story-Points.aspx" rel="nofollow">post on story points</a>.</p>
<p>Thanks again!<br />
Ian</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What is a story point ? by Bhavin H. Joshi</title>
		<link>http://agilefaq.net/2007/11/13/what-is-a-story-point/#comment-98</link>
		<dc:creator>Bhavin H. Joshi</dc:creator>
		<pubDate>Wed, 19 Nov 2008 06:31:58 +0000</pubDate>
		<guid isPermaLink="false">http://agilefaq.wordpress.com/2007/11/13/what-is-a-story-point/#comment-98</guid>
		<description>Hummm...
Quite interesting!
I&#039;ll calculate the hours per story point for my team.</description>
		<content:encoded><![CDATA[<p>Hummm&#8230;<br />
Quite interesting!<br />
I&#8217;ll calculate the hours per story point for my team.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What is a story point ? by Federico</title>
		<link>http://agilefaq.net/2007/11/13/what-is-a-story-point/#comment-90</link>
		<dc:creator>Federico</dc:creator>
		<pubDate>Tue, 23 Sep 2008 09:13:44 +0000</pubDate>
		<guid isPermaLink="false">http://agilefaq.wordpress.com/2007/11/13/what-is-a-story-point/#comment-90</guid>
		<description>8 working hours? They don&#039;t eat, talk, think? Auch...</description>
		<content:encoded><![CDATA[<p>8 working hours? They don&#8217;t eat, talk, think? Auch&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What is a story point ? by Joe</title>
		<link>http://agilefaq.net/2007/11/13/what-is-a-story-point/#comment-65</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Mon, 02 Jun 2008 17:27:54 +0000</pubDate>
		<guid isPermaLink="false">http://agilefaq.wordpress.com/2007/11/13/what-is-a-story-point/#comment-65</guid>
		<description>Nice description of the story point...my team just started using SCRUM to manage our new product line and this post has really helped.  Thanks!</description>
		<content:encoded><![CDATA[<p>Nice description of the story point&#8230;my team just started using SCRUM to manage our new product line and this post has really helped.  Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What is Moscow Rule In Scrum? by editor</title>
		<link>http://agilefaq.net/2007/11/29/what-is-moscow-rule-in-scrum/#comment-39</link>
		<dc:creator>editor</dc:creator>
		<pubDate>Thu, 03 Jan 2008 05:45:59 +0000</pubDate>
		<guid isPermaLink="false">http://agilefaq.net/2007/11/29/what-is-moscow-rule-in-scrum/#comment-39</guid>
		<description>This is a rule that gets mention in many books. Check out Agile retrospectives by Diana Larson</description>
		<content:encoded><![CDATA[<p>This is a rule that gets mention in many books. Check out Agile retrospectives by Diana Larson</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What is Moscow Rule In Scrum? by PhilippeAntras</title>
		<link>http://agilefaq.net/2007/11/29/what-is-moscow-rule-in-scrum/#comment-38</link>
		<dc:creator>PhilippeAntras</dc:creator>
		<pubDate>Wed, 02 Jan 2008 20:45:17 +0000</pubDate>
		<guid isPermaLink="false">http://agilefaq.net/2007/11/29/what-is-moscow-rule-in-scrum/#comment-38</guid>
		<description>Hello again Vibhu,

This is really an interesting rule, where does it comes from ?

Thanks for sharing,
Philippe</description>
		<content:encoded><![CDATA[<p>Hello again Vibhu,</p>
<p>This is really an interesting rule, where does it comes from ?</p>
<p>Thanks for sharing,<br />
Philippe</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What is Kiss Principle by PhilippeAntras</title>
		<link>http://agilefaq.net/2007/11/03/what-is-kiss-principle/#comment-37</link>
		<dc:creator>PhilippeAntras</dc:creator>
		<pubDate>Wed, 02 Jan 2008 20:40:07 +0000</pubDate>
		<guid isPermaLink="false">http://agilefaq.wordpress.com/2007/11/03/what-is-kiss-principle/#comment-37</guid>
		<description>Hello,

The KISS principle is mentionned in Eric Raymond, New Hacker dictionary and therefore predates agile. 
See http://www.ccil.org/jargon/jargon_26.html#SEC33

The corresponding XP practice is Simple design. 

Cheers,
Philippe</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>The KISS principle is mentionned in Eric Raymond, New Hacker dictionary and therefore predates agile.<br />
See <a href="http://www.ccil.org/jargon/jargon_26.html#SEC33" rel="nofollow">http://www.ccil.org/jargon/jargon_26.html#SEC33</a></p>
<p>The corresponding XP practice is Simple design. </p>
<p>Cheers,<br />
Philippe</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What is a story point ? by Himath</title>
		<link>http://agilefaq.net/2007/11/13/what-is-a-story-point/#comment-3</link>
		<dc:creator>Himath</dc:creator>
		<pubDate>Sat, 24 Nov 2007 20:28:53 +0000</pubDate>
		<guid isPermaLink="false">http://agilefaq.wordpress.com/2007/11/13/what-is-a-story-point/#comment-3</guid>
		<description>One issue I&#039;ve encountered in using hours as a measure of effort is, it can be very subjective when using for estimates. In Extreme Programming (XP), developers need to estimate the effort for the stories. The effort in hours could vary from developer to developer. We could attempt to overcome this issue by using story points which can be used as a relative measure between stories. After a few iterations, it would be possible to calculate the equivalent effort in hours per story point.</description>
		<content:encoded><![CDATA[<p>One issue I&#8217;ve encountered in using hours as a measure of effort is, it can be very subjective when using for estimates. In Extreme Programming (XP), developers need to estimate the effort for the stories. The effort in hours could vary from developer to developer. We could attempt to overcome this issue by using story points which can be used as a relative measure between stories. After a few iterations, it would be possible to calculate the equivalent effort in hours per story point.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
