This week we had a team meeting discussing the next steps in our project and what we will be handling going forward with the week. We referred multiple times to our master schedule and even made some minor adjustments based on feedback we had gotten. With our work distributed equally between our entire team, we are confident moving forward.

With my individual work on the programming side of the project, I spent the week making myself accustomed to our games engine, one which I have only used once before, and that is the Twine engine.

My first week was dedicated to making sure Twine was in working order for our teams repository, while also setting up any essential assets that will be used in the future programming and development of our game while also researching deeper into Twine to fully understand how to properly use the engine.

With this I had gotten started on a proof of concept version of our game engine to see the possibilities for when we later expand upon it. I did this in order to assess any problems we may run into in the future and do damage control early on so I know what to expect and to prevent myself from running into problems later that may put our team behind on schedule.

Following our next meeting, I will present this proof of concept game engine to our team and report any and all odd findings or potential problems that we may face later on in development. This sprint was spent mostly doing risk assessment and seeing the limitations of our game engine while also learning how to properly utilize it, as before this week it was an engine that I was really not familiar with. Following our meeting we will discuss any possible work arounds or anything that may cause issues later on in development.