Categories
GDC 2009

GDC09: Building and Sustaining Successful Free to Play MMOs

Don Choi, OGPlanet

Summary

Very little of interest in this talk. I think there is a *lot* more you could say, and it would be a lot valuable and interesting, on the topics covered. I have no idea why the talk was so content-light (mis-guessed the audience? speaker having to give someone else’s talk? lawyers insisted on removing info? nervous speaker?), the speaker seemed fine, it’s just that the content was … absent.

Categories
computer games design GDC 2009 massively multiplayer

GDC09: Making of Little Big Planet (ups, downs, mistakes, successes)

Alex Evans, Media Molecule
Mark Healey, Media Molecule

Summary

The MM guys are funny as ever, although Alex’s “I made it myself on the way here” presentation tool would perhaps have been more usefully replaced with something like Presi (or whatever it’s called – the “interactive” presentation tool that is like Alex’s thing, but on steroids. Ask Jussi, he’s a fan of it).

The overall impression I got is: here’s another studio that has “by trial and error and cunning and talent” independently discovered something very similar to Scrum. They don’t do Scrum, and I’m sure a lot of people will scream at me for even saying it, but … I went through similar “find a process that worked for game development” (not carried so far, and on much smaller projects), and I recognize a lot of the lessons they learnt and things they incorporated in their processes and approaches. And from my experience, I think they’d find it relatively easy to switch over to Scrum, and that they’d get a lot of benefit from having a more polished version of their processes. Not to say that Scrum is universally better – there’d be losses too – but for people considering their own processes to use – or trying to “understand” Scrum – you’d do well to read this liveblog and try to internalize some of the lessons and attitudes. And then consider this and scrum as alternative to each other, but both near-relatives. And … if you are *not* MM, and don’t have all the details of precisely how they work, you’d probably find it much easier and more effective to adopt the well-documented Scrum instead.