CIS 300: Introduction to Computer Game Design

Two Week Report:
Gameplay Prototype

Due: Saturday, March 1st at 11:59pm

This week you need to submit your first two-week report. The report should be two things: a summary of the work that you did in order to get your gameplay prototype working, and a prediction of the amount of work you will need to do to get the technical prototype working.

First, you need to make a summary of what work went into the prototype. You should be very detailed. You should submit a report that documents the activities of your team members. For each team member, you should include the following:

  • Exactly what activities the team member was involved in during the development of the prototype.
  • How many hours over the past two weeks that team member spent on each of those activities
  • An assessment of whether these activities were a valuable use of that team member's time. If they were not, what could that team member have been doing instead?

Once you have finished the report for the gameplay prototype, you should layout your plans for the next stage, the technical prototype. The technical prototype is like the gameplay prototype, except that it needs to be a more polished piece of software and should show off some substantial engineering/developement challenge. For each team member, you should again describe their responsibilities (in detail) as well as how much time the should be spent on each responsibility. Remember, this should add up to 10 hours a week. Obviously, you do not need to assess whether the responsibilities you assign are correct yet -- you will not know this until the next two week report. However, you consider the lessons you learned from the gameplay prototype in assigning responsibilities for the technical prototype.

Submit the file report by Saturday, March 1st at 11:59pm through CMS. It may either be a text file (txt), a Microsoft Word file (doc), or a PDF file (pdf).