<?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: Focus on Team Communication</title>
	<atom:link href="http://www.gettingagile.com/2010/02/03/focus-on-team-communication/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gettingagile.com/2010/02/03/focus-on-team-communication/</link>
	<description>with Sterling Barton</description>
	<lastBuildDate>Sun, 04 Jul 2010 16:55:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ranata</title>
		<link>http://www.gettingagile.com/2010/02/03/focus-on-team-communication/comment-page-1/#comment-1200</link>
		<dc:creator>Ranata</dc:creator>
		<pubDate>Mon, 05 Apr 2010 19:18:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.gettingagile.com/?p=368#comment-1200</guid>
		<description>I find with my team that they really want to associated the &quot;size&quot; with &quot;task estimation&quot;.  They can&#039;t seem to get past that at times.  I like the information you&#039;ve posted, it wraps it up nice and neat and serves as a good reminder.  Communication is the key aspect to all the planning that we are doing.  Great post!</description>
		<content:encoded><![CDATA[<p>I find with my team that they really want to associated the &#8220;size&#8221; with &#8220;task estimation&#8221;.  They can&#8217;t seem to get past that at times.  I like the information you&#8217;ve posted, it wraps it up nice and neat and serves as a good reminder.  Communication is the key aspect to all the planning that we are doing.  Great post!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Katie</title>
		<link>http://www.gettingagile.com/2010/02/03/focus-on-team-communication/comment-page-1/#comment-973</link>
		<dc:creator>Katie</dc:creator>
		<pubDate>Fri, 19 Feb 2010 16:23:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.gettingagile.com/?p=368#comment-973</guid>
		<description>Great post! Such a great post it is now the featured blog post on www.agileshout.com. I was not familiar with Planning Poker until you described it. Is there anything similar for requirements planning?</description>
		<content:encoded><![CDATA[<p>Great post! Such a great post it is now the featured blog post on <a href="http://www.agileshout.com" rel="nofollow">http://www.agileshout.com</a>. I was not familiar with Planning Poker until you described it. Is there anything similar for requirements planning?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Koontz</title>
		<link>http://www.gettingagile.com/2010/02/03/focus-on-team-communication/comment-page-1/#comment-930</link>
		<dc:creator>David Koontz</dc:creator>
		<pubDate>Thu, 04 Feb 2010 18:20:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.gettingagile.com/?p=368#comment-930</guid>
		<description>Nice explanation of why these two practices (team estimation of stories &amp; team tasking of stories) are vital to well functioning teams.  It is not so much the paper artifact product of the activity that is important, it is the shared understanding arrived at by true communication and consensus on a plan of action and the effort that should be required.

One trick Pete T. taught me was to change the terminology to change the attitude.  He called the sessions for estimation a &quot;sizing meeting&quot;.  Explained why, as you have, but also changed the label to ingrain what was to happen.  Estimation is so tied up in the concept of time or money - breaking away from those connotation is powerful.</description>
		<content:encoded><![CDATA[<p>Nice explanation of why these two practices (team estimation of stories &amp; team tasking of stories) are vital to well functioning teams.  It is not so much the paper artifact product of the activity that is important, it is the shared understanding arrived at by true communication and consensus on a plan of action and the effort that should be required.</p>
<p>One trick Pete T. taught me was to change the terminology to change the attitude.  He called the sessions for estimation a &#8220;sizing meeting&#8221;.  Explained why, as you have, but also changed the label to ingrain what was to happen.  Estimation is so tied up in the concept of time or money &#8211; breaking away from those connotation is powerful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Dempsey</title>
		<link>http://www.gettingagile.com/2010/02/03/focus-on-team-communication/comment-page-1/#comment-928</link>
		<dc:creator>Robert Dempsey</dc:creator>
		<pubDate>Thu, 04 Feb 2010 16:24:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.gettingagile.com/?p=368#comment-928</guid>
		<description>Great post Sterling, and I fully agree that every team really needs to focus on communication, especially in planning. One of the jobs of the ScrumMaster is to moderate these meetings so that each member of the team can be heard, and that some of the team&#039;s assumptions can be challenged. Other than that, it&#039;s up to the team to map out what they feel is the best course of action, as ultimately the responsibility to deliver is on their shoulders.</description>
		<content:encoded><![CDATA[<p>Great post Sterling, and I fully agree that every team really needs to focus on communication, especially in planning. One of the jobs of the ScrumMaster is to moderate these meetings so that each member of the team can be heard, and that some of the team&#8217;s assumptions can be challenged. Other than that, it&#8217;s up to the team to map out what they feel is the best course of action, as ultimately the responsibility to deliver is on their shoulders.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
