Skip to content

Code Club Activities

Day 5 – Planning and Running a Mini Code Club

These activities support the Day 5 lesson plan: Micro:bit Part 2, Code Club introduction, choosing and planning a first session, and running a short “mini Code Club” with peers.

Activity 1: Micro:bit Part 2 – Radio and Variables (Optional Depth)

Objective

Use the radio blocks (if available) and variables to build a slightly more complex Micro:bit project (e.g. simple game or message sender).

Instructions

  1. Radio (two Micro:bits): In MakeCode, open Radio. Radio set group to the same number (e.g. 1) on both Micro:bits. On Micro:bit A: on button A pressed → radio send number 1 (or radio send string "Hi"). On Micro:bit B: on radio received (number or string) → show string "Got it!" or show number received. Flash both; press A on one and see the other react.
  2. Variables and scoring: In a simple game (e.g. dice or reaction), use a variable score. When something good happens, change score by 1 (or by dice value). When button B pressed, show number score. Optionally: when score ≥ 5, show icon and reset.
  3. One substantial project: Choose one: (a) two-Micro:bit message sender/receiver, (b) simple game with score (dice, reaction, or catch), (c) data logger idea (show temperature every 5 s when button held). Plan it in pairs; implement in MakeCode; test in simulator and on device if time.

Discussion

  • How could “radio” be used in a classroom (e.g. voting, sending codes, teamwork)?
  • How do variables help in games and data?

Note for Facilitators

If radio or extra Micro:bits are not available, focus on variables and one “deeper” project (game or data idea) only.

Activity 2: What is Code Club? – Aims and Structure

Objective

Agree on a shared understanding of Code Club: what it is, who it’s for, and how a typical session runs.

Instructions

  1. Read or summarise the “What is Code Club?” and “Typical Code Club Session” sections from code-club-guide.md.
  2. In small groups: List 3 things that make Code Club different from a “normal” lesson (e.g. project-based, learner pace, volunteer/facilitator role, optional, creative).
  3. Share: One point from each group. Facilitator adds: same tools (Scratch, Micro:bit) as the workshop; fits DBE coding/technology outcomes.
  4. Quick vote or show: Who might run a Code Club in their school? (Hands up or sticky note.) Note: no pressure; the aim is to know what’s possible.

Discussion

  • How could Code Club support your formal curriculum rather than replace it?
  • What would your school need to say “yes” to a Code Club? (Venue, time, approval, equipment.)

Activity 3: Browse and Choose a First Project

Objective

Find and choose one Code Club (or similar) project to use as the “first project” in your mini Code Club session this afternoon.

Instructions

  1. Browse: Open Code Club project pages (e.g. Scratch or Micro:bit). Or use project templates from Day 1 (Scratch) or Day 4 (Micro:bit). Skim 2–3 possible “first” projects.
  2. Choose one that: (a) you can complete in about 30–45 minutes with learners, (b) matches your context (Scratch-only or Micro:bit available), (c) has clear steps.
  3. Note: Project name, link or source, and in one sentence: “Learners will …” (outcome).
  4. Pair share: Tell a partner which project you chose and why. Partner gives one suggestion (e.g. “Add a challenge for fast finishers” or “Print the first page for those without internet”).

Discussion

  • What makes a good “first” project for a new club? (Clear steps, achievable, fun, one main concept.)
  • How will you support learners who get stuck without giving the answer? (Prompt questions, “what have you tried?”, pair support.)

Activity 4: Plan Your Mini Code Club Session (30–45 min)

Objective

Write a short session plan for the mini Code Club you will run in the afternoon: timing, steps, and differentiation.

Instructions

  1. Use the structure from code-club-guide.md: Welcome (5 min), Project time (30–40 min), Share (5–10 min), Wrap-up (2–5 min).
  2. Fill in:
  3. Welcome: What will you say? (e.g. “Today we’re doing [project name]. By the end you’ll have …”)
  4. Project: Which project? Link or handout? Will you demo the first step or let them start from the sheet?
  5. Share: How will you choose who shares? (Volunteer, random, “who got to step X?”)
  6. Wrap-up: What will you say? (Next week, optional challenge, thank you.)
  7. Differentiation: One idea for someone who finishes early (extension). One idea for someone who is stuck (e.g. pair with a buddy, simplify to first 3 steps only).
  8. Optional: Use or adapt first-code-club-session-template.md if available.

Discussion

  • What might go wrong in your first real session? (Time, tech, behaviour.) One thing you’ll do to prevent or handle it.
  • How will you record who attended and what they did? (Register, tick list, photos with permission.)

Activity 5: Run a Mini Code Club (Peer Practice)

Objective

Facilitate a short Code Club-style session (about 30–45 min) with other participants as “learners,” using the project you chose.

Instructions

  1. Roles: One person = facilitator; rest = learners (they follow the project and may “get stuck” or “finish early” to simulate real behaviour).
  2. Facilitator: Run the session as planned (welcome, project time, share, wrap-up). Don’t over-teach; support when asked; encourage sharing.
  3. Learners: Do the project as if you were a learner (you can ask for help, pretend to be stuck, or finish and ask for an extension).
  4. After the session: Quick round: What worked? What was hard? What would you do differently in a real school Code Club?
  5. Optional: Swap and let someone else facilitate a different project (if time).

Discussion

  • How did it feel to facilitate vs. to be a “learner”?
  • What will you take from this into your first real Code Club session?

Note for Facilitators

Keep time strictly so everyone gets a turn to facilitate or to participate meaningfully. If large group, you can have 2–3 mini clubs in parallel (each with one facilitator and 3–5 learners).

Activity 6: Action Planning – My Next Steps

Objective

Write down 2–3 concrete next steps for using Scratch, Arduino, and/or Micro:bit in your school (lessons and/or Code Club).

Instructions

  1. Use resources/templates/integration-planning-template.md or a simple list.
  2. Include at least:
  3. One thing you will do in the next 2 weeks (e.g. try one Scratch/Micro:bit lesson with one class; speak to principal about Code Club).
  4. One thing you will do in the next term (e.g. run first Code Club session; plan one Arduino project with Grade 6).
  5. One resource you will use (e.g. Day 4 project templates, Code Club Micro:bit project, Day 3 wiring diagrams).
  6. Share one step with a partner. Partner asks one question or gives one encouragement.
  7. Optional: Collect contact details (with permission) to stay in touch or share resources later.

Discussion

  • What support do you need to make these steps happen? (School, district, peer, online.)
  • How will we celebrate when you’ve run your first Code Club or first lesson? (Photo, certificate, WhatsApp group, next workshop.)

Notes for Facilitators

  • Activity 1 can be shortened if time is short; focus on variables and one “deeper” project rather than radio.
  • Activities 2–4 prepare for the mini Code Club (Activity 5); keep the plan realistic (one project, clear structure).
  • Activity 6 ties to certificates and evaluation; ensure everyone has time to write at least 2–3 steps and share once.