Facilitator Guide: Lesson 4 Coding Games on the micro:bit

TEACHER ONLY · LESSON GUIDE

Facilitator's Guide and Materials: Lesson 4 Coding Games on the micro:bit

Run the lesson here; the student item below remains the independent and absence route.

Daily Learning Contract

Topic: Game algorithms and iterative revision

Objective: Students will apply iterative algorithm development to design, test, and improve an original micro:bit game and explain its rules.

Demonstration of learning: Completed game worksheet, working Rock Paper Scissors program, original-game program, test or revision evidence, and checkpoint.

Before class

Time: One class period
Student route: Learn: Lesson 4 Coding Games on the micro:bit
Use what already exists: Keep existing guide, presentation, worksheet, printable checkpoint, RISE route, and EdPuzzle setup note.

Lesson flow

1. Launch: Launch with a concrete question or failure that makes game logic and iteration matter.
2. Model: Model one current example or tool move before students begin.
3. Do: Guide the first decision together, then release students to the existing Canvas task.
4. Check + support: Check for the named evidence, not completion alone; keep a visual sequence, sentence stems, and purposeful partner roles available.
5. Close + handoff: Collect or verify the evidence and name the next lesson's connection.

Check before students leave

Ask students to point to the specific evidence above and explain one choice, test, or revision. Completion alone is not evidence of understanding.

Support + troubleshooting

Scaffold: Keep the visual task sequence visible, assign purposeful partner roles, and use the sentence stems on the student page before simplifying the task.

When students get stuck: Ask for the exact step where the tool, code, or task stopped. Check setup, inputs, and saved work before replacing the task or lowering the thinking.