Discussion

Starting back at the beginning of the product, we knew we would want to get extra credit for this project, so we immediately aimed for six “game points”. We decided to split the points for a two-point hang man game and a four-point adventure game. The hang man game was relatively uninspired, so we quickly and easily made code, graphics, and even bug tested within the first few days. With that out of the way, we moved on to the planning of the adventure game. We brainstormed ideas about a stats system, but ultimately decided on a 5-choice based tree in a Zork style text-based adventure. The group, at this point, split into two coders / bug testers and two miscellaneous workers. The coders would spend their time figuring out the code and testing runs while the other two would build the descriptive script for all choices, update the notebook, create advertisements, and other business related aspects of the project.

Conclusion and Recommendations

The dynamic of this team is very powerful. With a clear goal in mind and some motivation, we can get anything done. Our team managed to split the work as evenly as possible in such a way that everyone pulled their weight to receive a great end product. Everyone showed up outside of class to continually spend time on the games. Should we have more time, we would’ve liked to add more graphics, some more music, and most importantly a more expansive game. Such ideas for a larger game included bosses, random encounters, and more mysteries. We recommend that teams spend their time together outside of class often, like this group has. It not only builds team workability but also friendships, and it is much easier to work with a friend than an acquaintance. We also recommend to work hard, even when it’s inconvenient. Too many times we would meet outside of class at strange times, but eventually we would all be there to work together. Even if one of us were to not show up at those meetings, much less and less would’ve been accomplished.