<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Mike Cohn&#039;s Blog - Succeeding With Agile® &#187; planning poker</title>
	<atom:link href="http://blog.mountaingoatsoftware.com/tag/planning-poker/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.mountaingoatsoftware.com</link>
	<description>Succeeding With Agile®</description>
	<lastBuildDate>Mon, 06 Feb 2012 18:11:05 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>New Planning Poker Card Design</title>
		<link>http://blog.mountaingoatsoftware.com/new-planning-poker-card-design</link>
		<comments>http://blog.mountaingoatsoftware.com/new-planning-poker-card-design#comments</comments>
		<pubDate>Sun, 04 Dec 2011 15:01:28 +0000</pubDate>
		<dc:creator>Mike Cohn</dc:creator>
				<category><![CDATA[Agile Estimating]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[planning poker]]></category>

		<guid isPermaLink="false">http://blog.mountaingoatsoftware.com/?p=1206</guid>
		<description><![CDATA[I&#8217;ve wanted to update the design of our Planning Poker cards for quite awhile, and we finally got the chance. The new cards feature an all-new back design to go along with the same faces we&#8217;ve used for years. There are 56 cards in the deck. Thirteen estimating numbers are provided in four colors, each [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://blog.mountaingoatsoftware.com/wp-content/uploads/front-back-blue.png"><img src="http://blog.mountaingoatsoftware.com/wp-content/uploads/front-back-blue.png" alt="Blue Planning Poker Cards" title="Blue Planning Poker Cards" width="500" height="442" class="alignright size-full wp-image-1207" /></a></p>
<p>I&#8217;ve wanted to update the design of our Planning Poker cards for quite awhile, and we finally got the chance. The new cards feature an all-new back design to go along with the same faces we&#8217;ve used for years. </p>
<p>There are 56 cards in the deck. Thirteen estimating numbers are provided in four colors, each with a matching back as shown above. Additional cards include instructions on how to estimate with Planning Poker and feature full-color photos of goats on the back. </p>
<p>The cards are still the same high quality we&#8217;ve always provided. Our cards are manufactured by the same company that provides cards for Caesar&#8217;s Palace and other leading casinos. The cards come boxed as before although we&#8217;ve updated the art on the box cover&#8211;check out the leap of that goat!</p>
<p>Cards are <a href="http://store.mountaingoatsoftware.com/" title="the Mountain Goat Software store">for sale on our store</a>. We will continue to sell our branded cards (like these) at our cost of $2.50 per deck. We also have unbranded cards for sale if you don&#8217;t want to see any goats anywhere. And we will continue to sell cards with the traditional goat photo backs as long as our inventory lasts.</p>
<p>Let me know what you think of the new design in the comments below.</p>
<p><a href="http://blog.mountaingoatsoftware.com/wp-content/uploads/Fan.png"><img src="http://blog.mountaingoatsoftware.com/wp-content/uploads/Fan.png" alt="Fan of Planning Poker Cards" title="Fan of Planning Poker Cards" width="670" height="420" class="alignright size-full wp-image-1210" /></a></p>
<p><a href="http://blog.mountaingoatsoftware.com/wp-content/uploads/3d-Box.png"><img src="http://blog.mountaingoatsoftware.com/wp-content/uploads/3d-Box.png" alt="Planning Poker Card box" title="Planning Poker Card box" width="435" height="390" class="alignright size-full wp-image-1212" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.mountaingoatsoftware.com/new-planning-poker-card-design/feed</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Don&#8217;t Average During Planning Poker</title>
		<link>http://blog.mountaingoatsoftware.com/dont-average-during-planning-poker</link>
		<comments>http://blog.mountaingoatsoftware.com/dont-average-during-planning-poker#comments</comments>
		<pubDate>Thu, 11 Oct 2007 19:03:32 +0000</pubDate>
		<dc:creator>Mike Cohn</dc:creator>
				<category><![CDATA[Agile Estimating]]></category>
		<category><![CDATA[agile estimation]]></category>
		<category><![CDATA[planning poker]]></category>

		<guid isPermaLink="false">http://blog.mountaingoatsoftware.com/?p=14</guid>
		<description><![CDATA[I like to use Planning Poker to estimate the user stories on an agile team&#8217;s product backlog. In this approach individual estimators hold up cards showing their estimates. If estimators disagree they discuss why, ask questions of their product owner (who should be present), and repeat until they come to consensus. Team members often ask [...]]]></description>
			<content:encoded><![CDATA[<p>I like to use Planning Poker to estimate the user stories on an agile team&#8217;s product backlog. In this approach individual estimators hold up cards showing their estimates. If estimators disagree they discuss why, ask questions of their product owner (who should be present), and repeat until they come to consensus. Team members often ask me whether they really need to come to consensus orÂ  whether they can just take the mean of the individual estimates.<br />
The problem with averaging is that it is too easy&#8211;rather than have the fierce discussion that is one of the huge benefits of playing Planning Poker teams fall into a trap of playing one or two rounds and then just averaging. An obvious dysfunction is that one estimator may play the 100 card not because he thinks it will take that long but because he thinks 20 is the right number and other estimators are thinking 8 and 13. For this reason and others, if a team truly feels compelled to average, they should take the median (middle value) rather than the mean (sum of estimates divided by number of estimates).</p>
<p>A lot of dark corners are enlightened through the discussion; teams lose out on that when they average. So while I want teams to come to agreement, I don&#8217;t care how heartfelt the agreement is. If we agree on 13 some of us may really believe that&#8217;s the right number. Others may think 8 is right but that 13 is &#8220;close enough.&#8221; Still others may think we&#8217;ve discussed the item too long and even though it should be a 20 will give in and call it a 13 just to be done with it.</p>
<p>So, rather than average if the team is an impasse I suggest going another round. If still stuck, someone should suggest a reasonable number and see if everyone can &#8220;support it&#8221; rather than &#8220;think it&#8217;s the absolutely perfect number.&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.mountaingoatsoftware.com/dont-average-during-planning-poker/feed</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
	</channel>
</rss>

