UBM Tech - Game Network

My Shopping Cart

[ 0 ] items in cart

View Cart | Checkout

Game Developer Research

Research Reports

Gamasutra

Contractor Listings

GDC Vault

Individual Subscription

GDC Audio Recordings

App Developers Conference 2013

GDC Next 2013

GDC Europe 2013

	GDC 2013
	GDC Online 2012
	GDC Europe 2012
	GDC 2012
	GDC 2011
	GDC 10
	GDC 09
	GDC Austin 08
	GDC Mobile 08
	GDC 08
	GDC Austin 07
	GDC Mobile 07
	GDC 07
	GDC 06
	GDC 05
	GDC 04
	GDC 03
	GDC 01
	GDC 2000 & Before

Newest Item(s)

Why Now Is the Best Time Ever to Be a Game Developer

Ingress: Design Principles Behind Google's Massively Multiplayer Geo Game

Playing with 'Game'

Gathering Your Party with Project Eternity (GDC Next 10)

D4: Dawn of the Dreaming Director's Drama (GDC Next 10)

Using Plot Devices to Create Gameplay in Storyteller (GDC Next 10)

How I Learned to Stop Worrying and Love Making CounterSpy (GDC Next 10)

Luck and Skill in Games

Minimalist Game Design for Mobile Devices

Broken Age: Rethinking a Classic Genre for the Modern Era (GDC Next 10)

Storefront > GDC Vault Store - Audio Recordings > More GDC > GDC 2005

View larger image

QTY:

Spider-man 2 DS Launch: Double the Screens! Half the Dev Cycle
Price	$5.95
Adjustment
Type
Stock	Unlimited
Status
Weight	0 lb, 0 oz
SKU	GDC-05-128
Statistics

Description

Spider-man 2 DS Launch: Double the Screens! Half the Dev Cycle,
4698

Programming, Lecture

Brent Gibson
Lead Artist, Vicarious Visions

Jan-Erik Steel
ABG Programmer, Vicarious Visions
Somehow games keep getting more complicated and dev cycles shorter! Spider-Man 2 DS is a perfect example - the platform was announced in Spring 2004, and we had to go to lot check by October. We obviously had to do some things differently if we were going to make launch! This post mortem discusses how to make quality games on accelerated schedules. We will cover the basics such as how we leveraged assets and tech, kept constant and effective communication, and stuck to rigid deadlines. Did we mention how to plan when everything you know is constantly changing? The session describes how we applied the Team Software Process (from the Software Engineering Institute). Finally we'll talk about proving game play without hardware and the compromises that occur.

The attendee come away with practical ideas of strategies that they can use when faced with very short dev cycles, lack of assets, and constant change.

Please leave this field blank.