<?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"
	>
<channel>
	<title>Comments on: Flow or Iterations - What Do You Try First?</title>
	<atom:link href="http://www.agileadvice.com/2008/02/14/scrumxplean/flow-or-iterations-what-do-you-try-first/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.agileadvice.com/2008/02/14/scrumxplean/flow-or-iterations-what-do-you-try-first/</link>
	<description></description>
	<pubDate>Tue, 07 Oct 2008 08:21:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: tobiasmayer</title>
		<link>http://www.agileadvice.com/2008/02/14/scrumxplean/flow-or-iterations-what-do-you-try-first/#comment-1817</link>
		<dc:creator>tobiasmayer</dc:creator>
		<pubDate>Fri, 22 Feb 2008 05:06:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.agileadvice.com/2008/02/14/scrumxplean/flow-or-iterations-what-do-you-try-first/#comment-1817</guid>
		<description>I agree.  I like the clear boundaries a timebox provides. Constraints, in fact support creativity.  

In general though in a healthy agile implementation I believe it is not an either/or situation.  It is not flow OR Iterations, but actually both.  We need to commit to a set of work in the timebox, but within that there is priority, and given that a commitment is a guess sometimes we overcommit and sometimes we undercommit.  In the latter case we bring things in to the iteration using a pull model (of course).  In the former case we ensure we get the essential things done first.  The timebox helps frame our work and gives us regular rhythm, which I find enormously helpful.  It gives us regular breathing room.</description>
		<content:encoded><![CDATA[<p>I agree.  I like the clear boundaries a timebox provides. Constraints, in fact support creativity.  </p>
<p>In general though in a healthy agile implementation I believe it is not an either/or situation.  It is not flow OR Iterations, but actually both.  We need to commit to a set of work in the timebox, but within that there is priority, and given that a commitment is a guess sometimes we overcommit and sometimes we undercommit.  In the latter case we bring things in to the iteration using a pull model (of course).  In the former case we ensure we get the essential things done first.  The timebox helps frame our work and gives us regular rhythm, which I find enormously helpful.  It gives us regular breathing room.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
