THE VR SCHOOL
  • Schools & Districts
    • License the academy
    • Free program for your students
    • Request a demo
  • Catalog
    • AI & Data
    • Cybersecurity & Web
    • Programming
    • Health Science
    • All Guilds
    • All courses
  • Families
  • Accreditation
  • Log In
  • Request a demo
  • Home
  • Courses

RLP Video Game Design B — Playtesting, Levels, Launch and the Capstone

Curriculum

  • 5 Sections
  • 23 Lessons
  • Lifetime
Expand all sectionsCollapse all sections
  • Unit 1: Digital Prototypes and Ethical Playtesting
    5
    • 1.1
      Prototypes: Paper, Digital and Hybrid
      50 mins
    • 1.2
      Build: A Greybox Prototype with Pickups, Hazards and a Win State
      50 mins
    • 1.3
      Running an Ethical Playtest
      55 mins
    • 1.4
      Bug Reports and the Iteration Log
      50 mins
    • 1.5
      Prototype v1 and Playtest Report
      50 mins
  • Unit 2: Level Design, Accessibility and Player Experience
    5
    • 2.1
      How Levels Teach: Pacing, Flow and Guidance
      50 mins
    • 2.2
      Build: A Tile-Based Level with Checkpoints and a Following Camera
      50 mins
    • 2.3
      Accessibility Audit: Designing for More Players
      55 mins
    • 2.4
      Build: Accessibility Options — Remapping, Game Speed and Readable Text
      50 mins
    • 2.5
      Level Map, Playtest and Accessible Revision
      50 mins
  • Unit 3: Balance, Monetization and Getting Games to Players
    5
    • 3.1
      Balance: Fairness, Difficulty and the Numbers Behind Fun
      50 mins
    • 3.2
      Build: A Tunable Health, Damage and Drop-Rate System
      50 mins
    • 3.3
      Monetization, Loot Boxes and Fair Design
      55 mins
    • 3.4
      Publishing and Marketing: Web Export, Ratings and the Store Page
      50 mins
    • 3.5
      Balance Chart and Launch Plan
      50 mins
  • Unit 4: Careers and the Capstone Playable Prototype
    5
    • 4.1
      Working in Games: Roles, Crunch, Unions and Contracts
      50 mins
    • 4.2
      Build: Menus, Pause and a Shippable Build
      50 mins
    • 4.3
      Milestone Self-Review: Scope, Schedule and SkillsUSA
      55 mins
    • 4.4
      Career Profile, Résumé and Mock Interview
      50 mins
    • 4.5
      Capstone: Playable Prototype, Showcase Pitch and Reflective Essay
      50 mins
  • Unit 5: Missouri Multimedia Supplement: Producing a Game Trailer
    3
    • 5.1
      Shooting the Trailer: Phone Filming Techniques and OBS Gameplay Capture
      50 mins
    • 5.2
      Editing the Trailer: Timeline Assembly, Clip Controls, Effects, Sound Sync and an Advanced Shot
      50 mins
    • 5.3
      Delivering the Trailer: Playback Testing, Codecs and Exports for Store, Social and Archive
      50 mins

Milestone Self-Review: Scope, Schedule and SkillsUSA

Unit 4  ·  Design Critique & Collaboration Lab  ·  Lesson 18 of 23

Milestone Self-Review: Scope, Schedule and SkillsUSA

AME.D10.2RLP-GAMEB
Student sorts game features into essential, helpful, and optional groups while checking a project timeline.
By the end of this lesson I can…

run a solo milestone review that judges my build against its plan, cut scope to fit the schedule, and explain how career and technical student organizations such as SkillsUSA and FBLA build leadership and technical skill.

Instruction

Studios check progress at milestones: agreed points where a build is reviewed against the plan. A milestone review is not a performance; it is a decision meeting. Is the project on track? What is at risk? What do we cut?

Scope, time and budget. Every project balances three things: scope (what the game includes), time (the schedule) and resources (people and money, which is to say budget). Fix any two and the third is decided for you. If the showcase date is fixed and the team cannot grow, scope is the only thing that can move. In a studio, a slip in schedule costs money directly: every extra week is another week of salaries. That is why producers watch scope so closely.

Do the arithmetic. Suppose you have 5 weeks until the showcase and can work 5 hours a week on the capstone: 25 hours. Your feature list estimates 40 hours. Even if every estimate is right (and estimates are usually low), you are 15 hours over. You must cut or simplify about 40% of the planned work. The earlier you face this, the better the cut: cutting a feature in week 1 saves all its hours; cutting it in week 5 saves almost nothing and leaves it half-built.

