1. Game Design, Development, and Technology
CS 382
Game Design, Development, and Technology
Teams and Processes
Software Engineering Methods
Production Team Members
Part 3.1

2. Software Engineering Methods
Several software engineering methods are commonly used to create video games.
Method 1: Extreme Game Programming
(aka: “Code Like Hell, Fix Like Hell”)
Design
Code
Test
Deliver
Arguments For…
Coding with too much planning can be as bad as coding with no planning at all
Tends to make programmers tackle the big problems earlier rather than coming up with (possibly faulty) solutions to the smaller problems that are discarded later
Arguments Against…
The frantic pace of the process is too stressful for most developers
Errors are not systematically eliminated and sometimes are not detected at all
Only suited for small projects with simple requirements (i.e., not games)
Part 3.1
Teams and Processes
Page 70

3. Method 2: Cleanroom Software Engineering
(aka: “Increment-to-Completion”)
Game Design – High Level Requirements
Test
Integrate with Full Game
Initial Lower Level Designs
Key System Design A (e.g., Rendering)
Key System Design B (e.g., Game Logic)
Code
Pre-Integration System Test
Arguments For…
Promotes parallel development of independent features
Relies heavily on system integration, so a playable version of the game is available early in the process
Arguments Against…
Parallel efforts require high degree of coordination to be successful
Lower level design is always in flux, with specifications that are hard to document until after full implementation
Part 3.1
Teams and Processes
Page 71

4. Method 3: Cascade Development
(aka: “The Waterfall Method”)
High Level Game Design
Lower Level Features Design
Coding & Module Testing
Integration & System Testing
Delivery & Maintenance
Arguments For…
Eliminates common uncertainties by requiring extensive up-front planning
Yields accurate schedule and completion estimation
Arguments Against…
Relies heavily on correct decisions at the beginning of the development process
Does not accommodate significant alterations to game features
Part 3.1
Teams and Processes
Page 72

5. Method 4: Iterative Development
(aka: “The Spiral Method”)
Arguments For…
Flexibly allows the definition, design, and development to be adjusted throughout the entire process
Permits dynamic reaction to competitive market demands
Arguments Against…
Frequently results in “feature creep”, with constant changes to both budget and timeline
Tempts developers to short-change high- level design in favor of ad hoc adjustments
Part 3.1
Teams and Processes
Page 73

6. Method 5: Agile Project Management
(aka: “Adaptive Software Development”)
Arguments For…
Simplifies the development process to a minimal set of practices that may be adapted for each project and each development environment
Well suited to project mobility and speed
Arguments Against…
Does not prescribe specific practices, so getting started can seem problematic
Game publishers may have difficulty accepting this approach unless they view themselves as customers who control the list of priorities
Part 3.1
Teams and Processes
Page 74

7. Production Team Members
Producer
Day-to day supervision of direct reports
Review of weekly task lists
Evaluation of resource allocation
Assignment of personnel to specific game features
Maintaining cohesive and consistent team vision
Management of outside contractors
Facilitating communication and decision-making
Proactive identification of potential problems
Ensuring that the team is fully staffed and supplied
Providing feedback and performance reviews for team
Part 3.1
Teams and Processes
Page 75

8. Assistant Producer Project management and game design evaluation
Interfacing with and supporting developers, licensors, and marketing
Design documentation review
Tracking team members’ progress according to schedule
Interacting with Quality Assurance team
Coordinating information released to game fans
Assisting in the fulfillment of the producer’s responsibilities
Part 3.1
Teams and Processes
Page 76

9. Executive Producer
Offering creative input and direction to guide the brand to a successful place within the market
Leading the global business effort and vision for a brand
Clarifying the vision for the brand, conveying it to other department executives and internal leaders
Receiving reports from producers and assistant producers, as well as various team leads (lead programmer, lead designer, lead artist, etc.)
Part 3.1
Teams and Processes
Page 77

10. Product Planner Program Manager Development Director
Developing and defining the future of a game, a franchise, or even a product peripheral
Planning for new consoles, controllers, headsets, networking capabilities, etc.
Program Manager
Communicating as the voice of the game team to other departments, including marketing
Contributing to specification writing and managing dependencies between software groups
Development Director
Mentoring, training, and coaching developers
Defining initial project scopes and delivery schedules
Identifying risks and prioritizing objectives
Part 3.1
Teams and Processes
Page 78

11. Production Assistants
Interning at the ground level, doing mundane tasks in administrative work, software testing, meeting preparation, note taking, etc.
Learning the ropes to gain the experience needed to become assistant producer, producer, etc.
Part 3.1
Teams and Processes
Page 79