You have already chosen your path: a software project with your team, or a portfolio of work you have made. Today you turn that choice into a plan you can actually finish: a clear scope, a few milestones, and the first piece of real work started. You will not finish the whole thing today. You will leave with a plan and something underway that you can reopen next time.
A plan you can actually finish answers three questions before you build or collect anything:
- What exactly am I making or collecting? One clear sentence.
- What will I have done by each checkpoint? Three milestones written so someone else could tell if you hit them.
- What could go wrong, and what is the backup? One risk and one simple backup.
Scope means cutting as much as adding. If a feature or an extra portfolio piece would make the plan unrealistic, leave it out now and note it as a stretch idea for later.
Scope: A micro:bit classroom temperature logger that shows the reading on the LED screen and saves values over a lesson.
Risk: micro:bit not available. Backup: use the online simulator and note the swap.
Scope: Four pieces (Arcade game, website, Python list program, one studio build), each with a short learning note.
Risk: a file is missing. Backup: rebuild a small version from notes, or swap in another saved build.
Open one piece of earlier work you already have (a saved game, website, micro:bit or Python file, or your portfolio folder if it exists). Leave it on screen so you can see what you are building on.
Unlock the full learning experience
You're previewing this lesson. Get full access to this lesson and hundreds more — each one ready to teach, with interactive activities, printable resources and pupil progress tracking built in.
This lesson is copyright of Coding Ireland 2017 - 2026. Unauthorised use, copying or distribution is not allowed.