Last month, we had decided to start an enterprise App/Game Jam internally. The concept behind a jam is to run a 48h straight event with the objective to create a prototype by the end of it, allowing as much freedom as possible to a given team while they respond to a given theme.
This jam’s theme was “Rewards“.
To begin with, the main goal of this jam was to reunite the developers and designers at Appearition together and have them work in a single team. While we had worked together on various occasions and projects, we never had experienced a single project with all of us working towards a single outcome at once.
Although, each of us knew what others do, a jam (along with the pressure it provides) offered us the best way to bond further and learn more about out various skill sets, especially secondary skills and things we prefer doing in a project. During this jam, some of us found out that one of us had artistic skills, another with a preference for developing UI rather than code, and another with a strong desire to learn game programming. Participating in this type of event helped learning about each other’s strengths and weaknesses, as well as working as a team to achieve the single outcome.
While most projects we do are on an individual scale or a bigger scale, this was a great opportunity to test how we would come up with solutions for different time zones and remote work for a project with a tight deadline and heavy pressure.
Lastly, this was a great opportunity to change from what we usually do, which is more along the lines of R&D, enterprise application development, proof of concept, etc. Quite a few of us had never worked on a game before, or not for a long time. Being able to develop a prototype for a different type of use and audience was a challenge to us, as well as being refreshing.
Doing the jam
We started the jam with 6 of us:
- 2 Programmers (1 lead and 1 mechanic developer, both actual developers)
- 1 Game Artist (R&D developer but could do game art)
- 2 UI Designers (one pure UI Designer, one who prefers UI design over development)
- 1 Project Manager
We used Slack as our main communication tool and ZOOM and Skype for group calls. We started the jam all in a call, were briefed about the theme, then decided to individually explore the theme and return as a group to discuss our findings. Once on the call, we proposed several ideas, projects, talked about them and expanded them. After making sure each of us had something to work on, we started working. The team was divided in two locations: two people
in one house in Australia, and the rest of the team would meet at the office or at somebody’s place.
I want the latest in…
Connect with us
I want the latest in…
We agreed to work on an Appearition Simulator, which would be a game inspired from Game Dev Tycoon (2012, developed and published by Greenheart Games), where the player starts as our CEO, takes on projects, expands the team and builds the whole company from scratch. Part of this idea also helped explaining what the origin of Appearition was, and how it became what it is today.
The prototype of the game was meant to be a 2D horizontal management game, where the player controls several employees by selecting them one by one and giving them orders individually. Our CEO would receive calls about a client wanting a project, along with requirements and modules.
Client project panel. Gives some background on the project and client, including salary, time and tasks. The client stats affect the flow of the project, change of requirements, etc; and are meant to improve as we educate them.
Once accepted, all those requirements would appear on a blackboard as tasks (like a Kanban workflow, to-do, QA, done, etc) of different field of practice. Each of those tasks could be assigned to employees, who would have skills and preference in said field.
Task board, where employees select tasks. Here, there is a lvl5 R&D task, lvl0 UI Design and lvl0 Q&A. Those values aren’t meant to be absolutely accurate.
Upon project completion, each team member would receive skill proficiency, happiness if they worked on skills they liked, and food. The company would also get the money from the commission, and the client would gain trust in our company. If the project was not finished in time, the company would not earn a cent and every employee would lose happiness.
Our CEO currently working on a task. No time for sitting animations!
Unfortunately, we did not have sufficient time to push the project to a prototype level within the 48 given hours, mainly due to the way we worked as a group and had seek an extension in order to complete it.
However, the primary objectives were more along the lines of team-bonding and having a good time with colleagues by doing something different, and we did great on that. Additionally, most of us learned a lot from working on a non-enterprise project, since this isn’t what we’re used to.
Through most of the jam, we were using Slack to post work in progress of what we were each doing in order to keep the team informed. Once any of us had any struggle or was done with their task, we would get in a call together and keep ourselves updated. On the last day, we had a nearly constant group call ongoing to ensure that we were going to deliver properly and go through the problems we had.
Overall, we were happy with this opportunity given to us. On presenting this project to the entire company, we agreed on expanding this project as an introduction to Appearition, as well as a way to learn more about our colleagues.