Final game · Milestone 3 of 7 · Peer evaluation

Initial Game Demo Rubric

The first time the prototyped pieces come together in one program.

1. Game Pitch 2. Digital Prototypes 3. Initial Game Demo 4. Alpha Playtest 5. Beta Playtest 6. Final Game 7. Final Game Video

About this milestone

RememberThis is not yet a game. It should demonstrate the game logic: the player controls game objects, and the objects interact according to the rules.

Expect to see

All the key game objects in one program (stand-in shapes are fine)
Player controls working
Game states updating: score, win, lose, power-ups…

Not expected yet

Art or audio
More than one level
Menus or polish

How to score

Enter one whole number for each category, from 5 (best) to 1.
When a category has more than one criterion, weigh them together. If you're unsure, average them and round to the nearest whole number.
The descriptions are anchors, not checklists: pick the column that fits best.
Score what you saw today, not what the team says it will add later.
Most criteria are subjective. Apply your own judgment, but apply it the same way to every team.

Rubric

Criterion	5	4	3	2	1
1. Working game framework
Game objects and interactionsStand-in geometry is fine	All important objects are in, and they interact as the game needs.	Most important objects are in, with interesting interactions.	Most important objects are in, with little interaction.	Some important objects are in, with little interaction.	Few objects; almost no interaction.
2. Complete game logic
Game statesWinning, losing, scoring, power-ups, …	All game states update correctly.	Most update correctly.	Some update.	Few update.	None update.
3. Working player control
Control over game elementsCompared with the final game	The player controls every element the final game needs.	Most elements.	Some elements.	Few elements.	No working controls.
4. Confidence in meeting the deadline
Confidence in meeting the deadlineBased on what you saw today	Very confident the team will finish the game as proposed.	Fairly confident; a few parts still look risky.	Possible with steady work from here on.	Doubtful unless the team reduces its scope.	Not realistic without major changes to the plan.
5. Presentation
Clear demo	Clear, to-the-point demo of the game logic, controls and interactions.	Pointed out the important logic, controls and interactions.	Showed a working demo with some controls and interactions.	Showed some controls and interactions; unclear how they relate to the game.	Showed a program, but not how it becomes the game.
OrganizationDemo flow	Well rehearsed and to the point; everything ready to run.	Organized, with minor hiccups.	Mostly organized; some time lost (e.g., searching for files).	Disorganized and hard to follow.	Could not show the work (e.g., builds missing or not running).
Team participationWho presented	Every member presented a substantial part and knew it well.	Every member presented; some parts were uneven.	Most members presented.	Only one or two members presented.	One member did everything; the others did not take part.

Hints on preparation

You demo, we watch. This is basically the integration of all your digital prototypes in a meaningful way, demonstrating that:

the individual solutions can be integrated into the same system, and
the integrated result shows promise of the system you want to build.

During the game demo, some groups include PowerPoint slides to help direct their audience's attention (and to help them get higher scores).

Guide: you can include

Goal: to remind everyone of your game.

1 slide to remind everyone what your game is about (the level sketch from your pitch can work well)
1 slide to remind everyone of some of the challenges (or the ones you have solved)

Remember, the goal is to remind us what your game is about and show us the game
Keep the presentation short

Don't

Talk at length (the important part is the demo)
End up playing your game while presenting: you are not there to play, you are there to show what has been done