Micro:bit Foundations

Overview

In this first unit lesson, students explore Micro:bit hardware and the basics of its software interface. They practice introducing a topic, organizing information with headings, and writing clear, coherent instructions for what they observe.

Learning intentions

Students will be able to:

• Identify key Micro:bit components and describe what each does.
• Navigate the Micro:bit software interface and explain what the main panels show.
• Organize their observations into a short, structured written guide with headings and a simple graphic or table.
• Write a clear claim about how Micro:bit works, supported by evidence from observations.

Success criteria

• I can name at least 4 Micro:bit components and describe their function in one sentence each.
• I can explain what the code blocks/workspace area and the preview/output area are for.
• I can produce a short guide with headings and at least one chart/table or labeled graphic.
• I can write a claim and include evidence from my own observations and examples.

Curriculum links

• Writing: Introduce a topic clearly; organize ideas into broader categories; include formatting/graphics/media when useful (CCSS.ELA-LITERACY.WHST.6-8.2a).
• Writing: Produce clear, coherent writing appropriate to task, purpose, and audience (CCSS.ELA-LITERACY.WHST.6-8.4).
• Writing: Introduce claim(s); distinguish from alternate/opposing claims; organize reasons and evidence logically (CCSS.ELA-LITERACY.WHST.6-8.1a).
• Reading: Analyze how a text is organized into major sections and how that helps understanding the topic (CCSS.ELA-LITERACY.RST.6-8.5).

Lesson structure (45 minutes)

1. 0–5 min · Hook. Teacher displays a Micro:bit and shows a short “before/after” moment (LED display on), then asks, “How do you think this tiny computer shows information?” Students do a quick think-write of one guess.

2. 5–12 min · Micro:bit orientation demo. Teacher points to components (LED matrix, buttons, ports/edge connector, speaker/microphone if present, power method) and models descriptive language. Students use a provided component sheet to label what they see and write a one-sentence “I notice…” for 2–3 parts.

3. 12–18 min · Interface walkthrough. Teacher projects the Micro:bit software and explains the purpose of the main areas (workspace/code blocks, simulation/preview, connection/run controls). Students turn and talk: “Which part helps you test without hardware?” then share one idea.

4. 18–26 min · Structured reading for organization. Teacher hands out a short sample “Micro:bit Explorer Guide” (1 page) with headings and a simple table (e.g., Component → What it does → Evidence). Teacher prompts students to identify major sections and how headings help them understand. Students underline heading purposes and fill in a “What this section does for me” note.

5. 26–38 min · Write an Explorer Guide (draft). Teacher gives a half-page template with required sections: Title/Topic, Components (table), Software Interface (short paragraph), and Claim + Evidence (2–3 bullets). Students draft using their observations; teacher circulates to support clarity and logical order.

6. 38–45 min · Share and quick check. Students do a 2-minute “gallery share” (pairs read one table row and one claim-evidence bullet). Teacher uses a checklist to note who can name components, explain interface areas, and use headings/graphics.

Resources

• Micro:bit devices (enough for groups of 2–3; or teacher demo + stations)
• Printed component labeling sheet and Explorer Guide draft template
• Projector/display for interface walkthrough
• Projected “sample guide” for the organization mini-lesson
• Markers/pens; sticky notes for gallery share
• Labeled example chart/table (Component → Function → Evidence)
• Computer lab access with Micro:bit software open (or preloaded demo mode)

Assessment

• Formative: Teacher listens during think-pair-share and checks component labeling accuracy during step 2.
• Formative: Teacher reviews the draft template for headings, logical order, and at least 4 components described by step 5.
• Formative: Gallery share checklist—students can explain one interface area and one component function.
• Exit ticket (last 2 minutes, optional if time allows): “One claim about how Micro:bit works is… Evidence from my observations is…”

Differentiation

• Support: Provide sentence starters for the guide (e.g., “One component is ____. It helps because ____.” “I think Micro:bit works by ____.”).
• Support: Offer a word bank (component names, function verbs like “shows,” “sends,” “receives,” “connects,” “tests”).
• Extension: Students add an “Alternate idea” bullet (“Some people might think ____; however, in our test/observations ____.”) while staying grounded in evidence.
• EAL/SEN: Allow oral dictation to a partner before writing; accept simplified sentences as long as they include evidence and correct component/function matching.