Day 26: Prototype & Presentation — Day 2
Day 26: Prototype & Presentation — Day 2
Monday, April 27th, 2026
Work Session
This is the 6th day of this project. Check in with your team right now: what did you get done last time, and what’s left?
What should your team work on today?
Use this priority order to decide who does what:
| Priority | If… | Then work on… |
|---|---|---|
| 🔴 First | Your core mechanic doesn’t work yet | Scratch prototype — get the player moving and one rule working |
| 🟡 Second | The mechanic works but the game isn’t complete | Scratch prototype — add scoring, a win/loss condition, or a second level |
| 🟢 Third | The prototype is in good shape | PowerPoint — finish Slides 1–6 and insert your concept art |
You should not both be doing the same thing. Split up: one teammate on Scratch, one on PowerPoint — unless the prototype urgently needs all hands.
Prototype checklist (Scratch)
If you’re working on the prototype today, focus on these in order:
- Core mechanic — can the player actually do the main thing? (move, jump, collect, shoot, etc.)
- Win/loss condition — does something happen when the player wins or loses?
- At least one sprite and one backdrop — not the default cat on a white screen
- No broken scripts — test every change before moving on
Presentation checklist (PowerPoint)
If you’re working on the presentation today, aim to finish:
- Slides 1–5 fully filled in with your team’s real content (no placeholder text)
- Slide 6 — concept art photo inserted
- Every slide has at least one image or drawing
- Your file is shared with all team members and Mr. Willingham
- My team agreed on who is working on the prototype and who is working on the presentation.
- I made progress on my assigned task and can point to something new since Friday.
- I checked my work against the rubric at least once today.
Standards
- MS-CS-FCP.3.4 — Decompose the game project into manageable parts (prototype mechanic, win/loss logic, slides) and tackle them in priority order.
- MS-CS-FCP.4.5 — Implement a simple algorithm in Scratch to power the game’s core mechanic.
- MS-CS-FCP.4.6 — Build an event-driven program in Scratch that responds to player input.
- MS-CS-FCP.4.8 — Write scripts that use loops to keep game logic running continuously (e.g., a
foreverblock checking for collisions or key presses). - MS-CS-FCP.4.9 — Develop win and loss conditions that make decisions based on game data (score, health, timer, etc.).
Last updated on