---

Bug Tracking

My junior game, Aztech, was huge for a student team with a lot of dev power.  That made having a formal system of bug tracking more important than ever to us.  One of the many tools we tried, and the one that stuck the best, was a Google spreadsheet.  It was easy to open and modify, and with Google's scripting tools you could modify it to fit you however you needed - for example, I wrote a script that highlighted different rows based on the status of the bug.

Sprint documents

For my latest game project, Guns with a Z, after our bi-weekly sprint meetings I would type up our goals into a Google spreadsheet that's shared with the whole team.  I like to divide tasks into four major sectors: Design, Logistics/Setup, Misc. Tech, and Procedural Content Generation for easy viewing.  All the tasks are used to work towards one of the goals we've set for the two weeks, usually determined by what we need to do for that milestone and, based on our other classwork, how much we expect to get done.