Latest News
spacer View All spacer
 
November 22, 2009
 
Video Game Watchdog National Institute On Media And The Family Shutting Down [11]
 
Modern Warfare 2 Infinity Ward's 'Most Successful PC Version' Yet [13]
 
New Tech, Design Details Of Project Natal To Emerge At Gamefest In February
spacer
Latest Features
spacer View All spacer
 
November 22, 2009
 
arrow Upping The Craft: Susan O'Connor On Games Writing [6]
 
arrow Small Developers: Minimizing Risks in Large Productions - Part II [7]
 
arrow iPhone Piracy: The Inside Story [50]
spacer
Latest Blogs
spacer View All     Post     RSS spacer
 
November 22, 2009
 
Time Fcuk - A Postmortem [2]
 
Accepting the Inherent Value of Games
 
Planckogenesis, Part II: Song Structure & Gravy Train [1]
spacer
Latest Jobs
spacer View All     Post a Job     RSS spacer
 
November 22, 2009
 
Trion Redwood City
Sr. Environment Artist
 
Trion Redwood City
Sr. Evnironment Modeler
 
Sucker Punch Productions
Network Programmer
 
Sucker Punch Productions
Texture Artist
 
Sucker Punch Productions
Character Artist
 
Sucker Punch Productions
3D Environment Artist
 
Crystal Dynamics
Sr. Level Designer
 
Sony Online Entertainment
Brand Manager
spacer
About
spacer News Director:
Leigh Alexander
Features Director:
Christian Nutt
Editor At Large:
Chris Remo
Advertising:
John 'Malik' Watson
Recruitment/Education:
Gina Gross
 
News

  Feature: 'Small Developers: Minimizing Risks in Large Productions - Part I'
by Staff
0 comments
Share RSS
 
 
November 3, 2009
 
Feature: 'Small Developers: Minimizing Risks in Large Productions - Part I'
Advertisement
In a new Gamasutra feature, experienced game developer and manager Troy Dunniway, a veteran of studios like Microsoft, EA, Insomniac, and Ubisoft, discusses some of the major risks involved in transitioning from a small to large development team and how to identify and avoid them.

The first part in a two-part series, this feature covers four of the 10 risks outlined by Dunniway -- business risks, pre-production risks, process risks, and team risks -- and is designed to help other developers get a general feel for the inherent risks in a large-scale project.

In this excerpt, Dunniway stresses the importance of a good pre-production phase, an area he believes many developers overlook or approach incorrectly:

"The biggest risk related to pre-production is not having adequate (or any) pre-production at all. Some teams will jump right in and just start building the game, planning to adjust things as they go. The whole point of pre-production is to mitigate the creative risks of a project and build a plan which you know you can execute on and have proven is feasible.

"Unfortunately it is very easy for a team to either work on the wrong stuff during pre-production, or to not work on things thoroughly enough, since the definition of pre-production is a little vague for most.

"For example, teams have used all their pre-production time to test risky new game technologies and mechanics, but then failed to produce anything else. So, in this case, they succeeded in that they proved that their big new and hopefully cool feature sucked and wasn't worth doing, but on the other hand they chewed up 12 months and now have almost nothing to show for it -- and basically had to start over and prove that the new core idea was feasible.

"Another common mistake is that people prototype a variety of features, but hack the code together. This code is usually meant to be redone, but now suddenly everyone assumes everything is "working" and that the game can be done much sooner than the team actually intended.

"What you do in pre-production is just as important as how you do it."


The full feature delves even further into areas of pre-production like concepting and prototyping, and covers the other three risk areas covered by part one of the series.
 
   
 
Comments

none
 
Comment:
 


Submit Comment