<?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: Stage Gates are Wrong for Games</title>
	<atom:link href="http://programmerjoe.com/2007/02/04/stage-gates-are-wrong-for-games/feed/" rel="self" type="application/rss+xml" />
	<link>http://programmerjoe.com/2007/02/04/stage-gates-are-wrong-for-games/</link>
	<description>Joe Ludwig's blog</description>
	<lastBuildDate>Sun, 01 Jan 2012 19:08:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Jeff Freeman</title>
		<link>http://programmerjoe.com/2007/02/04/stage-gates-are-wrong-for-games/comment-page-1/#comment-206</link>
		<dc:creator>Jeff Freeman</dc:creator>
		<pubDate>Sun, 11 Feb 2007 17:30:02 +0000</pubDate>
		<guid isPermaLink="false">http://programmerjoe.com/2007/02/04/stage-gates-are-wrong-for-games/#comment-206</guid>
		<description>What are movies doing? That 80% looks pretty good.</description>
		<content:encoded><![CDATA[<p>What are movies doing? That 80% looks pretty good.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danc</title>
		<link>http://programmerjoe.com/2007/02/04/stage-gates-are-wrong-for-games/comment-page-1/#comment-164</link>
		<dc:creator>Danc</dc:creator>
		<pubDate>Wed, 07 Feb 2007 20:03:23 +0000</pubDate>
		<guid isPermaLink="false">http://programmerjoe.com/2007/02/04/stage-gates-are-wrong-for-games/#comment-164</guid>
		<description>Aye, I think some of the practical lessons of the Stage Gate process are quite useful even if you strip the name off. Completely agree on the need to kill projects.  
- Prototype lots of little projects/features
- Test them
- Quickly kill the ones that don&#039;t work

Looking forward to hearing your thoughts about that particular book.  It has some great information in it despite the sometimes repetative writing style. :-)</description>
		<content:encoded><![CDATA[<p>Aye, I think some of the practical lessons of the Stage Gate process are quite useful even if you strip the name off. Completely agree on the need to kill projects.<br />
- Prototype lots of little projects/features<br />
- Test them<br />
- Quickly kill the ones that don&#8217;t work</p>
<p>Looking forward to hearing your thoughts about that particular book.  It has some great information in it despite the sometimes repetative writing style. <img src='http://programmerjoe.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://programmerjoe.com/2007/02/04/stage-gates-are-wrong-for-games/comment-page-1/#comment-132</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Tue, 06 Feb 2007 01:49:42 +0000</pubDate>
		<guid isPermaLink="false">http://programmerjoe.com/2007/02/04/stage-gates-are-wrong-for-games/#comment-132</guid>
		<description>Just ordered his book. I&#039;ll get back to you on the term &quot;Stage-Gate&quot; in a couple weeks. :)

In anycase, I think we could stand to be a lot more brutal about killing our own games.  Much better to kill a game at the prototype stage on your own terms than wait for the publisher to kill it late in development and let it take the whole studio with it.</description>
		<content:encoded><![CDATA[<p>Just ordered his book. I&#8217;ll get back to you on the term &#8220;Stage-Gate&#8221; in a couple weeks. <img src='http://programmerjoe.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>In anycase, I think we could stand to be a lot more brutal about killing our own games.  Much better to kill a game at the prototype stage on your own terms than wait for the publisher to kill it late in development and let it take the whole studio with it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danc</title>
		<link>http://programmerjoe.com/2007/02/04/stage-gates-are-wrong-for-games/comment-page-1/#comment-117</link>
		<dc:creator>Danc</dc:creator>
		<pubDate>Mon, 05 Feb 2007 05:37:41 +0000</pubDate>
		<guid isPermaLink="false">http://programmerjoe.com/2007/02/04/stage-gates-are-wrong-for-games/#comment-117</guid>
		<description>Try picking up one of Cooper&#039;s books on the topic.  Stage gate is more of a framing portfolio management technique than a development process in the way you are describing. 

&lt;b&gt;Winning at New Products:&lt;/b&gt; http://www.amazon.com/Winning-New-Products-Accelerating-Process/dp/0738204633

I can see where stage gate ideas can be easily mixed up with waterfall ideas.  The original concept came about during the 80&#039;s before even Lean Manufacturing had really matured in American companies. So you&#039;ll find some of the typical stages mentioned in the literature matching onto waterfall names.  However, the important idea is that there are stages and gates, not that you follow the exact model used 20 years ago by Proctor and Gamble for developing new types of cookies. In later writings, the 3rd generation processes emphasize flexibility as a key attribute. 

Because stage gate is a framework that works across multiple industries, there are lots of possible implementations.  I&#039;ll be the first to admit that there are bad business decisions made in the name of the stage gate process, just as is the case when any good idea is adopted by large numbers of people. I mentioned a few common mistakes in the paper.  The trick is to take the potent ideas like options-based portfolio management or success metrics and adapt them to your business. 

I like the paper you mentioned.  It is good to see this researching happening. 

take care
Danc.</description>
		<content:encoded><![CDATA[<p>Try picking up one of Cooper&#8217;s books on the topic.  Stage gate is more of a framing portfolio management technique than a development process in the way you are describing. </p>
<p><b>Winning at New Products:</b> <a href="http://www.amazon.com/Winning-New-Products-Accelerating-Process/dp/0738204633" rel="nofollow">http://www.amazon.com/Winning-New-Products-Accelerating-Process/dp/0738204633</a></p>
<p>I can see where stage gate ideas can be easily mixed up with waterfall ideas.  The original concept came about during the 80&#8242;s before even Lean Manufacturing had really matured in American companies. So you&#8217;ll find some of the typical stages mentioned in the literature matching onto waterfall names.  However, the important idea is that there are stages and gates, not that you follow the exact model used 20 years ago by Proctor and Gamble for developing new types of cookies. In later writings, the 3rd generation processes emphasize flexibility as a key attribute. </p>
<p>Because stage gate is a framework that works across multiple industries, there are lots of possible implementations.  I&#8217;ll be the first to admit that there are bad business decisions made in the name of the stage gate process, just as is the case when any good idea is adopted by large numbers of people. I mentioned a few common mistakes in the paper.  The trick is to take the potent ideas like options-based portfolio management or success metrics and adapt them to your business. </p>
<p>I like the paper you mentioned.  It is good to see this researching happening. </p>
<p>take care<br />
Danc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://programmerjoe.com/2007/02/04/stage-gates-are-wrong-for-games/comment-page-1/#comment-111</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Mon, 05 Feb 2007 00:19:44 +0000</pubDate>
		<guid isPermaLink="false">http://programmerjoe.com/2007/02/04/stage-gates-are-wrong-for-games/#comment-111</guid>
		<description>The thing is, I agree with everything you&#039;re saying except &quot;stage gate&quot;.  I&#039;m just not finding any reference to anyone using the Stage-Gate Process iteratively.  I found &lt;a href=&quot;http://serg.telecom.lth.se/research/publications/publication.php?main!filter!Publications:ID=309&quot; rel=&quot;nofollow&quot;&gt;this case study&lt;/a&gt; of a couple of Agile teams in a company that used stage gates.  They paid lip service to the gate criteria, but in the end, they didn&#039;t deliver everything and were still allowed to advance.

&lt;a href=&quot;http://www.agilejournal.com/content/view/33/&quot; rel=&quot;nofollow&quot;&gt;This&lt;/a&gt; article on the Agile Journal refers offhand to both Stage-Gate and waterfall as though they were synonyms. In fact, everything (online) I can find to read on Stage-Gate shows it as being somewhere between exactly the same and almost the same as waterfall.

What are you reading that points out Stage-Gate and agile being used together, or stages being used iteratively?  I&#039;m just not finding it.</description>
		<content:encoded><![CDATA[<p>The thing is, I agree with everything you&#8217;re saying except &#8220;stage gate&#8221;.  I&#8217;m just not finding any reference to anyone using the Stage-Gate Process iteratively.  I found <a href="http://serg.telecom.lth.se/research/publications/publication.php?main!filter!Publications:ID=309" rel="nofollow">this case study</a> of a couple of Agile teams in a company that used stage gates.  They paid lip service to the gate criteria, but in the end, they didn&#8217;t deliver everything and were still allowed to advance.</p>
<p><a href="http://www.agilejournal.com/content/view/33/" rel="nofollow">This</a> article on the Agile Journal refers offhand to both Stage-Gate and waterfall as though they were synonyms. In fact, everything (online) I can find to read on Stage-Gate shows it as being somewhere between exactly the same and almost the same as waterfall.</p>
<p>What are you reading that points out Stage-Gate and agile being used together, or stages being used iteratively?  I&#8217;m just not finding it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danc</title>
		<link>http://programmerjoe.com/2007/02/04/stage-gates-are-wrong-for-games/comment-page-1/#comment-108</link>
		<dc:creator>Danc</dc:creator>
		<pubDate>Sun, 04 Feb 2007 21:26:35 +0000</pubDate>
		<guid isPermaLink="false">http://programmerjoe.com/2007/02/04/stage-gates-are-wrong-for-games/#comment-108</guid>
		<description>You&#039;ve made a leap here and fundamentally mischaracterized a stage gate process as just another name for waterfall development methodologies.  One has absolutely nothing to do with the other.  You can use stage gate with waterfall.  You can use it with agile.  I personally feel it fits agile development much better and you&#039;ll see that more evolved stage gate processes have a striking similarity to many agile techniques even though you find them in non-software industries. 

As you may know from my other essays, I&#039;m a huge fan of various agile process and put a big emphasis on both prototyping and rapid iteration. The stage gate process maps quite nicely onto practices like Scrum or XP and brings a lot of common lessons to the table

&lt;b&gt;Start small:&lt;/b&gt; Do the simplest thing possible. You may learn something.
 
&lt;b&gt;Don&#039;t put all your eggs in one basket:&lt;/b&gt;  Try out multiple ideas early on.  Since you can&#039;t know which ideas will pan out, it makes a lot of sense to try several and then invest further in the promising ones. 

&lt;b&gt;Test regularly:&lt;/b&gt;  The whole point of the stage gate process is to have formal testing *throughout* the development process, not at the end. 

&lt;b&gt;Understand what success looks like:&lt;/b&gt; Even the most rapid iterative process is useless if you are making random changes that do no improve the product.  By understanding what success looks like, you can iteratively guide your products towards that that goal. 

&lt;b&gt;Invest late, not early:&lt;/b&gt;  Product development is a learning process. You might as well invest money as you discover success mechanics, settings, etc instead of dumping a wad on hand waving specs early on.

It is also worth noting that just because there are big formal stages that are used for large scale portfolio management, there is nothing in  the process that rejects the hundreds or thousands of iterative loops within each development stage.  In fact, I&#039;d recommend it since it helps teams meet the gate criteria more successfully. 

Stage gate has some serious potential for helping us create innovative product.  It brings portfolio management out of the darkness of Skull&amp;Bones green lighting committees and encourages that smart companies set aside money to build new-to-the world, high payoff products. 

It is worth taking another look at the concept and imagining how it might fit into the iterative work flow you so rightly target as critical to success in our industry.  I&#039;m guessing you&#039;ll be pleasantly surprised at how the two compliment each other. 

Appreciate the article and the opportunity to start a conversation. :-) 

take care
Danc.</description>
		<content:encoded><![CDATA[<p>You&#8217;ve made a leap here and fundamentally mischaracterized a stage gate process as just another name for waterfall development methodologies.  One has absolutely nothing to do with the other.  You can use stage gate with waterfall.  You can use it with agile.  I personally feel it fits agile development much better and you&#8217;ll see that more evolved stage gate processes have a striking similarity to many agile techniques even though you find them in non-software industries. </p>
<p>As you may know from my other essays, I&#8217;m a huge fan of various agile process and put a big emphasis on both prototyping and rapid iteration. The stage gate process maps quite nicely onto practices like Scrum or XP and brings a lot of common lessons to the table</p>
<p><b>Start small:</b> Do the simplest thing possible. You may learn something.</p>
<p><b>Don&#8217;t put all your eggs in one basket:</b>  Try out multiple ideas early on.  Since you can&#8217;t know which ideas will pan out, it makes a lot of sense to try several and then invest further in the promising ones. </p>
<p><b>Test regularly:</b>  The whole point of the stage gate process is to have formal testing *throughout* the development process, not at the end. </p>
<p><b>Understand what success looks like:</b> Even the most rapid iterative process is useless if you are making random changes that do no improve the product.  By understanding what success looks like, you can iteratively guide your products towards that that goal. </p>
<p><b>Invest late, not early:</b>  Product development is a learning process. You might as well invest money as you discover success mechanics, settings, etc instead of dumping a wad on hand waving specs early on.</p>
<p>It is also worth noting that just because there are big formal stages that are used for large scale portfolio management, there is nothing in  the process that rejects the hundreds or thousands of iterative loops within each development stage.  In fact, I&#8217;d recommend it since it helps teams meet the gate criteria more successfully. </p>
<p>Stage gate has some serious potential for helping us create innovative product.  It brings portfolio management out of the darkness of Skull&amp;Bones green lighting committees and encourages that smart companies set aside money to build new-to-the world, high payoff products. </p>
<p>It is worth taking another look at the concept and imagining how it might fit into the iterative work flow you so rightly target as critical to success in our industry.  I&#8217;m guessing you&#8217;ll be pleasantly surprised at how the two compliment each other. </p>
<p>Appreciate the article and the opportunity to start a conversation. <img src='http://programmerjoe.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  </p>
<p>take care<br />
Danc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

