Team Tools

This week I thought it might be interesting for people to see what tools we use internally at the studio when working on a project. Over the years we’ve changed how we’ve communicated on a daily basis and track our work tasks. As Drinkbox grew, we adopted new practices – but as you’ll see, we also have stuck with some old school tools.

For daily communication we’ve recently started to use Slack – although Slack isn’t the perfect solution, we enjoy the ease at which we can break into teams and add media files. For me it provides an easy way to harass the art team, or pop over to the coders to see what are the newest memes. Also, my favorite channel is the #bookclub.


When Drinkbox wants to coordinate tasks at a high level we prefer to use Trello. The tool provides a simple way to pass tasks around to each other. We usually are much more active on Trello earlier in a project where having microscopic control over tasks isn’t all that important. Some of our pros include the drag-and-dropness, comments & image sharing capabilities.



As a project starts to enter final production / bug fixing we move over to the nitty gritty greatness of bugzilla. Although not the prettiest, bugzilla is a powerhouse in providing a multitude of ways for us to track bugs, asign bugs, and statistically evaluate how our bugs are being fixed.

Below is a list of bugs currently for the Severed project


Here is a really cool graph of our Severed bugs tracked over time – a lot of information can be gained seeing the # of new bugs found (hopefully decreasing) and the rate at which we’re fixing assigned bugs. For example you usually see a big spike up when a big QA pass happens, and big drops during intensive periods of production as we knock down tasks.

Hope you enjoyed your dose of insight into Drinkbox game production.

Comments are closed.