<?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: Iteration makes great games &#8211; duh</title>
	<atom:link href="http://blog.wolfbytes.fi/iteration-makes-great-games-duh/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.wolfbytes.fi/iteration-makes-great-games-duh/</link>
	<description>Games, storytelling and rants in between</description>
	<lastBuildDate>Thu, 29 Jul 2010 13:30:30 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andy</title>
		<link>http://blog.wolfbytes.fi/iteration-makes-great-games-duh/comment-page-1/#comment-13</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Mon, 21 Sep 2009 21:09:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wolfbytes.fi/?p=57#comment-13</guid>
		<description>Exactly the process the NetDevil folks have been using for Jumpgate Evolution. Using agile software development you can burn through iterations of functionality really fast, iron out any potential problem areas and respond to feedback from testers - be they internal or external. NetDevil have used both - they iterate and iterate and iterate internally then grab people from nearby game shops/off the street and ask them to playtest. And film them doing so. Then use the feedback to iterate some more.

I&#039;m torn as to the pros and cons of this approach. Speaking as a long-standing community member over at the Jumpgate Evolution forums, one of the biggest complaints I see is that this &quot;random Joe off the street&quot; approach means you&#039;re getting feedback off people that don&#039;t necessarily have the drive or passion to provide meaningful critique of the game. On the other hand, if you want to make a game that&#039;s easy to get into, accessible but ultimately complex to master (which I hope JGE will be...) then it&#039;s a really good approach to take. But where do you draw the line? How much feedback can you get from someone that might not even have heard of your game or that doesn&#039;t even play MMORPGs, let alone after only a couple of hours of gameplay? Maybe that&#039;s where the &quot;complex to master&quot; element comes in; your random, focus testing public are the perfect testers to tell you what&#039;s wrong with your user interface and to identify usability issues. Hermann Peterscheck (Lead Producer for JGE) has often been cited as touting that &quot;first fifteen minutes&quot; as being critical to capturing a potential subscriber in an MMORPG. Can you get the accessibility and polish early on in a project&#039;s lifecycle (which is kind of the idea of agile, iterative development) with just internal focus testing? Is it crazyness to keep things internal (all use of cranial explosive devices aside)?

I&#039;m interested to see how this pans out with a smaller developer like NetDevil. The game isn&#039;t in beta yet but has been &quot;Friends and Family&quot; testing for some time so I&#039;m guessing they&#039;re listening to their testers and...iterating their iterations. Time will tell...</description>
		<content:encoded><![CDATA[<p>Exactly the process the NetDevil folks have been using for Jumpgate Evolution. Using agile software development you can burn through iterations of functionality really fast, iron out any potential problem areas and respond to feedback from testers &#8211; be they internal or external. NetDevil have used both &#8211; they iterate and iterate and iterate internally then grab people from nearby game shops/off the street and ask them to playtest. And film them doing so. Then use the feedback to iterate some more.</p>
<p>I&#8217;m torn as to the pros and cons of this approach. Speaking as a long-standing community member over at the Jumpgate Evolution forums, one of the biggest complaints I see is that this &#8220;random Joe off the street&#8221; approach means you&#8217;re getting feedback off people that don&#8217;t necessarily have the drive or passion to provide meaningful critique of the game. On the other hand, if you want to make a game that&#8217;s easy to get into, accessible but ultimately complex to master (which I hope JGE will be&#8230;) then it&#8217;s a really good approach to take. But where do you draw the line? How much feedback can you get from someone that might not even have heard of your game or that doesn&#8217;t even play MMORPGs, let alone after only a couple of hours of gameplay? Maybe that&#8217;s where the &#8220;complex to master&#8221; element comes in; your random, focus testing public are the perfect testers to tell you what&#8217;s wrong with your user interface and to identify usability issues. Hermann Peterscheck (Lead Producer for JGE) has often been cited as touting that &#8220;first fifteen minutes&#8221; as being critical to capturing a potential subscriber in an MMORPG. Can you get the accessibility and polish early on in a project&#8217;s lifecycle (which is kind of the idea of agile, iterative development) with just internal focus testing? Is it crazyness to keep things internal (all use of cranial explosive devices aside)?</p>
<p>I&#8217;m interested to see how this pans out with a smaller developer like NetDevil. The game isn&#8217;t in beta yet but has been &#8220;Friends and Family&#8221; testing for some time so I&#8217;m guessing they&#8217;re listening to their testers and&#8230;iterating their iterations. Time will tell&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
