<?xml version="1.0"?>
<rss version="2.0">
<channel>

  
<title>Coding the Architecture - How long is a timebox?</title>
<link>http://www.codingthearchitecture.com/2006/01/23/how_long_is_a_timebox.html</link>
<description> One of the most common questions about timeboxing relates to the length of timeboxes. How long should they be and what factors influence this decision?    While there are many recommendations out there, some of which are strongly tied to the development ...</description>
<language>en</language>
<managingEditor>Simon Brown</managingEditor>
<lastBuildDate>Thu, 13 Apr 2006 03:52:47 GMT</lastBuildDate>
  
  

  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>Re: How long is a timebox?</title>
    <link>http://www.codingthearchitecture.com/2006/01/23/how_long_is_a_timebox.html#comment1144901306006</link>
    <description>
      I actually disagree with the premise - I don&#039;t believe that requirements churn should have any impact on iteration length - certainly not when we&#039;re talking about 2 to 4 week timeboxes.&lt;br/&gt;&lt;br/&gt;

I just posted a couple articles about 
1) &lt;a href=&#034;http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/&#034;&gt;Using timeboxes to schedule delivery&lt;/a&gt;
and
2) &lt;a href=&#034;http://tynerblain.com/blog/2006/04/11/scheduling-requirements-changes-part-2/&#034;&gt;Scheduling change requests&lt;/a&gt;.
&lt;br/&gt;&lt;br/&gt;
The process identified in the scheduling post allows us to handle churn without affecting the ideal timebox duration.

Scott Sehlhorst
    </description>
    <author>Scott Sehlhorst</author>
    <comments>http://www.codingthearchitecture.com/2006/01/23/how_long_is_a_timebox.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2006/01/23/how_long_is_a_timebox.html#comment1144901306006</guid>
    <pubDate>Thu, 13 Apr 2006 04:08:26 GMT</pubDate>
  </item>
  
  <item>
    <title>How to use timeboxes for scheduling software delivery</title>
    <link>http://www.codingthearchitecture.com/2006/01/23/how_long_is_a_timebox.html#trackback1144900367228</link>
    <description>
      Roger had a great suggestion in the comments to our previous two-part post on scheduling requirements changes based on complexity.  Roger pointed out that we had not explained what timeboxing is, but implicitly used the principles of timeboxing in our ...
    </description>
    <author>Tyner Blain</author>
    <comments>http://www.codingthearchitecture.com/2006/01/23/how_long_is_a_timebox.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2006/01/23/how_long_is_a_timebox.html#trackback1144900367228</guid>
    <pubDate>Thu, 13 Apr 2006 03:52:47 GMT</pubDate>
  </item>
  
  <item>
    <title>The Pros and Cons of Short Iterations</title>
    <link>http://www.codingthearchitecture.com/2006/01/23/how_long_is_a_timebox.html#trackback1143553480192</link>
    <description>
      My first experience with any process that was similar to an Agile approach was in a startup ten years ago.  We did 3-day-long iterations on a software project with a three person development team.  That experience, followed by its antithesis, shaped ...
    </description>
    <author>Agile Advice - How and Why to Work Agile</author>
    <comments>http://www.codingthearchitecture.com/2006/01/23/how_long_is_a_timebox.html#comments</comments>
    <guid isPermaLink="true">http://www.codingthearchitecture.com/2006/01/23/how_long_is_a_timebox.html#trackback1143553480192</guid>
    <pubDate>Tue, 28 Mar 2006 13:44:40 GMT</pubDate>
  </item>
  
  </channel>
</rss>
