Pupils needing extra support

• Could use the Knowledge organiser to help identify and name different error types (syntax, logic and loop errors) before attempting to fix them.
• Could take on the role of running the program and describing what happens on the micro:bit simulator while their partner reads the code aloud, helping them link what they see to specific lines of code.
• Could use the Debugging checklist to work through the code line by line when they are unsure where the bug is.
• Could act as the ‘checker’ once a fix is applied to confirm that the program runs without red error messages.

Pupils working at greater depth

• Should predict the program’s output before running it and justify their reasoning by referring to loop values, indentation and syntax.
• Should evaluate more than one possible cause for a bug and explain why one is the most likely based on how Python executes the code.
• Could create a short buggy Python program (for example, with a syntax, indentation or loop error) for another team to debug.
• Could support other pupils by explaining clearly how a specific fix works and why it resolves the error.