Final Project Scoping Proposal

To get early feedback on your final project ideas, you are asked to submit a brief project scoping proposal. You'll get feedback before the in-class project pitches, so you can use it when you prepare for these presentations. The purpose is to get you started thinking about initial project directions. Nothing you write in the proposal is set in stone; that is, it is possible to change direction later, although we recommend you do so judiciously and it is probably good to consult with us about any really big changes of direction.

See the Final Project Guidelines for a sense of the overall requirements for the final project.

Scoping Proposal Requirements

The goal is to scope out your final project. The proposal should be at most 2 pages and should include:

1.  Project title, team members, and their areas of relative expertise.
2. Describe the subject domain you intend to build a game for. If you have a couple ideas you can list both and we can provide feedback.
   
   1. What is an example of task a player would get better at from playing your game?
   2. What challenges do you think novices have with learning this content?
3. Describe any preliminary game ideas. Again if you have more than one you can list them.
   
   1. Are you thinking of making a digital or non-digital game?
   2. What kinds of mechanics, dynamics, or aesthetics are you interested in creating?
4. Describe who you envision your audience to be.
   1. How will you find novices or experts for knowledge elicitation or playtesting?
5. Describe your collaboration plan
   1. Provide a link to a Google drive (or other service) where we can track your working files
   2. When will your team meet outside of class? Or how will you manage work asynchronously?