<?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: Focussing Your Goals</title>
	<atom:link href="http://edgehopper.com/focussing-your-goals/feed/" rel="self" type="application/rss+xml" />
	<link>http://edgehopper.com/focussing-your-goals/</link>
	<description>Tales from the Edge of Technology</description>
	<lastBuildDate>Mon, 26 Jul 2010 17:50:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Keith Sterling</title>
		<link>http://edgehopper.com/focussing-your-goals/comment-page-1/#comment-150</link>
		<dc:creator>Keith Sterling</dc:creator>
		<pubDate>Mon, 27 Oct 2008 15:46:14 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/focussing-your-goals/#comment-150</guid>
		<description>Interesting article, but I&#039;m struggling to see how this aligns with a strong product backlog, and an active customer who is prioritising and ordering the backlog ahead of the next iteration.

Teams struggling to plan the next release or iteration point towards a smell of a poor on none engaged customer and poor back log management.

Don&#039;t get me wrong there is definately a need to brainstorm each iteration, discuss those niggly little problems and tech debt that people think need to be brought up, so I would keep everything in the article but reword/rewrite Brainstorm section and place greater emphasis on getting together with the customer, reviewing the current backlog and agreeing the priority and using this to create a list of what things that need to be accomplished</description>
		<content:encoded><![CDATA[<p>Interesting article, but I&#8217;m struggling to see how this aligns with a strong product backlog, and an active customer who is prioritising and ordering the backlog ahead of the next iteration.</p>
<p>Teams struggling to plan the next release or iteration point towards a smell of a poor on none engaged customer and poor back log management.</p>
<p>Don&#8217;t get me wrong there is definately a need to brainstorm each iteration, discuss those niggly little problems and tech debt that people think need to be brought up, so I would keep everything in the article but reword/rewrite Brainstorm section and place greater emphasis on getting together with the customer, reviewing the current backlog and agreeing the priority and using this to create a list of what things that need to be accomplished</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Venu Tadepalli</title>
		<link>http://edgehopper.com/focussing-your-goals/comment-page-1/#comment-149</link>
		<dc:creator>Venu Tadepalli</dc:creator>
		<pubDate>Mon, 27 Oct 2008 15:39:02 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/focussing-your-goals/#comment-149</guid>
		<description>Excellent points. Any suggested materials on how to converge on goal</description>
		<content:encoded><![CDATA[<p>Excellent points. Any suggested materials on how to converge on goal</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://edgehopper.com/focussing-your-goals/comment-page-1/#comment-142</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Sat, 25 Oct 2008 03:30:26 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/focussing-your-goals/#comment-142</guid>
		<description>@ Larry: There are several ways this can be done using some of the tools I mentioned in a previous post on Tools for Distributed Teams. Check out the post here:  http://edgehopper.com/tools-for-distributed-teams/  . If you still have questions, let me know I can give more suggestions.  

@Carlos: Thanks.  Glad you enjoyed it.  Let me know how it works out for your team.</description>
		<content:encoded><![CDATA[<p>@ Larry: There are several ways this can be done using some of the tools I mentioned in a previous post on Tools for Distributed Teams. Check out the post here:  <a href="http://edgehopper.com/tools-for-distributed-teams/" rel="nofollow">http://edgehopper.com/tools-for-distributed-teams/</a>  . If you still have questions, let me know I can give more suggestions.  </p>
<p>@Carlos: Thanks.  Glad you enjoyed it.  Let me know how it works out for your team.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Larry Freedman</title>
		<link>http://edgehopper.com/focussing-your-goals/comment-page-1/#comment-139</link>
		<dc:creator>Larry Freedman</dc:creator>
		<pubDate>Fri, 24 Oct 2008 22:28:15 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/focussing-your-goals/#comment-139</guid>
		<description>How would you adjust modify this if your team was distributed geographically and all but a few were not able to see your visual cues?</description>
		<content:encoded><![CDATA[<p>How would you adjust modify this if your team was distributed geographically and all but a few were not able to see your visual cues?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carlos Roldan</title>
		<link>http://edgehopper.com/focussing-your-goals/comment-page-1/#comment-138</link>
		<dc:creator>Carlos Roldan</dc:creator>
		<pubDate>Fri, 24 Oct 2008 20:59:43 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/focussing-your-goals/#comment-138</guid>
		<description>Great post Chris! I am going to try this with my team and report back.
Carlos</description>
		<content:encoded><![CDATA[<p>Great post Chris! I am going to try this with my team and report back.<br />
Carlos</p>
]]></content:encoded>
	</item>
</channel>
</rss>
