<?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: Timeboxes, Iterations, and Orthodoxy</title>
	<atom:link href="http://jrothman.com/blog/mpd/2007/02/timeboxes-iterations-and-orthodoxy.html/feed" rel="self" type="application/rss+xml" />
	<link>http://jrothman.com/blog/mpd/2007/02/timeboxes-iterations-and-orthodoxy.html</link>
	<description>Management, especially good management, is hard to do. This blog is for people who want to think about how they manage people, projects, and risk.</description>
	<pubDate>Thu, 08 Jan 2009 17:14:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Roger L. Cauvin</title>
		<link>http://jrothman.com/blog/mpd/2007/02/timeboxes-iterations-and-orthodoxy.html/comment-page-1#comment-591</link>
		<dc:creator>Roger L. Cauvin</dc:creator>
		<pubDate>Sat, 03 Feb 2007 03:38:57 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/?p=7996#comment-591</guid>
		<description>Advocates of time-based iterations typically favor iterations that end in a deliverable.  The idea is to deliver something of demonstrable value to the user at the end of each iteration.  Typically, an iteration results in the implementation of a use case or &lt;a href="http://cauvin.blogspot.com/2006/12/use-case-versions.html"&gt;use case version&lt;/a&gt;.
When implementation of the deliverable runs behind schedule, you adjust the deliverable.  An effective agile team recognizes slippage early and promptly begins to make creative adjustments to the deliverables.
If you're implementing the "Purchase Items" use case and are running behind, reset the deliverable to be a &lt;i&gt;version&lt;/i&gt; of the use case such as "Purchase Item (cash only)".  The use case version still delivers value to the user, but the simplifying assumptions (support cash but not check or credit transactions) render it possible to meet the timebox for the iteration.</description>
		<content:encoded><![CDATA[<p>Advocates of time-based iterations typically favor iterations that end in a deliverable.  The idea is to deliver something of demonstrable value to the user at the end of each iteration.  Typically, an iteration results in the implementation of a use case or <a href="http://cauvin.blogspot.com/2006/12/use-case-versions.html">use case version</a>.<br />
When implementation of the deliverable runs behind schedule, you adjust the deliverable.  An effective agile team recognizes slippage early and promptly begins to make creative adjustments to the deliverables.<br />
If you&#8217;re implementing the &#8220;Purchase Items&#8221; use case and are running behind, reset the deliverable to be a <i>version</i> of the use case such as &#8220;Purchase Item (cash only)&#8221;.  The use case version still delivers value to the user, but the simplifying assumptions (support cash but not check or credit transactions) render it possible to meet the timebox for the iteration.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
