<?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: Poker Playing for Software Development Projects</title>
	<atom:link href="http://www.innovationontherun.com/poker-playing-for-software-development-projects/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.innovationontherun.com/poker-playing-for-software-development-projects/</link>
	<description>Ruminations about innovation and software by Rob Di Marco</description>
	<lastBuildDate>Tue, 06 Apr 2010 15:52:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: tim</title>
		<link>http://www.innovationontherun.com/poker-playing-for-software-development-projects/comment-page-1/#comment-15</link>
		<dc:creator>tim</dc:creator>
		<pubDate>Tue, 31 Jul 2007 19:42:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.innovationontherun.com/poker-playing-for-software-development-projects/#comment-15</guid>
		<description>Some developers are pretty good at estimating.  Others are pretty horrible.  What&#039;s kind of sad is that, for whatever reason, it&#039;s really really hard to teach those who are bad at it to get better.

I&#039;ve also worked with some &quot;problem child&quot; developers, who simply refuse to estimate at all.  When pressed, they just say &quot;2 weeks&quot;, but you know it&#039;s BS, and you know they just don&#039;t care.

We actually have used a simple version of planning poker on my team at Yahoo, and have found that it did improve our estimates, and the team liked it pretty well. :)  It helps for the same reason that code reviews help; the collective works better/smarter than the individual.  If it doesn&#039;t, you should fix that problem before you worry about anything else. :)</description>
		<content:encoded><![CDATA[<p>Some developers are pretty good at estimating.  Others are pretty horrible.  What&#8217;s kind of sad is that, for whatever reason, it&#8217;s really really hard to teach those who are bad at it to get better.</p>
<p>I&#8217;ve also worked with some &#8220;problem child&#8221; developers, who simply refuse to estimate at all.  When pressed, they just say &#8220;2 weeks&#8221;, but you know it&#8217;s BS, and you know they just don&#8217;t care.</p>
<p>We actually have used a simple version of planning poker on my team at Yahoo, and have found that it did improve our estimates, and the team liked it pretty well. <img src='http://www.innovationontherun.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />   It helps for the same reason that code reviews help; the collective works better/smarter than the individual.  If it doesn&#8217;t, you should fix that problem before you worry about anything else. <img src='http://www.innovationontherun.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
