<?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: How We Do Things &#8211; Planning Part 2</title>
	<atom:link href="http://lostechies.com/scottreynolds/2009/10/06/how-we-do-things-planning-part-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://lostechies.com/scottreynolds/2009/10/06/how-we-do-things-planning-part-2/</link>
	<description>Just another LosTechies site</description>
	<lastBuildDate>Fri, 25 Mar 2011 10:26:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: www.lostechies.com</title>
		<link>http://lostechies.com/scottreynolds/2009/10/06/how-we-do-things-planning-part-2/#comment-189</link>
		<dc:creator>www.lostechies.com</dc:creator>
		<pubDate>Fri, 25 Mar 2011 10:26:03 +0000</pubDate>
		<guid isPermaLink="false">/blogs/scottcreynolds/archive/2009/10/06/how-we-do-things-planning-part-2.aspx#comment-189</guid>
		<description>How we do things planning part 2.. Awesome :)</description>
		<content:encoded><![CDATA[<p>How we do things planning part 2.. Awesome <img src='http://lostechies.com/scottreynolds/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott C Reynolds</title>
		<link>http://lostechies.com/scottreynolds/2009/10/06/how-we-do-things-planning-part-2/#comment-162</link>
		<dc:creator>Scott C Reynolds</dc:creator>
		<pubDate>Tue, 06 Oct 2009 17:05:11 +0000</pubDate>
		<guid isPermaLink="false">/blogs/scottcreynolds/archive/2009/10/06/how-we-do-things-planning-part-2.aspx#comment-162</guid>
		<description>@alberto sure, it&#039;s a matter of perspective. for us it&#039;s about reducing noise and extra movement. Things we know don&#039;t even need consideration for 6 months don&#039;t even enter our minds when we look at the backlog.</description>
		<content:encoded><![CDATA[<p>@alberto sure, it&#8217;s a matter of perspective. for us it&#8217;s about reducing noise and extra movement. Things we know don&#8217;t even need consideration for 6 months don&#8217;t even enter our minds when we look at the backlog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alberto</title>
		<link>http://lostechies.com/scottreynolds/2009/10/06/how-we-do-things-planning-part-2/#comment-161</link>
		<dc:creator>alberto</dc:creator>
		<pubDate>Tue, 06 Oct 2009 16:32:49 +0000</pubDate>
		<guid isPermaLink="false">/blogs/scottcreynolds/archive/2009/10/06/how-we-do-things-planning-part-2.aspx#comment-161</guid>
		<description>Well, when I said planned I was referring to things the client &quot;wanted to have&quot;, just as you called it the &quot;planning space-time continuum&quot;. They don&#039;t have to be planned in detail.

And yes, the backlog has to be prioritized, but IMHO it&#039;s no different from your different segments: high priorities first, low priorities last, and a continuum in the middle.</description>
		<content:encoded><![CDATA[<p>Well, when I said planned I was referring to things the client &#8220;wanted to have&#8221;, just as you called it the &#8220;planning space-time continuum&#8221;. They don&#8217;t have to be planned in detail.</p>
<p>And yes, the backlog has to be prioritized, but IMHO it&#8217;s no different from your different segments: high priorities first, low priorities last, and a continuum in the middle.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mob</title>
		<link>http://lostechies.com/scottreynolds/2009/10/06/how-we-do-things-planning-part-2/#comment-160</link>
		<dc:creator>mob</dc:creator>
		<pubDate>Tue, 06 Oct 2009 16:04:23 +0000</pubDate>
		<guid isPermaLink="false">/blogs/scottcreynolds/archive/2009/10/06/how-we-do-things-planning-part-2.aspx#comment-160</guid>
		<description>Nice series, thanks for sharing all of this.

BTW, I keep thinking that a midi of Montell Jordan&#039;s &quot;This is how we do it&quot; will start playing when I open these posts. :)</description>
		<content:encoded><![CDATA[<p>Nice series, thanks for sharing all of this.</p>
<p>BTW, I keep thinking that a midi of Montell Jordan&#8217;s &#8220;This is how we do it&#8221; will start playing when I open these posts. <img src='http://lostechies.com/scottreynolds/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott C Reynolds</title>
		<link>http://lostechies.com/scottreynolds/2009/10/06/how-we-do-things-planning-part-2/#comment-159</link>
		<dc:creator>Scott C Reynolds</dc:creator>
		<pubDate>Tue, 06 Oct 2009 15:32:25 +0000</pubDate>
		<guid isPermaLink="false">/blogs/scottcreynolds/archive/2009/10/06/how-we-do-things-planning-part-2.aspx#comment-159</guid>
		<description>@alberto

the roadmap and lie features are not &quot;planned&quot;. They just &quot;exist&quot;

What we found was that maintaining a single backlog for everything became noisy and involved a lot of wasted motion. Things far into the future detract from the signal of managing work coming up.

Additionally, and I could be wrong, but my understanding of the scrum backlog is that it is a prioritized backlog. Things far into the future here do not have priorities attached, further lessening the usefulness of keeping them in the same grouping as the rolling wave.

but again, this is just what I do.</description>
		<content:encoded><![CDATA[<p>@alberto</p>
<p>the roadmap and lie features are not &#8220;planned&#8221;. They just &#8220;exist&#8221;</p>
<p>What we found was that maintaining a single backlog for everything became noisy and involved a lot of wasted motion. Things far into the future detract from the signal of managing work coming up.</p>
<p>Additionally, and I could be wrong, but my understanding of the scrum backlog is that it is a prioritized backlog. Things far into the future here do not have priorities attached, further lessening the usefulness of keeping them in the same grouping as the rolling wave.</p>
<p>but again, this is just what I do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alberto</title>
		<link>http://lostechies.com/scottreynolds/2009/10/06/how-we-do-things-planning-part-2/#comment-158</link>
		<dc:creator>alberto</dc:creator>
		<pubDate>Tue, 06 Oct 2009 15:13:43 +0000</pubDate>
		<guid isPermaLink="false">/blogs/scottcreynolds/archive/2009/10/06/how-we-do-things-planning-part-2.aspx#comment-158</guid>
		<description>In Scrum, a product backlog can very well fit all your planned features, not only your rolling wave. Nothing in it says all stories in the product backlog have to be fine grained, so you can (and should) also add your roadmap and &quot;lie&quot; features in it.</description>
		<content:encoded><![CDATA[<p>In Scrum, a product backlog can very well fit all your planned features, not only your rolling wave. Nothing in it says all stories in the product backlog have to be fine grained, so you can (and should) also add your roadmap and &#8220;lie&#8221; features in it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mihai Lazar</title>
		<link>http://lostechies.com/scottreynolds/2009/10/06/how-we-do-things-planning-part-2/#comment-157</link>
		<dc:creator>Mihai Lazar</dc:creator>
		<pubDate>Tue, 06 Oct 2009 08:47:53 +0000</pubDate>
		<guid isPermaLink="false">/blogs/scottcreynolds/archive/2009/10/06/how-we-do-things-planning-part-2.aspx#comment-157</guid>
		<description>This is nice. Thanks for sharing. You&#039;ve given me something to think about, maybe the work process will stick with me, maybe not but it is something I found useful.</description>
		<content:encoded><![CDATA[<p>This is nice. Thanks for sharing. You&#8217;ve given me something to think about, maybe the work process will stick with me, maybe not but it is something I found useful.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
