Computing · Year 7

Active learning ideas

Introduction to Block Programming (Scratch)

Active learning works for Scratch because students need to physically drag, snap, and test blocks to grasp core programming concepts. Hands-on exploration builds muscle memory for sequencing and problem-solving, turning abstract ideas like loops and events into tangible experiences that stick longer than passive explanation.

• National Curriculum Attainment Targets
• KS3: Computing - Programming and Development

• 30–50 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Flipped Classroom
• 30 min · Pairs

Block Exploration: Category Hunt

Students open Scratch and select one sprite. They drag blocks from each category (motion, looks, sound, control, events) to the scripts area, predict effects, then test by clicking the green flag. Pairs discuss and note one key purpose per category in a shared table.

Explain the purpose of different categories of blocks in Scratch.

Facilitation Tip

During Block Exploration, move between groups to gently correct incomplete stacks before students test scripts.

What to look for

Ask students to write down one block category they used today and describe what kind of action it controls. Then, have them explain one difference between Scratch and a text-based language they might have seen (e.g., Python, JavaScript).

• Understand
• Apply
• Analyze
• Self-Management
• Self-Awareness

Activity 02

• Flipped Classroom
• 45 min · Individual

Guided Build: Simple Animation

Provide a storyboard for a sprite walking across the stage and waving. Students sequence motion, control, and looks blocks to match. They add a sound block and test, adjusting for smooth playback before remixing a partner's project.

Design a simple interactive animation using basic Scratch blocks.

Facilitation Tip

In Guided Build, pause frequently to ask students to predict what will happen before they click the green flag.

What to look for

During project work, circulate and ask students to explain their script. For example: 'What does this 'when this sprite clicked' block do? What happens when you use the 'repeat' block here?'

• Understand
• Apply
• Analyze
• Self-Management
• Self-Awareness

Activity 03

• Flipped Classroom
• 50 min · Pairs

Pair Challenge: Interactive Game

Pairs design a basic game where a sprite chases the mouse, using sensing and forever loops. They add scorekeeping with variables. Groups present one feature, explaining block choices to the class.

Compare the Scratch environment to other visual programming tools.

Facilitation Tip

For Pair Challenge, assign clear roles so both partners share the coding work and the debugging talk.

What to look for

Pose the question: 'Imagine you are explaining Scratch to someone who has only ever used a word processor. What are the most important things you would tell them about how it works?'

• Understand
• Apply
• Analyze
• Self-Management
• Self-Awareness

Activity 04

• Flipped Classroom
• 40 min · Small Groups

Comparison Station: Visual Tools

Set up laptops with Scratch, Blockly, and Tynker open. Small groups spend 10 minutes at each, building the same sequence (move forward, turn), then compare interfaces on a Venn diagram.

Explain the purpose of different categories of blocks in Scratch.

Facilitation Tip

At Comparison Station, direct students to physically categorize printed block images to reinforce differences in function.

What to look for

Ask students to write down one block category they used today and describe what kind of action it controls. Then, have them explain one difference between Scratch and a text-based language they might have seen (e.g., Python, JavaScript).

• Understand
• Apply
• Analyze
• Self-Management
• Self-Awareness

A few notes on teaching this unit

Teach Scratch by modeling curiosity and iteration: show how you fix a mistake in front of students to normalize debugging. Avoid rushing to solutions; instead, ask targeted questions like ‘What happens if we swap this block?’ Research shows that immediate feedback from peers during pair work accelerates understanding more than teacher-led demonstrations alone.

Successful learning looks like students confidently identifying block categories, building functional scripts, and explaining how their code works to peers. By the end, they should demonstrate decomposition by breaking tasks into steps and debugging collaboratively.

---

Watch Out for These Misconceptions

• During Block Exploration, watch for students who leave blocks unconnected or assume all blocks run simultaneously.

  Have students test each lone block by clicking it directly in the editor, then ask them to connect it to a stack to observe the difference in behavior.

• During Guided Build, listen for students who say the animation runs without clicking the green flag.

  Pause the class to demonstrate that scripts only run when triggered, then ask pairs to add and test a missing ‘when green flag clicked’ block.

• During Comparison Station, notice students who group blocks by color rather than function.

  Ask students to match printed block images to their correct category labels on the wall, using motion blocks as the first example to anchor their understanding.

---

Methods used in this brief

• Flipped Classroom