Jacob Dixey PPJ #9 (Final)

Jacob Dixey PPJ #9 (Final)

Personal Postmortem

What Went Right

  1. The vision of the game was accepted and further developed by the group. We ran into very little conflict (for the most part) on ideas, and the ideas that required discussion and deliberation were handled quickly through meetings.
  2. With making a game we could polish heavily, we were able to make a game that already feels pretty good to play, and will only get better as we add more challenges that stretch the player's ability to use what we've given them, i.e. the movement system.
  3.  The team has done a great job of helping build up the visual style of the game both through 2d art and models, but also shading work and post-processing
What Went Wrong
  1. Team communication was often very sparse up until the last minute each week, meaning it was difficult to recover when things didn't get done, and even worse when we needed to work up to the last minute to get content in.
  2. Even as we planned to program everything properly even if it took too much time, the pressure of showing work each week resulted in some parts of the game needing some significant refactoring to work ideally.
  3. Even core systems like Welded Weapons which was meant to be a part of the game from the beginning didn't make it in due to time constraints.

What I Learned
  • Don't be okay with doing all of the documentation while being the team lead. It severely cut into my programming time to the point where I had weeks where I didn't get to write a line of code.
  • As the team lead, it's easy enough for me to be excited for the game and want to work on it more seriously, but I need to try harder to have each team member feel that they responsibility and desire to work on the game because they have a big say in how it turned out.
  • There were a lot of moments where I didn't give clear instruction to artists which in turn put more of a burden on them even as I tried to give them the chance to design what they wanted.

Comments

Post a Comment

Popular posts from this blog

Peter Eldredge PPJ #6

Image
Bug Fixes/ Random Tweaks and Testing/Polish - 3 Hours Code Refactoring - 1 Hour Post Processing - 2 Hours Rumble Implementation - 2 Hours Overview I think artistically and game feel wise this week was very productive. This was thanks to the menus being filled out with 2d art and the implementation of Unity's Post Processing as well as the Beautify, another processing solution. Additionally rumble was added which adds a lot of impact to the collisions in the game, as well as allows the player to feel in heat increase better. Bug Fixes Tons of minor bugs were fixed and time was spent tweaking values. Not all of these are worth mentioning but I'll list the biggest ones: Fixed a issue where the player would rotate inappropriately after colliding with an object, causing the player controls to become inaccurate. Fixed issues where the prefabs were not consistent between scenes and not being saved properly. Fixed an issue where pausing the gam...
Read more

Sean McFadden PPJ#2

Overview:  Time Spent: Git Write-up and Practices Update: 2 hours AWS setup and Webhook setup: 2 hours Website rebuild into Vuejs: 2 hours Positives: Updated Git practices are incredibly helpful Negatives:Website broke at the last minute due to the EC2 instance Upcoming: Finishing the website and updating compute shader clouds
Read more

Rex Christian Personal Postmortem

Personal Postmortem Things that went right: 1:  Group member roles and workloads were typically very well defined and separated. We had very few issues with overlapping or conflicting work. 2: We communicated pretty effectively and easily contacted each other when we needed help or coordination while adding to the game. 3: We all mostly agreed on our vision for the game, and never really had any arguments or disputes regarding how the game should play or look. Things that went wrong: 1: Most of our work happened 1-2 days before the due date, and sometimes we'd even be patching bugs and getting things working mere minutes before class started. 2: Though we met on most weekends, we only planned our work during those meetings. We actually DID the work separately, only to meet right before class and compile it all at the last minute. 3: Sometimes features that were largely complete wouldn't make it in the week that we'd made them because we'd encounter a bug or ...
Read more