<?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: Scrum &#8211; More details about the Planning Poker process</title>
	<atom:link href="http://learnsoftwareprocesses.com/2010/02/06/scrum-more-details-about-the-planning-poker-process/feed/" rel="self" type="application/rss+xml" />
	<link>http://learnsoftwareprocesses.com/2010/02/06/scrum-more-details-about-the-planning-poker-process/</link>
	<description>All about the processes involved in software development</description>
	<lastBuildDate>Fri, 24 Feb 2012 10:21:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: James Grenning</title>
		<link>http://learnsoftwareprocesses.com/2010/02/06/scrum-more-details-about-the-planning-poker-process/comment-page-1/#comment-5721</link>
		<dc:creator>James Grenning</dc:creator>
		<pubDate>Sun, 28 Feb 2010 17:52:11 +0000</pubDate>
		<guid isPermaLink="false">http://learnsoftwareprocesses.com/?p=519#comment-5721</guid>
		<description>Generally a team will converge on an estimate.  If all provide the same estimate, move to the next story without discussion.  If numbers are not the same, have the high tell why it is hard, the low tell why it is easy and play a new card.  This usually leads to better understanding of the story or of how to implement the story. If you cannot converge, maybe put the story aside for discussion later.

I suggest not getting hung up on the rules and do something that keeps the process moving.</description>
		<content:encoded><![CDATA[<p>Generally a team will converge on an estimate.  If all provide the same estimate, move to the next story without discussion.  If numbers are not the same, have the high tell why it is hard, the low tell why it is easy and play a new card.  This usually leads to better understanding of the story or of how to implement the story. If you cannot converge, maybe put the story aside for discussion later.</p>
<p>I suggest not getting hung up on the rules and do something that keeps the process moving.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steps to optimize Scrum Planning Poker estimation process &#124; Learn Software Development</title>
		<link>http://learnsoftwareprocesses.com/2010/02/06/scrum-more-details-about-the-planning-poker-process/comment-page-1/#comment-5719</link>
		<dc:creator>Steps to optimize Scrum Planning Poker estimation process &#124; Learn Software Development</dc:creator>
		<pubDate>Sun, 28 Feb 2010 07:26:18 +0000</pubDate>
		<guid isPermaLink="false">http://learnsoftwareprocesses.com/?p=519#comment-5719</guid>
		<description>[...] previous posts (Details about Planning Poker process), I have explained the process of Planning Poker as a part of how to do estimation of tasks during [...]</description>
		<content:encoded><![CDATA[<p>[...] previous posts (Details about Planning Poker process), I have explained the process of Planning Poker as a part of how to do estimation of tasks during [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

