Evan: Postmortem

Things are coming to a close this week and it's time to do a brief personal postmortem. We decided each person should individually write a mini version, and we'd bring together our ideas for a longer one.

The Good

• Not being overly ambitious: Early on, we took a pragmatic approach with what we could and couldn't do in ten weeks. This paid off big time. We didn't over-promise too much, and we defined an idea that we could - and did- build.
• Regardless of short term setbacks, we improved: Each week, we had a new build that was noticeably improved than the previous. Regardless of assets being late or not turned in at all, our weekly build improved.
• Dylan Yates: He did an unproportional amount of work, and without him the project wouldn't be what it was. Dylan, if our project moves forward, I promise this will be fixed!

The Bad

• Management: This is more of a disappointment in myself rather than the rest of the team. There were times where I didn't micromanage enough and it ended up hurting the quality of the project at times.
• Not having a (used) master asset list: This would have been helpful to have for obvious reasons. I created a master list late in the project, and it was unfinished and unused. We should have created and maintained a list earlier in development. This is necessary should our project move forward.
• Deadlines being missed: This was stressful for a few reasons. When things are late, I had to go find out  the reason why and when they'd be in. When it became a problem, I had to be Mr. Manager and give serious talks. That wasn't fun.