Skip to content

Day 4 Assessment Rubric

Coding & Robotics with Micro:bit – Part 1

Overall Assessment Framework

Formative Assessment (Throughout Day)

  • Observation during MakeCode and simulator use
  • Check-ins on buttons, sensors, and LED output
  • Success in downloading and flashing at least one program
  • Participation in robotics-ideas discussion

Summative Assessment (End of Day)

  • At least one working Micro:bit project (e.g. name badge, dice, step counter)
  • Ability to explain inputs and outputs used
  • Daily reflection and self-assessment

Rubric 1: MakeCode and Interface

Component Not Yet (1) Developing (2) Proficient (3) Advanced (4)
Navigating MakeCode Cannot find blocks or run program Finds blocks with help, runs with support Navigates categories and runs programs independently Uses advanced blocks (e.g. pins, radio) with guidance
Simulator use Does not use simulator Uses simulator with guidance Tests and debugs in simulator before flashing Uses simulator to try alternatives quickly
Block selection Incorrect or random blocks Selects basic blocks (show, on start) Selects input, logic, and output blocks correctly Combines blocks for intended behaviour
Saving and naming Does not save or name Saves with reminder Saves and names projects clearly Organises projects for reuse in class

Evidence: Projects in MakeCode, facilitator observation.


Rubric 2: Inputs and Outputs

Component Not Yet (1) Developing (2) Proficient (3) Advanced (4)
LED output No use of LEDs show leds or show string with help show leds, show string, show number appropriately Uses plot/unplot or animation for effect
Buttons Does not use buttons Uses one button with help Uses A and B (and optionally A+B) for different actions Uses buttons for mode switching or menus
Sensors Does not use sensors Uses one sensor (e.g. light) with help Uses at least two (e.g. light, temperature, shake) Uses sensor values in conditions or variables
Pins (optional) Not attempted Attempts with support Writes to or reads from a pin correctly Integrates pin with logic (e.g. motor on/off)

Evidence: At least one project using button + LED output; optional sensor and pins.


Rubric 3: Flashing and Troubleshooting

Component Not Yet (1) Developing (2) Proficient (3) Advanced (4)
Download Cannot download .hex Downloads with step-by-step help Downloads and locates file independently Helps others download and find file
Flashing to device Does not flash or flash fails Flashes with facilitator support Flashes successfully and runs program on device Troubleshoots (cable, drive, copy) independently
Troubleshooting Cannot describe issues Names one issue (e.g. cable) Lists 2–3 common issues and simple fixes Explains or documents steps for others
Safe use Unsafe handling or ejection Ejects with reminder Safely copies file and ejects drive Models safe practice for learners

Evidence: At least one successful flash; optional short troubleshooting list.


Rubric 4: Classroom and Curriculum Readiness

Component Not Yet (1) Developing (2) Proficient (3) Advanced (4)
Curriculum link Cannot identify link Identifies one subject (e.g. Technology) Links to DBE Technology/coding and one other subject Plans a concrete lesson or activity with Micro:bit
Managing devices No idea how to manage Suggests one idea (e.g. pairs) Explains pairing, storage, and sharing of Micro:bits Plans for storage, rotation, and saving work
Differentiation No ideas One idea for different learners Several ideas (simplify/extend by project) Clear plan for mixed abilities and group size
Robotics idea Cannot describe robot use Describes vague idea Describes one concrete “robot” use (inputs/outputs) Plans a classroom robotics project (time, kit, steps)

Evidence: Reflection, robotics-ideas discussion, optional lesson or activity note.


How to Use This Rubric

  • During the day: Use Rubrics 1 and 2 to observe progress in activities and projects.
  • After flashing: Use Rubric 3 to note success and any troubleshooting used.
  • End of day: Use Rubric 4 for reflection and planning for classroom use.
  • Scale: 1 = Not yet, 2 = Developing, 3 = Proficient, 4 = Advanced. “Proficient” for the day: most criteria at 2–3, at least one project flashed and explained.
  • Feedback: Give one strength and one next step (e.g. “Try one project with a sensor” or “Plan one lesson using the dice project”).

Notes for Facilitators

  • If hardware is limited, “Proficient” can be achieved mainly in the simulator plus one shared flash per pair/group.
  • Emphasise saving and naming so teachers can reuse projects in school.
  • Day 5 will add radio, variables, and Code Club; keep Day 4 focused on core inputs/outputs and flashing.