Computing · Year 7

Active learning ideas

Events and User Interaction

Active learning works for events and user interaction because students must see, test, and revise how code responds to real-time input. Hands-on programming turns abstract triggers into visible outcomes, helping Year 7 students grasp that events wait for user actions before executing. This approach builds confidence as students immediately see cause and effect in their own projects.

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

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

Activity 01

• Experiential Learning
• 35 min · Pairs

Pair Programming: Key Press Dodge Game

Pairs create a sprite that moves left or right when arrow keys are pressed to dodge falling objects. One partner codes the event blocks while the other tests and suggests changes; swap roles after 10 minutes. End with a class share-out of best features.

Analyze how different events can initiate actions in a Scratch program.

Facilitation Tip

During Pair Programming, circulate and ask each pair to explain which event block controls their sprite’s movement before they test it, reinforcing the connection between code and outcome.

What to look for

Provide students with a simple Scratch project that uses 'when key pressed' and 'when sprite clicked'. Ask them to write down: 1. Which event block makes the sprite move left? 2. Which event block makes the sprite say 'Hello!'? 3. What would happen if we changed the 'when key pressed' to 'when green flag clicked'?

• Apply
• Analyze
• Evaluate
• Self-Awareness
• Self-Management
• Social Awareness

Activity 02

• Experiential Learning
• 45 min · Small Groups

Small Groups: Click-to-Score Quiz

Groups build a quiz where clicking correct sprite answers advances to the next question and adds points. Use 'when sprite clicked' events chained with broadcasts. Groups demo their quizzes and vote on the most engaging one.

Design an interactive game in Scratch that responds to user input.

Facilitation Tip

In Small Groups, ask students to swap projects halfway through and predict how the Click-to-Score Quiz will react to clicks before testing it themselves.

What to look for

During pair programming, circulate and ask students: 'What event is making this sprite change color?' or 'If you wanted the ball to bounce when clicked, which event block would you use and why?'

• Apply
• Analyze
• Evaluate
• Self-Awareness
• Self-Management
• Social Awareness

Activity 03

• Experiential Learning
• 30 min · Whole Class

Whole Class: Event Remix Challenge

Project a shared Scratch file with basic events. Students suggest and vote on additions like 'when space key pressed' for jumps, then implement as a class. Discuss how events make the program more interactive.

Compare the use of 'when key pressed' versus 'when sprite clicked' events.

Facilitation Tip

For the Whole Class Event Remix Challenge, provide a starter project with broken or missing events so students focus on debugging rather than starting from scratch.

What to look for

Pose the question: 'Imagine you are designing a simple drawing app in Scratch. What events would you need to program to allow a user to select a color and draw a line?' Facilitate a brief class discussion on their ideas.

• Apply
• Analyze
• Evaluate
• Self-Awareness
• Self-Management
• Social Awareness

Activity 04

• Experiential Learning
• 25 min · Individual

Individual: Personal Event Diary

Students remix a template to log daily events by clicking sprites or pressing keys to change backgrounds and add notes. Export and reflect on how events captured their choices effectively.

Analyze how different events can initiate actions in a Scratch program.

Facilitation Tip

For the Individual Personal Event Diary, model annotating one event block with a sticky note that explains its purpose before students begin.

What to look for

Provide students with a simple Scratch project that uses 'when key pressed' and 'when sprite clicked'. Ask them to write down: 1. Which event block makes the sprite move left? 2. Which event block makes the sprite say 'Hello!'? 3. What would happen if we changed the 'when key pressed' to 'when green flag clicked'?

• Apply
• Analyze
• Evaluate
• Self-Awareness
• Self-Management
• Social Awareness

A few notes on teaching this unit

Start by demonstrating how events wait for triggers using a simple starter project. Avoid overwhelming students with too many event types at once. Focus on one or two per activity, then gradually introduce more through comparison and discussion. Research shows students learn best when they observe immediate feedback, so prioritize quick testing cycles over long explanations. Use collaborative debugging to normalize mistakes as part of learning, not failures.

Successful learning looks like students confidently linking events to actions, choosing appropriate triggers for user control, and explaining why one event type works better than another. They should debug simple issues independently and collaborate to remix projects with layered interactions. By the end, students can design a small interactive program from scratch using at least two different event types.

---

Watch Out for These Misconceptions

• During Pair Programming, watch for students who assume the Key Press Dodge Game runs automatically without their input.

  Remind pairs to test the project before coding, pointing out that the character only moves when they press a key. Ask them to observe the script area to see which blocks light up when the key is pressed.

• During Small Groups, watch for students who believe all events work the same way regardless of type.

  Have groups compare the Click-to-Score Quiz’s 'when sprite clicked' event with a 'when green flag clicked' event from their starter project. Ask them to describe what happens when each is triggered and why the results differ.

• During Whole Class Event Remix Challenge, watch for students who think only one event can control a sprite at a time.

  Direct students to layer events in their remix, such as adding a 'when key pressed' event to change direction and a 'when sprite clicked' event to change color. Ask them to test both events on the same sprite to observe simultaneous control.

---

Methods used in this brief

• Experiential Learning