Most of the time this semester has been spent in pre-production and documentation, where me and my team create the blueprint for the game, and setup how the game is going to be made. We made schedules for tasks, and broke down who does what on the team, in what order, and on what weeks. All this setup will be useful for making next semester smoother as we progress to production. It has also given me an opportunity to meet the team and understand each other's workload and habits, which will make the interpersonal dynamics easier when we inevitably get into disputes and arguments during production. Doing all the documents required for pre-production also gives me a point of reference for implementing things, for example, how fire spreads and the types of trees in our game, which I will be working on, are clearly laid out in the GDD, so if I'm ever unsure of what to do or make, I can look back at the document for guidance. I think some of the processes and practices the team has employed will also be useful beyond next semester, taking how to create these documentations into capstone next year, and also some of the other tools like jira and Miro into a professional career beyond that. Excited to work on this next semester with my team.
Did you like this post? Tell us
Leave a comment
Log in with your itch.io account to leave a comment.