Final game · Milestone 5 of 7 · Peer evaluation

Beta Playtest Rubric

The second (and last) playtest. Remember what you saw at the alpha, and check what changed.

RubricHints on preparationFeedback template
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

Expect to see
  • Changes made since the alpha playtest
  • The game close to its final form
Not expected yet
  • Polish
  • Final art or audio (rough is okay)
  • Perfect stability (an occasional crash is okay)

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

Criterion54321
1. Fun
EnjoymentDid you enjoy playing?Fun; I wanted to keep playing after my turn ended.Enjoyable; I liked testing it.Okay; I didn't mind playing it.Not very engaging; I was ready to stop early.Not enjoyable at all.
Replay valueWould you come back to it?I'd play it again and again (new levels, strategies, scores).I'd play it several more times.I'd play it once or twice more.I'd play it once, to the end.I probably wouldn't finish one play-through.
2. Improvement since the alpha
Feedback addressedWere the alpha comments acted on?The important issues from the alpha are fixed, and suggestions are visibly integrated.Most important issues are fixed.Some issues are fixed; others remain.Few changes; key issues from the alpha remain.No noticeable changes.
Plays betterPlays much better than at the alpha.Plays better.Plays a little better.Plays about the same.Plays worse.
3. Playability
Goal and controlsCould you figure out how to play?I understood the goal and controls from the game itself, without being told.I understood them after a quick hint or reading an on-screen instruction.I understood them after the team explained.I was still unsure about the goal or some controls while playing.I could not tell what to do or how to control the game.
4. Confidence in meeting the deadline
Confidence in meeting the deadlineBased on what you saw todayVery 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.

Written feedback

Along with your scores, post short, clear, polite feedback using the feedback template: start with what works, then name the most important things that don't, with a suggestion for each.

While you play, the playtest questions can help you notice what to comment on: rules, controls, interface, and the moments that were fun or frustrating.

Hints on preparation

During each playtest (alpha and beta), before we begin playing your game, you have a chance to tell us what we should pay attention to.

Watch out!Playtesting time is short: every minute you spend presenting is a minute less for us to test your game! :)

Guide: you can include

Goal: to direct your testers' attention.

  • 1 slide to remind everyone what your game is about (a screenshot from the demo works well here)
  • 1 slide to explain what information you are looking for, for example:
    • How does it feel when the hero jumps?
    • Which of the mechanics do you prefer (with double jump or without)?
    • Does “sliding on ice” feel right?
  • Possibly a slide showing the game controls
Do
  • Remember, the goal is to remind us what your game is about and show us the game
  • Keep the presentation short
  • Include your own survey questions, if you like: no more than 4–6 questions, with easy access (e.g., the QR code from Six God)
Don't
  • Talk at length (the important part is the demo)