AEGIS

Given that I've talked about a team of computer science students working on a game project, I thought I should also touch on the case of a computer science student working on a phone application. The key difference between an application and a game is that the former doesn't require balancing. While games need to be tested to ensure that the gameplay is well-balanced and challenging, an application doesn't have these requirements. That said, both types of projects share many similarities, such as the need for effective planning, clear communication, and solid coding skills. Regardless of the project type, it's important to approach the work with a strong sense of purpose and a willingness to collaborate with others.

Postmortem:

The team was fortunate to have had a month to plan out the project before diving into development. This planning phase allowed them to hit the ground running and tackle tasks one by one. In addition, the team was fortunate to have a highly talented programmer who was able to implement features with remarkable efficiency. Not only was this programmer able to complete his tasks on time, but he also provided significant help to his teammates with their own implementations. This level of collaboration and mutual support was instrumental in keeping the project on track and ensuring its success.

There really wasn't anything that went wrong on this project. The only thing I can think of is the time frame. I think if the team had another two months to work on the project, this application would be a lot more polished and possibly ready to be published to the store.

As I mentioned, the experience of application development is very different from game development, and with an efficient team, for most of the time, my job as a producer/project manager is to get out of their way and let them work.