Organisational Skills, Schedules & Planning

During the planning stage Max, Jack and I created an overall plan for our project idea which showed the whole scope of our project. The other team members joined later but they agreed with the plan. We put ideas down on a piece of paper for the different aspects of our game. It wasn’t thoroughly detailed but it allowed us to determine a baseline for what we would need to do to make a solid project and give a taster for what the game idea could be if taken further.

Overall project plan showcasing our entire game idea before cutting elements for our final version

The overall idea was to have seven different levels set within a moving train that had different gameplay mechanics to give the player a different experience in each carriage. The level elements and order of these levels was intended to be randomised to make the game more replayable as it would be a unique experience each time.

Our group was organised using a Google Drive document that included tables of work that needed to be done with colour coding used to display the priority and completion state of each aspect. The 3D modellers could choose what assets they would prefer to do and they would add a date when they completed each model. Other members had similar lists for their specific work.

Green = Completed

Orange = Partially Done

Red = Not Started

Example of table displaying the models needed for the game and the completion states with dates
Example of table displaying the levels in priority order and what had been completed for each level

We didn’t set a rigid schedule for our project but we strived to always have an improvement each week of the project as long as we had a functioning game at the end of our development time. Having some of the levels playable with a beginning and end sequence was the end goal.