Two-Week Report 1
Gameplay Prototype Report
Due: Saturday, March 5th at 11:59 pm
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.
Report Contents
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:
-
The activities each team member was involved in.
-
For each activity, and estimation of how many ours each team member spent.
-
An assessment of whether these activities were valuable.
-
In hindsight, what you could have given this person instead, if anything.
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 that the time that you assign to each team member should add up to about
10 hours a week (e.g. 20 hours over the two weeks). However, there are a lot of
things that you are going to be doing over this period time. You should be very
liberal in how you count the time spent by each team member; include all of the
following:
In essence, we are asking that you take what you predicted in your
milestones and give us a lot more detail for the next
two-weeks. In the milestones, we just wanted a prediction of what the entire group
will accomplish. In the two-week report, we want a individual assignments and a
prediction of the hours that each person will spend on each.
In estimating time spent, you should try to do the best that you can; as part of
the next two week report you will be asked to assess how well you do in
distributing responbilities among your teammates. In particular, you should
use what you learned about your group dynamics in the gameplay prototype
to assign responsbilities for the technical prototype.
Submission
Due Saturday, March 5th at 11:59 pm
through CMS.
You should submit a PDF file called report.
Again, we ask that the file be a PDF so that we cannot annotate it in order to
return it to you with feedback for possible revision. It is fine if you create
the document in a program like Microsoft Word, but you should convert it to PDF
before submission.
|