Risk vs Reward

So we finally picked a game this week to move forward with. And it was a close one. We were torn between our well developed first person platformer/adventure, and our interesting fishing game. What it came down to was Risk vs Reward.

Our first game, which we now call a First Person Agile Adventure, was very developed. It had full movement, pickups, and other cool stuff. Our fishing game, on the other hand, had cool ideas behind it, but wasn't nearly as developed. Everyone liked both games. The thing was, while the Fishing game might have turned out as the more interesting of the two ideas, there were just so many unknowns. Our team doesn't have an actual programmer, so all the programming that would have been required would have been a huge hurdle. We had already had trouble getting the fishing game even with the Adventure game. On the other hand, while the end product might have been less novel, the adventure game already had so much done, we had proven we could effectively make it, and all that was left was to actually make it. Lower risk, but lower possible reward.

In the end, we decided to move the agile adventure forwards. For the purpose of Capstone, we felt it would be a better use of our time to work on something that had less risk, and a higher chance of generating a polished finished project. Yes, the fishing game might well have been more interesting game, but it also had a much higher chance of crashing and burning. The adventure game gave us a better chance at really showing off what we were capable of.