Plan
Planning means writing what the program must do before writing any code — inputs, outputs, and one sentence describing success.
Nine modules of skills, one idea of your own, and a year to point at.
The capstone is a student-chosen project built in stages over eight sessions: plan it, build the smallest working version, add features one at a time, test it on a real person, then demonstrate it and explain the code out loud.
Explaining your own code is the truest test of understanding there is. A project a child can walk an adult through is worth more than a folder of finished exercises.
Three core ideas, each taught with worked examples and then practised until it feels obvious.
Planning means writing what the program must do before writing any code — inputs, outputs, and one sentence describing success.
Building in stages means always having something that runs. Add one feature, test it, save it, then add the next. Never break everything at once.
Demonstrating means showing the program working and then answering “why did you write it that way?” — the question that separates copying from understanding.
Professional teams call the smallest working version a “minimum viable product”. Students build one in session two, long before they have heard the phrase.
“Bigger project, better grade.” A small program that works perfectly and is fully understood beats an ambitious one held together with hope.
Sessions 65–72 of the 72-session year, at two one-hour sessions per week.
Where this module fits, what you will build, and a hands-on starter that gets everyone curious about plan.
Guided teaching on plan, worked through together with the teacher.
Independent practice, small challenges and one deliberate mistake to diagnose.
Guided teaching on build in stages, building directly on the previous two sessions.
Applied tasks that combine plan and build in stages in one piece of work.
Demo and explain code introduced and practised, completing the toolkit needed for the project.
Guided build session for the module project: Original Python game or learning tool.
Finish, test against the checklist, present the work and explain the decisions behind it.
Every module ends with something the student built themselves and can demonstrate. This is the piece that goes into their portfolio and gets explained out loud at the end of session 72.
Before coding, describe your project to someone in exactly three sentences: what it does, who it is for, and how you will know it worked.
Students finishing Module 9 can:
The vocabulary introduced here, in plain language:
6 quick questions drawn from this module — vocabulary, the project you build, and a myth-or-fact round. Every wrong answer explains itself, so a mistake still teaches you something.
Tell us your child’s class and what they enjoy. We will suggest the closest program fit—no pressure and no upfront payment.