<?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: The Train Game</title>
	<atom:link href="http://blog.tastycupcakes.com/2009/06/the-train-game/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.tastycupcakes.com/2009/06/the-train-game/</link>
	<description>Fuel for Software Professionals</description>
	<lastBuildDate>Tue, 20 Jul 2010 12:11:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Kevin E. Schlabach</title>
		<link>http://blog.tastycupcakes.com/2009/06/the-train-game/comment-page-1/#comment-46</link>
		<dc:creator>Kevin E. Schlabach</dc:creator>
		<pubDate>Tue, 15 Dec 2009 01:20:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tastycupcakes.com/?p=67#comment-46</guid>
		<description>This game was played in an organization that provides software on a monthly billing cycle.  Each one minute iteration represents a one month billing cycle.  This is why the iterative team gets paid every time.

It illustrates how an earlier delivery leads to earlier value and billing from the customer.  It also surprises people how quickly this &quot;revenue&quot; adds up and helps the project &quot;break even&quot; long before the big bang development.

Because the metaphor is a tangible product, I see where your question comes from.  I hope this helps clarify the game and its application!

Also, every time I&#039;ve run this game, the iterative team gets much further in their &quot;value&quot; simply because they learn/adapt quicker.  The big release team almost always tries to do BDUF (big design up front) and falls behind.</description>
		<content:encoded><![CDATA[<p>This game was played in an organization that provides software on a monthly billing cycle.  Each one minute iteration represents a one month billing cycle.  This is why the iterative team gets paid every time.</p>
<p>It illustrates how an earlier delivery leads to earlier value and billing from the customer.  It also surprises people how quickly this &#8220;revenue&#8221; adds up and helps the project &#8220;break even&#8221; long before the big bang development.</p>
<p>Because the metaphor is a tangible product, I see where your question comes from.  I hope this helps clarify the game and its application!</p>
<p>Also, every time I&#8217;ve run this game, the iterative team gets much further in their &#8220;value&#8221; simply because they learn/adapt quicker.  The big release team almost always tries to do BDUF (big design up front) and falls behind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lodewijk Bergmans</title>
		<link>http://blog.tastycupcakes.com/2009/06/the-train-game/comment-page-1/#comment-44</link>
		<dc:creator>Lodewijk Bergmans</dc:creator>
		<pubDate>Mon, 14 Dec 2009 22:52:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tastycupcakes.com/?p=67#comment-44</guid>
		<description>I do not quite understand this; does the iterative team get money for the entire track every minute??
that would not be a fair comparison! normally one would assume that a team is only paid once: for their final delivery..
(or otherwise they may collect their money in steps; but if the final product is doing less than the &quot;big release&quot; group; it does not make sense if they get much more money..)

now it is questionable whether the iterative team will actually build a &#039;more valuable&#039; final product in this game.. (any experience?)

Why not set a fixed time (and be very strict about it), and then see if the big release team can handle that? --&gt; makes also for an excellent social skills training, although that can actually ruin the real goals of the exercise..</description>
		<content:encoded><![CDATA[<p>I do not quite understand this; does the iterative team get money for the entire track every minute??<br />
that would not be a fair comparison! normally one would assume that a team is only paid once: for their final delivery..<br />
(or otherwise they may collect their money in steps; but if the final product is doing less than the &#8220;big release&#8221; group; it does not make sense if they get much more money..)</p>
<p>now it is questionable whether the iterative team will actually build a &#8216;more valuable&#8217; final product in this game.. (any experience?)</p>
<p>Why not set a fixed time (and be very strict about it), and then see if the big release team can handle that? &#8211;&gt; makes also for an excellent social skills training, although that can actually ruin the real goals of the exercise..</p>
]]></content:encoded>
	</item>
</channel>
</rss>
