Gear Up launched today!
Wow...seven years almost to the day since my first book. What took so long? Well, cranking out 250 pages of text, illustrations and doing most of the proofreading on my own took years. I'm proud of the result, but it was a "check off the bucket list item" thing at the time.
This book was different. First, let's visit its origin.
Developers always ask me “we’re having problems doing X with methodology Y, what should we do?”. My first answer is always “What have you tried?”. I ask this because the best solutions usually come from the people doing the work and experimenting with new practices, not following so-called “best practices”.
“Best practices” implies there are none better. Practices will always change as do our players, technology and markets. This leads to experimental practices, where teams explore ways of adapting to change and improving how they work together.
Thinking about that original question, I think of all the experiments I’ve seen developing games, training and coaching at over 100 studios over the last decade. I thought that if we could share these as a reference, it might spark that sense of experimentation with many developers. Experimentation is key not only to creating great games, but creating great teams.
I had a GDC workshop coming up, so I decided to make it about such practices.
|The "Shonk" and I sporting our|
Rugby jerseys at GDC
While collecting these practices, we established some criteria for what makes a practice “advanced”:
- Experimental - Expressed as something we are doing to solve a specific problem. If it doesn’t solve it, we stop doing it. Implemented with the idea that it will be eliminated or someday replaced with something better.
- Incremental - Not so large that we don’t see the benefit, at least in an iteration or release cycle of a few months. They can be validated quickly
- Flexible – Not too specific so as to be adaptable to differing needs
- Collaborative - Not imposed. Demonstrates consideration, and respect.
- Radiative - Visible. Creates transparency. There is sometimes an electronic solution, but they are only recommended for distributed teams
This experience was a joy. It felt like being on a team again, which I have sorely missed. Maybe the next book won't take seven years!
If you are interested in learning more about the book, please visit