what went wrong? · what went wrong? a survey of problems in game development good practices in...
TRANSCRIPT
What Went Wrong? A Survey of Problems in Game Development
Good Practices in Game DevelopmentIs The Game Industry That Bad?Is The Game Industry That Bad?
Francisco TrindadeTW London Geek Night
21st Nov 2008
© ThoughtWorks 2008
• Why?
• What?
Agenda
• How?
• Results
© ThoughtWorks 2008
Why?Why?
© ThoughtWorks 2008
• Survey of problems found in game development– Compare to the “traditional” industry
• Good practices in game development
What?
• Good practices in game development– Is Agile a good fit?
© ThoughtWorks 2008
How?
Read Analyzed Compared with
traditional
© ThoughtWorks 2008
Read
Postmortems
Analyzed
Datatraditional
industry
• Summarize project experience– Emphasys on positive and negative aspects
Postmortems
“The most severe blow suffered by all teams was
© ThoughtWorks 2008
“The most severe blow suffered by all teams was from accepting an unrealistic schedule. Despite endemic problems, . . . the concept that was floated at the time was that it would be possible to adhere to the original schedule if everyone simply worked around the clock.Foolish and naıve, we bought it, and started pushing.”
Problems Occurrence
Test Problems
Great Number of Defects
Over Budget
© ThoughtWorks 2008
0% 10% 20% 30% 40% 50% 60% 70% 80%
Unreal or Ambitious Scope
Feature Creep
Cutting Features
Design Problems
Delay or Optimistic Schedule
Crunch Time
Communication Problems
So...
© ThoughtWorks 2008
Is Agile a Good Is Agile a Good Fit?
© ThoughtWorks 2008
Best Practices
Good Programming Practices
Agile Modeling
Quality Control
Iterative Process
© ThoughtWorks 2008
0% 20% 40% 60% 80% 100%
Qualified Team
Creativity
Product Focus
Simple Tools
Good Programming Practices
• Game industry has the same problems as traditional software industry
• Agile is a good fit
Conclusion
• Agile is a good fit– Probably more than in the traditional industry
• Teamwork, Motivation, Cross-functional teams
© ThoughtWorks 2008