How to cut. Sort features into must (the core loop cannot work without it), should (it makes the game much better) and could (nice to have). Build all the musts first, to the point of being playable. Then add shoulds one at a time, keeping the game playable after each. Coulds go on a list called “after the showcase”. Cutting is not failure: a small game that is finished and polished beats a large one that is broken.

How studios run a review. In a typical studio protocol each team gets a few minutes: it states the milestone goal, reviewers play the build in silence, the team reports progress against its task board with estimates versus actuals, reviewers give feedback in the form I noticed… / I wonder… / What if…, and the team names its top risk and what it will cut. The team listens and records; it does not defend. Accepting criticism gracefully and deciding calmly what to act on is one of the most valued skills in the industry.

Your solo version. You run the same review on yourself, with evidence standing in for the reviewers. (1) Write the milestone goal in two sentences. (2) After at least a day away, set a three-minute timer and play the build as a stranger would, without fixing anything, noting what you see; or watch a family member play it silently and take notes. (3) Compare your task board’s estimates with actual hours. (4) Write feedback to yourself in I noticed / I wonder / What if form, each line pointing to evidence: a tester’s note, a bug report, a death map or your timer notes. (5) Name your top risk and what you will cut. Record first, decide afterward, just as a team would.

Leadership and self-management. On a studio team, leadership is not the same as being in charge: it is making sure everyone knows the goal, that every voice is heard, that disagreements are settled on evidence and that commitments are kept, with each area owned by a named person. Working alone you hold every role, so the same habits become self-management: write down who you are “being” for each task (designer, programmer, artist, tester, producer), decide in advance how you will settle your own doubts (for example, test data beats preference), and practice accountability by doing what your plan says or changing the plan early, in writing.

SkillsUSA, FBLA and professional organizations. Career and technical student organizations (CTSOs) let students build leadership, workplace and technical skills, run chapter activities and compete. The SkillsUSA Championships include an Interactive Application and Video Game Development contest, which tests the planning, production and presentation of a game, as well as related contests such as 3D Visualization and Animation and Computer Programming. In Missouri, SkillsUSA Missouri is the CTSO for Skilled Technical Sciences, with nine districts, more than 85 local chapters and nearly 10,000 members, according to the Missouri Department of Elementary and Secondary Education; its State Leadership and Skills Conference has been held at State Technical College of Missouri in Linn. Because Multimedia is a Business, Marketing and Information Technology course, FBLA is also a natural fit: FBLA’s high-school competitive events include Computer Game & Simulation Programming (individual or team), in which members design and develop an interactive game or simulation on a set topic, and Missouri FBLA holds district and state leadership conferences. Membership and competition in both go through a registered school chapter and its adviser, so you cannot enter on your own; whether or not a chapter is available to you, you can read a contest’s current guidelines and use them as a practice brief for your capstone. Beyond student organizations, the IGDA and local developer meet-ups offer mentorship, and game jams, short events in which people make a game on a theme in a few days, are a common way to build a portfolio; join any event or online community only with a parent’s or guardian’s permission.

📖 Read for this lesson

The reading opens over the lesson; close it to come back to exactly where you were. The checks below draw on it.

  • A Milestone Self-Review Packet: Hour Arithmetic, a Scope Cut, Estimates Versus Actuals and Student OrganizationsSLS original packet with an invented solo developer; SkillsUSA contest page, Missouri DESE SkillsUSA and conference pages, FBLA high-school competitive events page and Missouri FBLA home page, retrieved 2026-11-10 · about 3 min

    An invented solo developer’s hour arithmetic, must, should and could sort, estimates-versus-actuals board and solo review time budget, with SkillsUSA, SkillsUSA Missouri and FBLA described from their own and DESE’s pages.

Vocabulary in context

  • milestone review — A meeting at an agreed point where a build is judged against the plan and decisions are made.
  • scope — Everything a project is planned to include.
  • must / should / could — A way to prioritize features by how essential they are.
  • career and technical student organization (CTSO) — A student organization, such as SkillsUSA, that builds leadership and career skills through activities and competitions.

Formative check

Work through these before moving on. They are not graded — they tell you whether the standard below has landed yet.

Fill in the blank

You have 4 weeks at 6 hours a week, which is hours. Your features are estimated at 36 hours, so you must cut about hours.

+50 XP

A family member who playtested your build says your jump feels floaty. What is the most professional response?

