Building big programs in small stages

Computing · Programming · ages 17-18

Name ______________________ Date ____________

What is a small backlog?
- An ordered list with the next stage on top
- A pile of finished printouts
- A single unchangeable plan
What must every stage leave behind?
- A broken build
- A program that still runs
- An empty folder
What does refactoring change?
- What the program does
- The code shape, not its behaviour
- The project aim
How do you choose the next stage?
- Roll dice
- Pick the slice with the best reason
- Always pick the easiest
Stage one of a quiz program ends. What should run?
- Ask one question and check the answer
- The full league tables and graphics
- Nothing until stage five
Refactor once the code shape has drifted, while everything still works.
Circle one: True False
A plan adds three features at once and the run breaks. What is the repair?
- Add a fourth feature quickly
- Stop testing entirely
- Split into single slices that each keep it running
New changes feel harder though tests pass. What is due?
- A bigger aim
- Refactoring the drifted shape
- Deleting the backlog

Answer key

For grown-ups. Fold this page away before handing over the rest.

An ordered list with the next stage on top · Order shows what you build now and why it beat the rest.
A program that still runs · Running ground lets each new stage build on proof.
The code shape, not its behaviour · Tidying keeps future stages easy without shifting features.
Pick the slice with the best reason · The winner unlocks work, cuts risk, or delivers value.
Ask one question and check the answer · A walking skeleton does the simplest end to end job.
True · Timely tidying keeps later stages fast.
Split into single slices that each keep it running · One slice per stage keeps faults attributable.
Refactoring the drifted shape · Hard changes on green tests signal structural drift.