Open Beta Report
Due: Saturday, May 7th at 11:59 pm
This two week-report covers what you did to get ready for public beta release. This report
has exactly the same format of the previous one. You will have another
CATME survey asking how you worked as a group. In
addition, you should fill out a short report documenting what tasks were completed
and what tasks a proposed for the next milestone.
Again, refer to the example below if you are unsure of how to
structure the report. If you received any negative comments about your
previous report, you should address those this time. We do not
want reports to be revised; we always want to be moving forward. However, we will take
off for mistakes that are made twice in a row.
Your report is divided into two halfs: the progress report and predictions for the next
milestone. In the first part, you should begin with a short description of what the
entire group did for these past two weeks. Obviously you worked on the technical prototype,
architecture specification, and design specification. However, did you do anything else
like animation and music? Have you do any playtesting yet?
This description should be no more than a paragraph or two. After this summary, you should
begin a more detailed breakdown for each individual on the team.
For each team member you need to create a subsection. At the start of the subsection you
should give short description of the primary responsbilities of that team member over the
course of this prototype. This needs be no longer than a paragraph.
After this paragraph, provide a table where each row consists of the following:
An individual task that the team member worked on or was supposed to work on
Whether or not this task was completed, and the data completed if appropriate.
The estimate of hours from the previous two week report
The actual of the number of hours spent on that task
This is the same format as the previous report, and will
be the format that we use for the rest of the semester. Again, this is what the
example report does, so you should look at it if you
have any questions.
After the table, you should provide the total number of hours that this person worked
over this reporting period. Please be honest here. We never count off for not working
"enough" hours. However, hours give us an idea of who is being productive and
who is not. This allows us to make suggestions for improvement in later
Once you have finished the report for this release, you should layout
your plans for the final sprint:
Showcase. For the
most part, this sprint is whatever you need to do finish the game. In
addition, Final Document Portfolio is part of this last push. We are not
going to give you much structure other than this. Do what you need to do.
As always, you should try to predict the number of hours that each person will spend on
each activity. The format for the predictions should be exactly the same format as the
activity breakdown. That is, have a subsection for each team member. For each person,
give a short description of their primary responsbility. Then give a bulleted list of
activities with hours.
For each team member, you should describe his or her 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:
Time spent discussing in group meetings
Time spent on the final document revisions
Time spent on the Showcase, final release
Time spent on final playtesting
Time creating the poster and other Showcase assets
In estimating time spent, we again ask that you organize this information into a table.
In each row of the table, you should have the following:
An individual task that the team member is assigned
The internal (team) deadline for completing this task
An estimate of the number of hours that will be spent on the task
A priority value for the task; lower priority tasks are optional
Due: Saturday, May 7th at 11:59 pm
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