Things that went right:
1. Team structure - Each member of the team knew their strengths so we could plan roles accordingly. Everyone was also flexible with their tasks and could pivot when new priorities popped up.
2. Core game system implementation - While we weren't able to get everything we wanted into our gold build, we managed to flesh out the core mechanics of this game to a playable state. Now that we have a solid framework for the gameplay mechanics, we can expand our scope continuing forward.
3. Team meetings - Whenever our group found the time to meet during the week, we would always have productive sessions. A lot would get done as we bounced ideas off of each other and developed a stronger bond as a team.
Things that went wrong:
1. Build testing - More often than not, build submissions weren't ready until hours before they were due, which led to a lot of bugs during game presentations that could'v been avoided. Looking to next term we should plan in advance for build to be done at least a day before a due date so that there's proper time to test.
2. Developer blocks - Our dev team worked in separate Unity scenes in order to isolate their changes, then merged to a master once changes were ready to be merged. Unfortunately, due to communication issues, some merges were done preemptively, or one developer's changes were overwritten by another's. Luckily the dev team stepped up communication to compensate, as we all realized how detrimental these errors would be if we kept making mistakes.
3. Team meetings - Although team meetings themselves were always positive, it ended up being very difficult to meet as a group consistently over the quarter. We all have busy schedules and members often had to skip meetings to get other priorities done. Since we're all in the same boat it's an understandable issue, but those meetings were so valuable when we managed to find the time, so we'll make an extra effort next term to work in more meeting times.
Commentaires