<?xml version="1.0" encoding="ISO-8859-15"?><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: Oy! Hasbro! Developing Software Is Harder Than You Think</title>
	<atom:link href="http://6d6fireball.com/rpg/oy-hasbro-developing-software-is-harder-than-you-think/feed/" rel="self" type="application/rss+xml" />
	<link>http://6d6fireball.com/rpg/oy-hasbro-developing-software-is-harder-than-you-think/</link>
	<description>Home of the 6d6 RPG</description>
	<lastBuildDate>Sun, 18 Jul 2010 04:36:41 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: njharman</title>
		<link>http://6d6fireball.com/rpg/oy-hasbro-developing-software-is-harder-than-you-think/comment-page-1/#comment-490</link>
		<dc:creator>njharman</dc:creator>
		<pubDate>Sun, 07 Dec 2008 18:48:04 +0000</pubDate>
		<guid isPermaLink="false">http://6d6fireball.com/?p=455#comment-490</guid>
		<description>I don&#039;t think this is a rule, although from experience it should be and for far more than just software development.

When you are rewriting a product, new language, new infrastructure, new ruleset, new manufacturing plant, do not also add features / expand the scope of product.  Wait until your change is done and stable then build on it.  It is too risky and hard to try to build on a moving, unfinished target.

So when radically changing the rules, themes, playstyle of your RPG do not at the same time decide to shift it from the table top to the computer screen.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think this is a rule, although from experience it should be and for far more than just software development.</p>
<p>When you are rewriting a product, new language, new infrastructure, new ruleset, new manufacturing plant, do not also add features / expand the scope of product.  Wait until your change is done and stable then build on it.  It is too risky and hard to try to build on a moving, unfinished target.</p>
<p>So when radically changing the rules, themes, playstyle of your RPG do not at the same time decide to shift it from the table top to the computer screen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonas Q</title>
		<link>http://6d6fireball.com/rpg/oy-hasbro-developing-software-is-harder-than-you-think/comment-page-1/#comment-92</link>
		<dc:creator>Jonas Q</dc:creator>
		<pubDate>Wed, 22 Oct 2008 04:07:20 +0000</pubDate>
		<guid isPermaLink="false">http://6d6fireball.com/?p=455#comment-92</guid>
		<description>You nailed it. Poor project management. In over their heads with software development. The online mags might be ok, but their compedium would be better suited as a data dump into a wiki. The tools (encounter builder , etc) , well -- they suck (imho). Dungeon Genie was better (for 3.5) but no OGL with nip that in the bud. Hasbro bringing corporate stupidity to the fantasy world.</description>
		<content:encoded><![CDATA[<p>You nailed it. Poor project management. In over their heads with software development. The online mags might be ok, but their compedium would be better suited as a data dump into a wiki. The tools (encounter builder , etc) , well &#8212; they suck (imho). Dungeon Genie was better (for 3.5) but no OGL with nip that in the bud. Hasbro bringing corporate stupidity to the fantasy world.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
