Death Be Thy Name - Week 1 Development Blog

Throughout the development of the game a series of weekly blog posts will be created which will be used to track overall progress alongside the discussion of my understanding of the practical implementation of agile and collaborative methods, discussing how problems were navigated and finally a weekly reflection to demonstrate what I have learnt and improved on throughout the games development.

The main use of the first week of the projects development cycle was used in order to collaboratively brainstorm ideas and establish what we want the game to be. This was achieved through the use of the digital collaboration service Miro which allowed us to brainstorm ideas and eventually come out with an idea which each member of the development team is happy with. A Retro Style boomer shooter.

Now that we had the base layer for what we wanted for the game it allowed the design team to begin flushing out ideas as to what can be done to make the game as enjoyable as possible. We did this through the use of a GDD (Games Design Document) which outlines the core design sectors and allowed us to give a concise and detailed description about the game which will overall help its development in the long term.

There is no significant individual work this week based on the collaborative nature of brainstorming and developing an idea to what we hope to achieve at the ending of the project, this will obviously change however as the project enters its official development stage around the three week mark.

In conclusion I believe that during this week I was successful in putting forward ideas and discussing my thoughts and providing evidence to why I believe they should be included. Furthermore through this weeks community session I was able to gain an understanding into agile development frameworks and how they should be introduced into the groups game. Most specifically Scrum as it is best suited for this project as the group would partake in weekly meeting to discuss what had been achieved in the previous week and what is going to be done in the upcoming week, which allows everyone to stay on task in order to end the 12 weeks with a product that is complete.