Record, don’t defend. Decide afterward with evidence, for example after another tester or a self-playtest.
+50 XP

Which SkillsUSA Championships contest most directly matches planning, building and presenting a game?

It is the contest built around planning, producing and presenting a game or interactive application.

Record your milestone self-review: the goal, the feedback you collected (from a home tester or your own timed fresh-eyes play) in ‘I noticed / I wonder / What if’ form with the evidence for each line, your top risk, and your revised feature list sorted into must, should and could, with hour estimates that fit your remaining time.

0 words
Quick self-check

How confident are you that you can run a milestone self-review and cut scope to fit the schedule?

Not yetVery confident

Practice

Work these on paper or in your notebook, then open Check your answer. Aim for all of Fluency and Application; try at least one Challenge.

Printable version: this unit’s practice workbook (PDF)

Fluency

Build speed and accuracy with the core skill.

  1. Name the three things every project balances, and what follows if two are fixed.
    Check your answer
    Answer: Scope, time and resources (people and money). Fix any two and the third is decided for you.
    If the showcase date and team are fixed, scope is the only thing that can move.
  2. Sort into must, should or could for a platformer whose core loop is run, jump, collect: (a) jumping; (b) a level-select screen; (c) a goal that ends the level; (d) particle sparkles on coins; (e) a pause menu with settings.
    Check your answer
    Answer: (a) must; (b) could; (c) must; (d) could; (e) should (it makes the game much better and supports accessibility).
    Musts are what the core loop cannot work without; build all of them first. Reasonable alternatives with a reason are acceptable for (b) and (e).
  3. Write the three feedback stems used in a studio milestone review, and explain what the team does while it hears them.
    Check your answer
    Answer: I noticed… / I wonder… / What if… The team listens and records; it does not defend, and decides afterward.
    Accepting criticism gracefully is one of the most valued skills in the industry.

Application

Use the skill in context. Show your reasoning.

  1. You have 6 weeks at 4 hours a week until the showcase, and your features are estimated at 30 hours. How many hours must you cut, and what percent of the planned work is that?
    Check your answer
    Answer: Cut 6 hours: 20% of the planned work.
    6 × 4 = 24 hours available. 30 − 24 = 6. 6 ÷ 30 = 0.2. Estimates are usually low, so cutting a little more is wise.
  2. Why does cutting a feature in week 1 save more than cutting it in week 5?
    Check your answer
    Answer: In week 1 none of its hours have been spent, so you save them all; in week 5 most hours are already spent and the feature is left half-built.
    Face the arithmetic early.
  3. Illustrative example: a studio of 4 people costs $1,000 per person per week. How much does a 3-week schedule slip cost? What does this show about why producers watch scope?
    Check your answer
    Answer: $12,000 (illustrative). Every extra week is another week of salaries, so schedule slips cost money directly.
    4 × $1,000 × 3 = $12,000. The rate is an assumed planning figure, not sourced.
  4. Write one line of self-feedback in each form (I noticed / I wonder / What if) for a build where your timed three-minute fresh-eyes play shows you got stuck at the second door for 40 seconds. Point each to evidence.
    Check your answer
    Answer: Model: I noticed I stood at the second door for 40 s in my timer notes. I wonder whether the key behind the crate is visible from the door. What if I moved the key into the door’s sightline and tested with a family member?
    Each line must point to evidence (the timer notes), not opinion.
  5. Working alone, how do you practice the leadership habits the lesson describes? Give three examples.
    Check your answer
    Answer: Write down which role you are being for each task (designer, programmer, artist, tester, producer); decide in advance how you will settle doubts (for example, test data beats preference); keep commitments by doing what the plan says or changing the plan early, in writing.
    On a team, leadership means everyone knows the goal, every voice is heard, disagreements are settled on evidence and commitments are kept.
  6. Name the SkillsUSA Championships contest that matches building a game, and the FBLA event that does. How do students enter either?
    Check your answer
    Answer: SkillsUSA: Interactive Application and Video Game Development. FBLA: Computer Game & Simulation Programming. Both go through a registered school chapter and its adviser; you cannot enter on your own, but you can use a contest’s current guidelines as a practice brief.
    In Missouri, SkillsUSA Missouri is the CTSO for Skilled Technical Sciences; Multimedia is a Business, Marketing and IT course, so FBLA also fits.

Review

Keep earlier skills sharp.

  1. Review (Lesson 4.2): which release-checklist items would you check at a milestone review, even before release?
    Check your answer
    Answer: For example: the game starts from an exported build, the core can be completed, no errors in a full play-through, and a dated backup exists.
    A milestone review judges a build against the plan; testing the actual build is part of that evidence.

