Anyone who has ever worked in the games industry knows that building a successful game is complicated and there’s no recipe for it.
So in the beginning we handled every game individually with some parts of standardization.
One day our CEO approached us with a completely new strategy. The goal was to release as many games as fast as possible, with all tech integrated we needed to evaluate the potential of the game.
First, we talked to the departments involved to understand their needs. We collected the requirements in a Confluence document and structured them in collaboration with the teams so that every requirement was of a similar size - of course that was just a gut feeling.
Then we created a Jira project and Stories that contained all requirements from the Confluence document. This setup was our template that we used for every new game we signed.
In the tickets we only described the desired result, instead of the steps to be done. As so often in software development, we only knew what information was needed to evaluate the game. But not what we actually had to do to get the required information.
In order to distinguish which Story belonged to which department we added Jira Components - e.g. “Quality Assurance”. As Component Lead, we set the responsible person from the respective department. So the content of the ticket was completely owned by her and she was allowed to change everything if necessary. At the end we had about 50 Stories in our template project.
Then came the day we started our new process with the first game. We created a new Jira project for the game and cloned all template Stories from the template project to the game project. At this point, we started working with Deep Clone for Jira. Using this Marketplace app we could bulk clone and bulk move all 50 issues in one go. That was a huge timesaver, since we started a new project every two weeks.
Once the clones were created in the target project we started to work with them as agile as possible. Now that we knew what to do, we could specify the Stories: We added checklists, we attached relevant information about the game, we even closed some of the Stories right away because they were obsolete.
As you can imagine, it took some time and pain for this process to work smoothly. But in the end, we were amazed how much more efficient we could be by defining some basic standards and working with templates in Jira.
So if you ever need to speed up recurring projects or events, consider working with templates in Jira.
Marlene Kegel (codefortynine)
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events