<?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 To Use Timeboxes for Scheduling Software Delivery</title>
	<atom:link href="http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/feed/" rel="self" type="application/rss+xml" />
	<link>http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/</link>
	<description>Software product success.</description>
	<lastBuildDate>Sat, 19 May 2012 12:04:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Market Problems – Comparing Products Part 3 &#124; The Agile Radar</title>
		<link>http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/comment-page-1/#comment-856429</link>
		<dc:creator>Market Problems – Comparing Products Part 3 &#124; The Agile Radar</dc:creator>
		<pubDate>Mon, 16 Jan 2012 14:10:01 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/#comment-856429</guid>
		<description>[...] combine incremental development techniques to the activities of product management, combined with timeboxing to impose practical, artificial constraints on the process.  An agile product management process [...]</description>
		<content:encoded><![CDATA[<p>[...] combine incremental development techniques to the activities of product management, combined with timeboxing to impose practical, artificial constraints on the process.  An agile product management process [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/comment-page-1/#comment-575100</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Tue, 09 Mar 2010 06:20:36 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/#comment-575100</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;R @jezzaman03 check out http://bit.ly/awYBOu a timeboxing article I wrote a few years ago - better approach than triangle.&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">R @jezzaman03 check out <a href="http://bit.ly/awYBOu" rel="nofollow">http://bit.ly/awYBOu</a> a timeboxing article I wrote a few years ago &#8211; better approach than triangle.</span></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2009-06-22 &#8226; Bare Identity</title>
		<link>http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/comment-page-1/#comment-502123</link>
		<dc:creator>links for 2009-06-22 &#8226; Bare Identity</dc:creator>
		<pubDate>Tue, 23 Jun 2009 00:01:33 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/#comment-502123</guid>
		<description>[...] How To Use Timeboxes for Scheduling Software Delivery &#124; Tyner Blain (tags: timebox timemanagement projectmanagement planning development) [...]</description>
		<content:encoded><![CDATA[<p>[...] How To Use Timeboxes for Scheduling Software Delivery | Tyner Blain (tags: timebox timemanagement projectmanagement planning development) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Managing Project Schedules with Timeboxes &#124; Scheduling Software Reviews</title>
		<link>http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/comment-page-1/#comment-447947</link>
		<dc:creator>Managing Project Schedules with Timeboxes &#124; Scheduling Software Reviews</dc:creator>
		<pubDate>Sun, 12 Oct 2008 11:52:13 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/#comment-447947</guid>
		<description>[...] more detailed article, http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/ can be found with supporting diagrams that help visualize using timeboxes and making tradeoffs. [...]</description>
		<content:encoded><![CDATA[<p>[...] more detailed article, <a href="http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/" rel="nofollow">http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/</a> can be found with supporting diagrams that help visualize using timeboxes and making tradeoffs. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Managing Project Schedules with Timeboxes &#124; Recovery - The Appetizer!</title>
		<link>http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/comment-page-1/#comment-337903</link>
		<dc:creator>Managing Project Schedules with Timeboxes &#124; Recovery - The Appetizer!</dc:creator>
		<pubDate>Tue, 01 Apr 2008 20:53:09 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/#comment-337903</guid>
		<description>[...] For more details on how to apply (and when not to apply) each of the four methods, check out the extended article &#8220;How To Use Timeboxes for Scheduling Software Delivery&#8221; at http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/ [...]</description>
		<content:encoded><![CDATA[<p>[...] For more details on how to apply (and when not to apply) each of the four methods, check out the extended article &#8220;How To Use Timeboxes for Scheduling Software Delivery&#8221; at <a href="http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/" rel="nofollow">http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Free Articles &#187; Blog Archive &#187; Managing Project Schedules with Timeboxes</title>
		<link>http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/comment-page-1/#comment-324858</link>
		<dc:creator>Free Articles &#187; Blog Archive &#187; Managing Project Schedules with Timeboxes</dc:creator>
		<pubDate>Sun, 09 Mar 2008 13:53:02 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/#comment-324858</guid>
		<description>[...] For more details on how to apply (and when not to apply) each of the four methods, check out the extended article &#8220;How To Use Timeboxes for Scheduling Software Delivery&#8221; at http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/ [...]</description>
		<content:encoded><![CDATA[<p>[...] For more details on how to apply (and when not to apply) each of the four methods, check out the extended article &#8220;How To Use Timeboxes for Scheduling Software Delivery&#8221; at <a href="http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/" rel="nofollow">http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Managing Project Schedules with Timeboxes &#124; 3-in-1 Protection for your Recovery.</title>
		<link>http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/comment-page-1/#comment-279736</link>
		<dc:creator>Managing Project Schedules with Timeboxes &#124; 3-in-1 Protection for your Recovery.</dc:creator>
		<pubDate>Sun, 27 Jan 2008 09:24:05 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/#comment-279736</guid>
		<description>[...] For more details on how to apply (and when not to apply) each of the four methods, check out the extended article &#8220;How To Use Timeboxes for Scheduling Software Delivery&#8221; at http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/ [...]</description>
		<content:encoded><![CDATA[<p>[...] For more details on how to apply (and when not to apply) each of the four methods, check out the extended article &#8220;How To Use Timeboxes for Scheduling Software Delivery&#8221; at <a href="http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/" rel="nofollow">http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sharp Blue</title>
		<link>http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/comment-page-1/#comment-70259</link>
		<dc:creator>Sharp Blue</dc:creator>
		<pubDate>Sun, 11 Feb 2007 20:12:14 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/#comment-70259</guid>
		<description>&lt;strong&gt;The Carnival of Software Development, number 2...&lt;/strong&gt;

Welcome to the second edition of the Carnival of Software Development. This time around there were many more submissions than......</description>
		<content:encoded><![CDATA[<p><strong>The Carnival of Software Development, number 2&#8230;</strong></p>
<p>Welcome to the second edition of the Carnival of Software Development. This time around there were many more submissions than&#8230;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/comment-page-1/#comment-54508</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Thu, 27 Jul 2006 23:28:22 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/#comment-54508</guid>
		<description>Hey, thanks Lou.  Hope you&#039;ll stick around and read some more.</description>
		<content:encoded><![CDATA[<p>Hey, thanks Lou.  Hope you&#8217;ll stick around and read some more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lou Salgado</title>
		<link>http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/comment-page-1/#comment-54507</link>
		<dc:creator>Lou Salgado</dc:creator>
		<pubDate>Thu, 27 Jul 2006 22:40:02 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/#comment-54507</guid>
		<description>Just happened upon your website - some insightful processes on how to approach situations - enjoyed reading them - thanks</description>
		<content:encoded><![CDATA[<p>Just happened upon your website &#8211; some insightful processes on how to approach situations &#8211; enjoyed reading them &#8211; thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/comment-page-1/#comment-947</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Wed, 19 Apr 2006 16:23:44 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/#comment-947</guid>
		<description>James, thanks for reading and commenting!
You make great points.
Method 1 is a &lt;em&gt;bad idea&lt;/em&gt;.  But nonetheless, it does happen.  The only way I&#039;ve seen it work effectively is when a  feature is implemented in robust but inelegant code in order to make the deadline (incurring a code-debt).  That feature is then immediately refactored as part of the next development cycle.  It&#039;s a slippery slope, as projects risk crossing the tipping point where so much code is spaghetti/inelegant/hardToMaintain that no one bothers to write good code in the future.
Method 2 can work.  Brooks&#039; law is definitely right about adding people to a late project.  &lt;a title=&quot;Scheduling requirements changes&quot; href=&quot;http://tynerblain.com/blog/2006/04/11/scheduling-requirements-changes-part-2/&quot;&gt;By following the &quot;change deadline&quot; constraints we referenced via the scheduling post&lt;/a&gt;, we are not in Brooks&#039; sandbox.
The old maxim that 9 women can&#039;t make a baby in a month is certainly true.  But what if you have 8 women on the team, and the requirement is for 9 babies in 9 months?  Adding another woman makes sense.
You&#039;re right about the inefficiencies, which I briefly mentioned, and demonstrated in the diagram by showing &quot;unused&quot; space - cost that is incurred in order to increase scope.
Thanks again for making good points.  As far advocating methods goes, we encourage delays when schedules &#039;matter&#039; and limited extensions when they don&#039;t.  In my experience, schedules always matter to someone.</description>
		<content:encoded><![CDATA[<p>James, thanks for reading and commenting!<br />
You make great points.<br />
Method 1 is a <em>bad idea</em>.  But nonetheless, it does happen.  The only way I&#8217;ve seen it work effectively is when a  feature is implemented in robust but inelegant code in order to make the deadline (incurring a code-debt).  That feature is then immediately refactored as part of the next development cycle.  It&#8217;s a slippery slope, as projects risk crossing the tipping point where so much code is spaghetti/inelegant/hardToMaintain that no one bothers to write good code in the future.<br />
Method 2 can work.  Brooks&#8217; law is definitely right about adding people to a late project.  <a title="Scheduling requirements changes" href="http://tynerblain.com/blog/2006/04/11/scheduling-requirements-changes-part-2/">By following the &#8220;change deadline&#8221; constraints we referenced via the scheduling post</a>, we are not in Brooks&#8217; sandbox.<br />
The old maxim that 9 women can&#8217;t make a baby in a month is certainly true.  But what if you have 8 women on the team, and the requirement is for 9 babies in 9 months?  Adding another woman makes sense.<br />
You&#8217;re right about the inefficiencies, which I briefly mentioned, and demonstrated in the diagram by showing &#8220;unused&#8221; space &#8211; cost that is incurred in order to increase scope.<br />
Thanks again for making good points.  As far advocating methods goes, we encourage delays when schedules &#8216;matter&#8217; and limited extensions when they don&#8217;t.  In my experience, schedules always matter to someone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James A. Ward</title>
		<link>http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/comment-page-1/#comment-946</link>
		<dc:creator>James A. Ward</dc:creator>
		<pubDate>Wed, 19 Apr 2006 16:07:03 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/04/12/how-to-use-timeboxes-for-scheduling-software-delivery/#comment-946</guid>
		<description>Two of your four methods just don&#039;t work. In method 1, poor quality will invariably cause you to miss delivery dates, or greatly increase the risk that you will do so. At what point will the quality be so poor that the system is not viable? Remember, if it doesn&#039;t have to work, you can always meet any other constraint.

Method 2 violates Brooks&#039; Law. I won&#039;t bore the reader with restating it here, but it still is the law, and you pay the penalty for violating it. Admittedly, you can incrementally increase resources, such as a few hours of overtime per week, but, in general, this has already been done before the choices have to be made.

That leaves you with two choices, increase time or decrease scope. You don&#039;t get a one for one tradeoff here, the increases are not linear. Change has its own costs.</description>
		<content:encoded><![CDATA[<p>Two of your four methods just don&#8217;t work. In method 1, poor quality will invariably cause you to miss delivery dates, or greatly increase the risk that you will do so. At what point will the quality be so poor that the system is not viable? Remember, if it doesn&#8217;t have to work, you can always meet any other constraint.</p>
<p>Method 2 violates Brooks&#8217; Law. I won&#8217;t bore the reader with restating it here, but it still is the law, and you pay the penalty for violating it. Admittedly, you can incrementally increase resources, such as a few hours of overtime per week, but, in general, this has already been done before the choices have to be made.</p>
<p>That leaves you with two choices, increase time or decrease scope. You don&#8217;t get a one for one tradeoff here, the increases are not linear. Change has its own costs.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

