Computing · Year 3

Active learning ideas

Introduction to Event-Driven Programming

Active learning helps Year 3 pupils grasp event-driven programming because they experience firsthand how code pauses and reacts to real-time inputs. When students manipulate sprites through clicks or key presses, they build intuition for conditional logic and sequencing in a way that abstract explanations cannot match.

• National Curriculum Attainment Targets
• KS2: Computing - Programming
• KS2: Computing - Algorithms

• 20–45 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Plan-Do-Review
• 30 min · Pairs

Pairs Coding: Sprite Click Reaction

In pairs, students select a sprite and add an 'if mouse clicked then jump' block. They test by clicking different screen areas, then modify to include sound effects. Pairs swap computers to try each other's code and suggest one improvement.

Explain how an 'if-then' statement helps a game respond to a player.

Facilitation Tip

During Pairs Coding, circulate to ensure partners alternate roles every two minutes to keep both engaged with the 'when clicked' and 'if-then' blocks.

What to look for

Provide students with a simple Scratch project where a sprite changes color when clicked. Ask them to write down: 1. What is the event in this program? 2. What action happens when the event occurs?

• Remember
• Apply
• Analyze
• Self-Management
• Decision-Making
• Self-Awareness

Activity 02

• Plan-Do-Review
• 45 min · Small Groups

Small Groups: Event Chain Challenge

Groups build a sequence of three events: key press makes sprite spin, mouse click changes backdrop, loudness sensor triggers speech. They run the program as a team, timing responses, and present the most creative chain to the class.

Compare a sequence that runs once to a loop that waits for an event.

Facilitation Tip

For the Event Chain Challenge, provide colored sticky notes so groups can map out events before coding, preventing tangled logic in their scripts.

What to look for

Ask students: 'Imagine you are designing a game where a character needs to jump when the spacebar is pressed. How would you tell the computer to make the character jump only when the spacebar is pressed, and not all the time?'

• Remember
• Apply
• Analyze
• Self-Management
• Decision-Making
• Self-Awareness

Activity 03

• Plan-Do-Review
• 20 min · Whole Class

Whole Class: Broadcast Event Demo

Project a shared Scratch file. Class calls out events like 'green flag' or 'spacebar'; teacher adds broadcasts live. Students predict outcomes, then vote on code fixes for bugs, reinforcing event connections.

Construct a simple program where a sprite reacts to a mouse click.

Facilitation Tip

In the Broadcast Event Demo, pause after each step to ask students to predict what will happen next, reinforcing the link between triggers and responses.

What to look for

Show students two code snippets: one a simple sequence and one using a 'when this sprite clicked' block. Ask them to hold up one finger for the sequence and two fingers for the event-driven code, explaining their choice.

• Remember
• Apply
• Analyze
• Self-Management
• Decision-Making
• Self-Awareness

Activity 04

• Plan-Do-Review
• 25 min · Individual

Individual: Personal Event Story

Each pupil creates a sprite that reacts to two custom events, such as arrow keys for movement and click for dialogue. They add a short story backdrop and test independently before sharing screenshots.

Explain how an 'if-then' statement helps a game respond to a player.

What to look for

Provide students with a simple Scratch project where a sprite changes color when clicked. Ask them to write down: 1. What is the event in this program? 2. What action happens when the event occurs?

• Remember
• Apply
• Analyze
• Self-Management
• Decision-Making
• Self-Awareness

A few notes on teaching this unit

Teach event-driven programming by starting with tangible examples students can manipulate directly, like clicking sprites to change colors. Avoid overwhelming them with abstract flowcharts—instead, use live coding where you model debugging when events don’t occur as expected. Research shows that young learners solidify concepts when they see immediate, visible consequences of their code, so prioritize projects where actions and reactions are clear and repeatable.

Successful learning looks like students confidently identifying triggers, writing conditional responses, and debugging mismatches between events and actions. By the end of the activities, pupils should explain why their sprite only moves when clicked, not automatically.

---

Watch Out for These Misconceptions

• During Pairs Coding: Sprite Click Reaction, students may assume the sprite moves automatically without a click.

  Ask pairs to deliberately remove the 'when this sprite clicked' block and observe what happens. Redirect them to re-insert the trigger to restore functionality, highlighting the necessity of event triggers.

• During Small Groups: Event Chain Challenge, students might think 'if-then' statements run every frame regardless of input.

  Challenge groups to test their code with no keyboard or mouse input. Have them present why the sprite did not move, guiding them to recognize that conditions require specific triggers to evaluate as true.

• During Whole Class: Broadcast Event Demo, students may believe events occur without player action.

  During the demo, deliberately do not press any keys or click the mouse. Ask students to predict whether the sprite will react, then discuss why the sprite only responds when the designated event occurs.

---

Methods used in this brief

• Plan-Do-Review