Computing · Year 7

Active learning ideas

Sequence: Order of Instructions

Active learning works for sequence because students must physically or visually experience how order changes outcomes. When students arrange instructions themselves, they see firsthand why precise sequencing matters in programming, building lasting understanding beyond abstract explanations.

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

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

Activity 01

• Project-Based Learning
• 35 min · Small Groups

Unplugged: Human Algorithm Relay

Divide class into chains of students. Front student receives simple goal instructions, like 'move forward, turn left, repeat twice.' They pass actions one-by-one down the line, acting as a 'computer.' Discuss order failures, then recreate in Scratch pairs.

Analyze why the order of instructions is critical in a computer program.

Facilitation Tip

During Human Algorithm Relay, have students physically line up and perform each instruction one at a time to emphasize the step-by-step nature of sequence.

What to look for

Provide students with a simple Scratch script (e.g., move, say, change costume). Ask them to draw or write the sprite's final appearance and state after the script runs. Then, ask them to predict what would happen if two specific blocks were swapped.

• Apply
• Analyze
• Evaluate
• Create
• Self-Management
• Relationship Skills
• Decision-Making

Activity 02

• Project-Based Learning
• 40 min · Pairs

Pairs: Predict-Reorder-Test

Provide Scratch scripts with jumbled blocks for a cat dance. Pairs predict outcomes on paper, drag to reorder, run the code, and note differences. Share one key insight per pair with class.

Predict the outcome of a Scratch script if the order of blocks is changed.

Facilitation Tip

In Predict-Reorder-Test, require pairs to sketch their predicted outcome before testing to make their assumptions explicit.

What to look for

Display a short, incomplete Scratch sequence on the projector. Ask students to identify the next logical block needed to achieve a stated goal (e.g., 'make the sprite jump'). Call on students to explain their choice and why that order is important.

• Apply
• Analyze
• Evaluate
• Create
• Self-Management
• Relationship Skills
• Decision-Making

Activity 03

• Project-Based Learning
• 45 min · Small Groups

Small Groups: Loop Dance Builder

Groups design a sprite dance using repeat loops for efficiency. Start with manual repeats, then refactor into loops. Test routines, vote on most elegant code, and explain efficiency gains.

Construct a sequence of blocks to achieve a specific animation goal.

Facilitation Tip

For Loop Dance Builder, ask groups to time their loops and compare efficiency to copy-pasted versions to highlight the value of loops.

What to look for

Pose the question: 'Imagine you are giving instructions to a friend to make a sandwich. Why is the order of your instructions (e.g., putting on bread before the filling) more important than just listing all the ingredients?' Facilitate a brief class discussion connecting this to computer programming.

• Apply
• Analyze
• Evaluate
• Create
• Self-Management
• Relationship Skills
• Decision-Making

Activity 04

• Project-Based Learning
• 30 min · Whole Class

Whole Class: Debug Challenge

Project a buggy Scratch script. Class calls out order fixes step-by-step. Code live, run after each change, and vote on predictions. End with students submitting their fixed versions.

Analyze why the order of instructions is critical in a computer program.

Facilitation Tip

In Debug Challenge, assign roles like 'Order Checker' and 'Behavior Reporter' to encourage systematic troubleshooting.

What to look for

Provide students with a simple Scratch script (e.g., move, say, change costume). Ask them to draw or write the sprite's final appearance and state after the script runs. Then, ask them to predict what would happen if two specific blocks were swapped.

• Apply
• Analyze
• Evaluate
• Create
• Self-Management
• Relationship Skills
• Decision-Making

A few notes on teaching this unit

Teach sequence by starting unplugged to build intuition, then transition to Scratch for concrete practice. Emphasize that computers execute instructions like recipes—not lists of ingredients—so order dictates results. Avoid rushing to loops; first ensure students grasp why repeating blocks manually fails before introducing loop blocks. Research shows that debugging misordered scripts helps students internalize sequence rules more effectively than passive instruction.

Successful learning looks like students confidently predicting and testing how block order affects outcomes, explaining why reordering changes behavior, and using loops efficiently instead of copy-pasting. They should plan sequences logically and debug errors by checking block order first.

---

Watch Out for These Misconceptions

• During Predict-Reorder-Test, watch for students who assume swapping blocks will not change the outcome as long as the same blocks are used.

  During Predict-Reorder-Test, have pairs sketch their expected outcome before testing. When results differ, prompt them to trace the script step-by-step together, asking, 'Which block runs first now? What happens because of that order?'

• During Loop Dance Builder, watch for students who copy and paste blocks to repeat actions instead of using loop blocks.

  During Loop Dance Builder, ask groups to compare the length and readability of their copy-pasted sequences versus looped versions. Challenge them to edit a looped version to add a new repeat and observe how much easier it is.

• During Loop Dance Builder or Debug Challenge, watch for students who assume loops always run forever unless manually stopped.

  During Loop Dance Builder, have students add visible outputs like 'Sprite says the loop count' to observe controlled repetition. In Debug Challenge, ask them to identify the loop’s end condition or count in the broken scripts to correct the misconception.

---

Methods used in this brief

• Project-Based Learning