teaching machines

CS 491 Project Milestones

January 16, 2017 by . Filed under gamedev for learning, specifications, spring 2017.

This semester you and your team will be dropped into a box. Calories will be dropped in one side of the box, and a game will pop out the other. The game will meet a call-for-games challenge issued by Filament Games. The game should be fun but also help its players achieve certain learning objectives.

To help structure your progress, your box is actually expected to pop out four versions of your game in various stages of completion. These milestones and their due dates are described below.


Your first milestone is a prototype of your game on paper and in some digital experiments. It should allow you and your playtesters to test out the game’s mechanics, visualize the user interface and level design, and help you piece together a coherent sequence of play.

Deliverables include the following:

The central purpose of the prototype is to fail fast—to find issues in your design before you’ve committed too much time into them and become their slave.

Due February 9. You have three weeks for this milestone.

Vertical Slice

The second milestone is a digital prototype of a single playable level of your game. Its assets are probably rough stand-in shapes and sprites. It lacks main menus, music, and other non-primary interface elements. Avoid tackling horizontal concerns; we aren’t interested in a cohesive whole at this point.

Deliverables include the following:

The central purpose of the vertical slice is to familiarize yourself with the game engine by applying it to a contained portion of your game.

Due March 9. You have four weeks for this milestone.


The third milestone is an alpha version of your game. There may be bugs and incomplete features, but the all mechanics should be in place, and at least half of the levels should be functional.

Deliverables include the following:

The central purpose of the alpha version is to provide playtesters a feel for the overall structure of your game. Along the way, you will almost certainly develop tools and workflows that allow you to scale your efforts across levels.

Due April 20. You have four weeks (not including spring break) for this milestone.

Final Build

The fourth milestone is a build of your game that you can ship to your stakeholders (Filament Games) for evaluation. All levels should be complete, with a cohesive narrative gluing together the gameplay. In addition to the core gameplay, sound and visual effects should be present to give your game polish.

The central purpose of the final build is to tie together all your ideas, art, and code into a package that you can deliver with reasonable confidence to your players.

Due finals week. You have four weeks for this milestone.