<?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 Evolution Explored</title>
	<atom:link href="http://drdansplace.com/2009/05/scrum-evolution-explored/feed/" rel="self" type="application/rss+xml" />
	<link>http://drdansplace.com/2009/05/scrum-evolution-explored/</link>
	<description></description>
	<lastBuildDate>Tue, 16 Aug 2011 18:42:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: Dan Rawsthorne</title>
		<link>http://drdansplace.com/2009/05/scrum-evolution-explored/comment-page-1/#comment-68</link>
		<dc:creator>Dan Rawsthorne</dc:creator>
		<pubDate>Thu, 20 Aug 2009 00:23:24 +0000</pubDate>
		<guid isPermaLink="false">http://drdansplace.com/?p=25#comment-68</guid>
		<description>Nothing else changes but the planning. The review cycle is the same, there is still Sprint Planning, etc. But the Sprint Planning changes so that the main result is the Sprint Goal, not the Sprint Backlog. Then the WIP is generated in an agile way in order to achieve the Goal given the reality of the work that&#039;s actually getting done. The only difference is that the team doesn&#039;t commit to stories at the beginning, it just commits to them as time becomes available. 

The main problem is prevention of &quot;scope creep&quot; within the stories once they have been committed to - so you need good definitions of done and a team mature enough to abide by them.

Dan Rawsthorne</description>
		<content:encoded><![CDATA[<p>Nothing else changes but the planning. The review cycle is the same, there is still Sprint Planning, etc. But the Sprint Planning changes so that the main result is the Sprint Goal, not the Sprint Backlog. Then the WIP is generated in an agile way in order to achieve the Goal given the reality of the work that&#8217;s actually getting done. The only difference is that the team doesn&#8217;t commit to stories at the beginning, it just commits to them as time becomes available. </p>
<p>The main problem is prevention of &#8220;scope creep&#8221; within the stories once they have been committed to &#8211; so you need good definitions of done and a team mature enough to abide by them.</p>
<p>Dan Rawsthorne</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rod Claar</title>
		<link>http://drdansplace.com/2009/05/scrum-evolution-explored/comment-page-1/#comment-67</link>
		<dc:creator>Rod Claar</dc:creator>
		<pubDate>Wed, 19 Aug 2009 14:18:28 +0000</pubDate>
		<guid isPermaLink="false">http://drdansplace.com/?p=25#comment-67</guid>
		<description>Nice article, Dan.

How do you see Scrum III measuring the delivery of business value if the the Kanban flow is driving the work?

Rod Claar</description>
		<content:encoded><![CDATA[<p>Nice article, Dan.</p>
<p>How do you see Scrum III measuring the delivery of business value if the the Kanban flow is driving the work?</p>
<p>Rod Claar</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rod Claar</title>
		<link>http://drdansplace.com/2009/05/scrum-evolution-explored/comment-page-1/#comment-66</link>
		<dc:creator>Rod Claar</dc:creator>
		<pubDate>Fri, 12 Jun 2009 15:58:44 +0000</pubDate>
		<guid isPermaLink="false">http://drdansplace.com/?p=25#comment-66</guid>
		<description>Nice, Dan.  One question.  How does Scrum III keep business value and business priority up front with the team?

Rod
http://EffectiveAgileDev.com</description>
		<content:encoded><![CDATA[<p>Nice, Dan.  One question.  How does Scrum III keep business value and business priority up front with the team?</p>
<p>Rod<br />
<a href="http://EffectiveAgileDev.com" rel="nofollow">http://EffectiveAgileDev.com</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

