Prototype Rubric
Use this rubric to guide your work and understand how your Scratch prototype will be graded. Your prototype demonstrates your game’s core mechanics and is the playable version of your concept. Aligned to CSS.68.CT.2 (sequencing), CSS.68.PCI.1 (events & conditionals), CSS.68.PCI.3 (debugging).
Game Design (25 points)
| Criteria | Excellent (25) | Proficient (20-24) | Developing (10-19) | Beginning (0-9) |
|---|---|---|---|---|
| Design Document | Complete design document with game concept, objectives, rules, and target audience clearly described. | Design document covers most elements. | Design document is incomplete or vague. | Design document is missing or unclear. |
| Core Loop | A single main action repeats with clear purpose, driving the player to keep playing. | Core loop exists but purpose is slightly unclear. | Core loop is hard to identify or doesn’t repeat. | No clear core loop. |
| Win/Lose Conditions | Clear rules define exactly how a player wins and loses. | Win/lose conditions exist but are slightly vague. | Conditions are confusing or incomplete. | No win/lose conditions defined. |
Scratch Implementation (40 points)
| Criteria | Excellent (40) | Proficient (30-39) | Developing (15-29) | Beginning (0-14) |
|---|---|---|---|---|
| Sprites & Backdrops | Multiple sprites with distinct costumes are used; at least one backdrop clearly sets the scene. | Several sprites used with basic costumes. | Limited sprite use or no backdrop. | Single sprite or no customization. |
| Events & Broadcasts | At least one event block (when flag clicked, when key pressed, when sprite clicked) triggers gameplay; or uses a broadcast to trigger another sprite. | Events used but limited variety. | Event exists but doesn’t drive gameplay. | No event blocks used. |
| Conditionals & Loops | Uses at least one if block and one loop (forever or repeat) to control game behavior. | Either conditional or loop present, not both. | Basic blocks present but logic is unclear. | No conditionals or loops used. |
| Variables | At least one variable tracks score, lives, or another key game state. | Variable exists but doesn’t affect gameplay. | Variable used but value never changes. | No variables used. |
| Controls & Input | Controls match actions (e.g., arrow keys move the player character). | Controls work but feel awkward. | Controls are unclear or inconsistent. | No working controls. |
Visual & Audio Design (15 points)
| Criteria | Excellent (15) | Proficient (12-14) | Developing (6-11) | Beginning (0-5) |
|---|---|---|---|---|
| Graphics | Consistent visual style; sprites and backgrounds are customized and clearly represent the game. | Graphics present with some customization. | Default Scratch sprites used without changes. | Little or no visual effort. |
| Audio | Sound effects or music enhance the experience and respond to gameplay (e.g., sound plays on collision). | Audio is present but doesn’t clearly respond to gameplay. | Audio or visual feedback is present but minimal or unrelated to gameplay. | No audio or visual feedback used. |
Technical & Polish (20 points)
| Criteria | Excellent (20) | Proficient (15-19) | Developing (8-14) | Beginning (0-7) |
|---|---|---|---|---|
| Functionality | Game runs without critical errors. The main mechanic works during play. | Game works with minor issues that don’t break gameplay. | Noticeable bugs or the main mechanic doesn’t function well. | Game does not start or crashes immediately. |
| Start & End States | Game has a clear start state (green flag resets score/lives) and a clear end state (win screen or game-over screen). | Start or end state missing. | States exist but are unclear. | No defined start or end states. |
| Teamwork | All team members contributed to the Scratch project; work was shared equitably. | All members contributed but unevenly. | One member did most of the work. | Project not shared with team or solo work only. |
Total: ___ / 100
Last updated on