MVP Building
Get a rough first version live. Fast.
The point
Everyone leaves the Saturday sprint with a live URL. Students who finish ideation early may begin the same fast track as soon as they have a team.
Time blocks
3 sections · 30 min- 0–5Live demo
- 5–25Make one thing
- 25–30Keep building
Facilitator cue sheet
Run this block
2 blocks · 60 min · 11 cues
Facilitator cue sheet
Run this block
Saturday · block 01
Vibe Coding 101 + MVP sprint
10:30 AM-11:00 AM · Lead: Workshop Guide
Timebox
0 → 30 min- 0–5Live demoBuild badly on purpose, recover once and publish something small.
- 5–25Make one thingStudents build the smallest page or form a stranger can react to; mentors remove setup stalls.
- 10Mentor checkFind students stuck on setup, spelling or a blank prompt; get one visible result on screen.
- 20Room callTen minutes remain: everyone should have something visible on screen.
- 25–30Keep buildingConfirm every student has something visible, then move into the supported build block.Finish check: Something tangible · Build opened · Next step clear
- 25Room callFive minutes: save the current version and prepare to keep building.
- Any timeCall it outFirst live URL: Show it briefly, award the first-launch patch and praise the speed of shipping.
Say this
“Make one thing a stranger can open and react to. Rough is fine. Get it live before the hour is up.”
Finish line
Every student has something visible and a clear next build step.
If late: Cut the demo explanation. Protect hands-on building.
Saturday · 11:00 AM-11:30 AMWork block · MVP build30 min · show cues↓↑
Lead: Mentors
Timebox
0 → 30 min- 0–20Build with supportStudents keep building while mentors clear tooling stalls and reduce scope.
- 10Mentor checkIdentify every student without a working page and assign one mentor through publication.
- 20–30Publish and collectStop adding features, publish the simplest working version and submit every URL.Finish check: Live or shareable URL · URL collected
- 20Room callTen minutes remain: stop adding features and publish.
- 25Room callFive minutes: submit every live URL through the Wall of URLs path.
Say this
“Keep building. By 11:30, I need a link or the simplest working fallback from every team.”
Finish line
Every student submits a live URL or the simplest tangible fallback.
If late: Cut design and extra features. Protect publication and URL collection.
The deck · 5 slides
PDF ↓
1 / 51In the roomCallouts8 callouts
- Building the real thing
- "Nope. What's the fake version? What can you fake and still learn something?"
- Stuck 20 min on one bug
- "Delete it and re-prompt. Don't debug, redirect."
- Perfecting fonts
- "Is it live? Then stop. Ugly ships now; the offer block improves it next."
- Blocked on tech after trying the first fix
- Escalate. Ambassador for 13 and under, staff for 14+.
- Way ahead
- Let them run. Chicago retro: kids who are ready to rip shouldn't be held to the programming. Give them the Module 3 material early.
- A kid is building a login screen
- Stop them. Nobody needs auth in this sprint. One page that explains the thing and captures an email.
- No URL at the 45-minute sweep
- Mentor sits with them for the rest of the block. This is the one hard gate of the sprint.
- A physical-product kid says this doesn't apply
- Google Form, three fields, live in four minutes. It can take a real order today.
When you see
Call out
- Ops: shadow accounts pre-created. Both retros flagged account setup friction as a top time-waster. [Open: who owns shadow account provisioning per city?]
- Feedback in this sprint is binary: is it live. Nothing about quality, copy, or design.
- Praise shipping speed publicly. Name the first kid with a live link to the room.
- Save substantive critique for the Module 3 teardown, where it has structure around it.