Missouri CTE — Multimedia (034356) objectives addressed: MM.WRS.8, MM.FND.4, MM.FIL.2, MM.WRS.4, MM.WRS.2, MM.PRS.7, SL.9-10.1

Instructional focus: Professional collaboration, leadership and project management

Reading

A Milestone Self-Review Packet: Hour Arithmetic, a Scope Cut, Estimates Versus Actuals and Student Organizations

SLS original packet with an invented solo developer; SkillsUSA contest page, Missouri DESE SkillsUSA and conference pages, FBLA high-school competitive events page and Missouri FBLA home page, retrieved 2026-11-10 · SLS original, with paraphrases of SkillsUSA, DESE and FBLA public pages

Why this reading. The lesson asks you to run a milestone self-review, cut scope to fit the hours and describe SkillsUSA and FBLA. This reading gives an invented solo developer’s review packet: the hour arithmetic, the must, should and could sort, an estimates-versus-actuals board with what it implies, feedback stems with examples and the time budget for a solo review. It also describes the student organizations as read on their own and DESE’s pages. SLS original except where cited.

Hour arithmetic (Coral, an invented solo developer)

5 weeks x 5 hours = 25 hours available. Features are estimated at 40 hours, so 40 minus 25 = 15 hours must go, which is 15 / 40 = 37.5% of the plan.

Feature list sorted

ClassFeatureHours
MustCore loop playable14
ShouldSound effects6
ShouldSecond enemy type5
CouldSettings menu4
CouldParticle effects3
CouldOnline leaderboard8

Musts 14 + shoulds 11 = 25 hours: exactly the budget. The coulds (4 + 3 + 8 = 15) go on the after-the-showcase list. Total 14 + 11 + 15 = 40.

Estimates versus actuals (first two weeks)

TaskEstimate (h)Actual (h)
Player movement34
Hazard and restart23
Level 1 layout46
Goal and win state34
Total1217

Actuals ran 17 / 12 = 1.42 times the estimates. If that continues, 25 hours buys only 25 / 1.42 = 17.6 hours of estimated work. The musts alone (14) fit, but only about 3.6 hours of shoulds do: drop the second enemy type as well, or find more hours. That is the risk this developer names in the review.

Solo review time budget (about 15 minutes, after a day away)

MinutesActivity
1Write the milestone goal in two sentences
3Timed fresh-eyes play without fixing anything (or watch a family member play in silence)
3Compare estimates with actuals on the task board
6Feedback to yourself in I noticed, I wonder and What if, each line with its evidence
2Name the top risk and what you will cut

Examples: I noticed the jump lands short of the second platform three times in my timed play. I wonder whether new players see the vanishing coral: my tester walked past it twice. What if the timer paused while a menu is open?

Student organizations (read 2026-11-10)

SkillsUSA. SkillsUSA’s site lists an Interactive Application and Video Game Development contest in its Championships. The national technical standards are the authority and change by year. In Missouri, the Department of Elementary and Secondary Education describes SkillsUSA Missouri as the CTSO for Skilled Technical Sciences, with nine districts, more than 85 local chapters and nearly 10,000 members; DESE’s conference page lists the State Leadership and Skills Conference at State Technical College of Missouri in Linn, with district fall leadership conferences usually in November or December.

FBLA. FBLA’s high-school competitive events include Computer Game & Simulation Programming (individual or team), which gives members the opportunity to design and develop an interactive game or simulation on a specific topic. Missouri FBLA runs district leadership conferences and a state leadership conference.

Eligibility. In both organizations, membership and contest entry go through a registered school chapter and its adviser; a student cannot enter alone. Whether or not a chapter is available to you, a contest’s current guidelines make a useful practice brief for your capstone.

Sources: SkillsUSA, Interactive Application and Video Game Development (skillsusa.org); Missouri DESE, SkillsUSA (dese.mo.gov); Missouri DESE, SkillsUSA Conferences and Championships (dese.mo.gov); FBLA, High School Competitive Events (fbla.org); Missouri FBLA (mofbla.org)

Up NextComplete & Continue →

Leave a Reply Cancel reply

Build: Menus, Pause and a Shippable Build
Prev
Career Profile, Résumé and Mock Interview
Next

© 2026 The VR School | Career content by Wiley | Powered by Sejal Learning Systems.

Join free · Accreditation · Privacy Policy · Terms of Service

Modal title

Main Content