What Went Well?
I am particularly proud of my role as the team’s producer and programmer. Acting in an organisational capacity allowed me to keep the project within a realistic scope, including the strategic decision to prioritise a polished arena over a half-finished fourth character. I was tested on the morning of our presentation when our version control broke down. I was able to remain rational, bypass the faulty desktop application, and manually download a stable build from GitHub just five minutes before presenting.
What Would I Do Differently?
While we delivered a stable final product, I have learned that time management is the most critical factor in avoiding technical debt. If I were to start this project again, I would implement a strict “code freeze” at least 24 hours before any major milestone. Falling behind slightly on the implementation phase meant we had to scrap the Fire character to ensure the rest of the game remained functional. In the future, I will set more aggressive internal deadlines for my personal tasks to ensure a smoother integration process for the whole team.
What Have I Learnt?
This module has been incredibly beneficial for my social and professional skills within an academic setting. I have learned the value of a learning log and how to act on feedback to improve my work. Beyond the technical side of Unity and GitHub, I have learned how easily work can pile up if not managed correctly. These lessons in teamwork, communication, and technical resilience will stay with me for the rest of my university career and into the professional world.