Assignment 12
Document Revisions

Now that you are back from your extended break, you need to start moving forward on your next release milestone. To give you some time to work on it, we want you to spend this week working on revising your documents.

To keep you from being overwhelmed, we have actually spread the due dates of these documents out a bit. However, the most important due date is the one for the Concept Document. This push is the final version of the Concept Document. Your grade on this version of the document will be your final one.

Workflow Document (Wednesday, April 8th)

The first thing we need from you is an updated Workflow document. This document will continue to be a perpetual document inside the team’s Google Drive. It should be updated immediately (or even a “Workflow 2” could be created) to reflect new functions, jobs, and expectations now that the team is entirely virtual. In particular, you should address the following issues.

Team Integrity

There are two important questions to answer.

• Who will be staying in the team?
• Who will be switching to S/U grading?

If someone is dropping, review your team roles and make sure that have enough people to cover the necessary parts of your game. If not, please contact the instructors immediately about renegotiating the scope of your game.

For anyone staying but switching to S/U,they need to declare very clearly their intended hours each week and their level of commitment to the game’s development. It is fine to step back from responsibilities, but the whole team needs to understand.

Team Roles

With team integrity more in the clear, it may be time to reassign or re-imagine roles (We know that some Project Leaders will not be able to move forward with their roles, for example). The team may decide to scuttle traditional Project Leader roles and work in a more “flat” hierarchy, and that would need to be very detailed.

With that said, it is okay if you keep your structure as is.

Consequences and Praise

With integrity and roles in place, revisit the consequences for missing internal deadlines and course deadlines. Remember to be gracious but realistic with your expectations of yourself and your colleagues.

Concept/Gameplay (Saturday, April 11th)

The next round of documents are your game-design related documents.

• concept document
• gameplay specification

The concept submission is not optional, unless you like your grade on the previous draft. The gameplay revision is semi-optional. If you absolutely feel like you must skip this step so that you can finish your milestone, you may. We do not recommend this, as this week counts as your second revision for gameplay. If you do not submit it, you will not get an additional revision.

Technical Specifications (Saturday, April 18th)

• architecture specification
• design specification

Once again revision is semi-optional. However, the due date is after the pre-beta milestone and so it should be feasible. We particularly do not recommend skipping your revision on the architecture specification, since those grades are so univerally low. You will likely need all three revisions of that document.

Submission

Workflow Due: Wednesday, April 8th at 11:59 pm
Concept Due: Saturday, April 11th at 11:59 pm
Technicals Due: Saturday, April 18th at 11:59 pm

Because of the due dates of these documents are spread out, there are no new assignments for your revisions. Instead, we will give you an extension in CMS for the original assignments. You will submit your revision there in place of your original submission.