User stories
A user story states who wants what and why: “As a student, I want to save my timetable so that I stop forgetting Thursday.” It keeps features honest.
Python for Kids · Class 7 · Module 9 of 9
Class 7 Capstone
Build something a real person would actually use.
8 sessionsSessions 65–72
4 weeksTypical pace
Foundation to IntermediateLevel
Class 7Python & Coding
The big idea
The Class 7 capstone starts with a user, not with code. Students write user stories, build to meet them, then hand the program to a classmate and fix whatever that classmate struggles with.
Why it matters
Peer testing teaches the humbling, essential lesson that obvious-to-the-builder is rarely obvious to the user.
Unpacked
What you will actually learn
Three core ideas, each taught with worked examples and then practised until it feels obvious.
Building
Building means turning each story into working code, one at a time, with the program running at the end of every session.
Peer testing
Peer testing means watching someone use it in silence. Every question they ask is a note for your next version.
Did you know?
Usability research shows testing with just five users uncovers around 85% of the problems in an interface. You do not need a crowd — you need five honest people.
Common mix-up
“They used it wrong.” If several people use it the same wrong way, the program is the thing that needs changing.
Session by session
Your 8-session journey
Sessions 65–72 of the 72-session year, at two one-hour sessions per week.
- 1
Warm-up and big picture
Where this module fits, what you will build, and a hands-on starter that gets everyone curious about user stories.
- 2
User stories
Guided teaching on user stories, worked through together with the teacher.
- 3
User stories — practice lab
Independent practice, small challenges and one deliberate mistake to diagnose.
- 4
Building
Guided teaching on building, building directly on the previous two sessions.
- 5
Building — practice lab
Applied tasks that combine user stories and building in one piece of work.
- 6
Peer testing
Peer testing introduced and practised, completing the toolkit needed for the project.
- 7
Project build
Guided build session for the module project: Useful console application.
- 8
Test, present and reflect
Finish, test against the checklist, present the work and explain the decisions behind it.
Project lab
Useful console application
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.
Try this at home
Watch someone use your program without helping or explaining. Write down every moment they hesitate. That list is your to-do list.
It is finished when
- It works from start to finish without breaking
- You can explain every part of it in your own words
- You tested it and improved at least one thing afterwards
- Someone else used or understood it without your help
By the end of this module
Students finishing Module 9 can:
- Explain and use user stories without prompting
- Explain and use building without prompting
- Explain and use peer testing without prompting
- Build and finish useful console application
- Test your own work and correct what you find
- Talk an adult through what you made and why
Word bank
The vocabulary introduced here, in plain language:
- user story
- A short statement of what a user needs and why.
- usability
- How easily a real person can use your program.
- feedback loop
- Testing, learning and improving in rounds.
Module challenge
Think you have got this?
0 XPLevel 1 · Curious Beginner
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.
Your child's free trial is one message away.
Tell us your child’s class and what they enjoy. We will suggest the closest program fit—no pressure and no upfront payment.