Micro:bit Innovations

Overview

Students reconnect with Micro:bit and MakeCode by revisiting essential ideas from their 6th grade experience. They explore what changes in 7th grade and use the engineering design process to frame unit goals, then complete a short “What I Remember” coding challenge to activate prior knowledge.

Learning intentions

• Students will be able to explain how signed numbers and opposites behave on a number line and in real-world contexts.
• Students will be able to interpret rational number sums and differences using additive inverses.
• Students will be able to model multiplication/division rules for signed values to interpret quotients as rational numbers.
• Students will be able to use an engineering design process (ask–imagine–plan–try–improve) to guide a small Micro:bit build.

Success criteria

• I can write and explain a rule for how opposite quantities combine to make 0.
• I can interpret a rational number operation (sum or difference) as a real-world situation.
• I can show that dividing integers with a nonzero divisor produces a rational number and explain sign rules.
• I can complete a short Micro:bit coding task and justify the changes I made during improvement.

Curriculum links

• The Number System — understanding additive inverses and opposite quantities (CCSS.MATH.CONTENT.7.NS.A.1a, CCSS.MATH.CONTENT.7.NS.A.1b).
• The Number System — interpreting sums and distances on a number line (CCSS.MATH.CONTENT.7.NS.A.1b, CCSS.MATH.CONTENT.7.NS.A.1c).
• The Number System — extending multiplication/division concepts to rational numbers with signed rules (CCSS.MATH.CONTENT.7.NS.A.2a, CCSS.MATH.CONTENT.7.NS.A.2b).

Lesson structure (45 minutes total)

1. 0–5 min · Welcome + Warm Start. Teacher greets students, shows two quick Micro:bit “before/after” demos (6th grade style vs. new 7th grade style), and asks: “What do you predict will be easier or harder this year?” Students do a quick think-write: one prediction and one question.

2. 5–12 min · Unit Expectations + Engineering Design Process. Teacher introduces 15-day unit flow and explains the engineering design process as the unit framework, emphasizing a cycle of trying and improving. Students track the cycle on an anchor chart and add one example of “improve” from school life.

3. 12–18 min · Mini Math Connection: Rational Words. Teacher connects coding decisions to signed rational reasoning using a simple scenario: “A temperature sensor reading changes by +3°C or -3°C; what does opposite mean?” Students discuss in pairs and answer: “What should the opposite change do?”

4. 18–27 min · Direct Teach: What’s New in 7th Grade (MakeCode Tour). Teacher runs a brief MakeCode tour highlighting where students will find new tools this year (blocks for sensors, improved variables, event handling, and testing workflow). Students complete a one-minute “spot and label” sheet: find (1) where to name a variable, (2) where to run the program, and (3) where to view results (simulator or board output).

5. 27–40 min · What I Remember Challenge (Micro:bit + Quick Rational Reasoning). Teacher gives the challenge:

• Build a program that reads a value from a simple sensor input (or uses an input button), displays an integer on the Micro:bit, and then displays the “opposite” value as a second step.
• Students must also include one rational interpretation in their notes: write what “opposite” means so their results match the sign rule (for example, why +x and -x relate). Students work in pairs: first get any working version, then refine so the sign behavior matches their written explanation. Teacher circulates using a checklist: opposite shown correctly, explanation uses “additive inverse” language, and program runs without errors.

6. 40–45 min · Share Out + Exit Check. Teacher calls for two fast demos and asks each pair: “What did you change when you improved?” Students complete a 2-question exit ticket:

• Q1: “If you add a number and its opposite, what do you get and why?”
• Q2: “If a value is divided by a nonzero integer, is the quotient rational or not? Explain using sign reasoning.”

Resources

• Micro:bit kits and USB cables (or simulator-capable devices if boards unavailable)
• MakeCode editor access (district-provided login if needed)
• “What I Remember” student worksheet (sensor/input option, explanation prompt, checklist)
• Anchor chart: engineering design process cycle
• Markerboard or projector with a sample program
• Printed sign rules card (quick reference: opposite/additive inverse, subtraction as adding the inverse)
• Exit ticket slips
• Pair role cards (Driver / Navigator)

Assessment

• During the MakeCode tour: teacher checks student “spot and label” answers (quick correction).
• During the challenge: teacher uses a 3-point rubric (works, opposite correct, written rational explanation).
• Exit ticket: verifies understanding of additive inverses and rational quotients with sign reasoning.

Differentiation

• Support:
• Provide sentence starters for explanations: “The opposite of ___ is ___ because…”
• Offer a partially completed MakeCode starter template (optional) with only the opposite-display portion missing.
• Use a sign-rule mini card and number-line poster at tables.
• Extension:
• Add a second requirement: display the “distance” between two values on a number line (students justify using absolute value language).
• Ask for an “improve” log entry: one change, one observed effect, one next step.
• EAL/SEN considerations:
• Keep directions in short steps; repeat challenge requirements verbally and on the board.
• Allow students to respond with diagrams (number line arrows) in addition to words.
• Partner students intentionally so each pair has at least one confident navigator and one builder.

Optional Make-to-Teach Notes (for the teacher)

• Emphasize that showing opposites in code is not just “multiply by -1,” but a conceptual additive inverse idea: adding opposite leads to 0 and subtraction turns into adding the inverse.
• When students discuss improvement, prompt them to connect the change to the math idea (“sign was wrong, so I updated the inverse rule”).