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.

• Year 7
• Computing
• 4 activities
• 30 min–45 min

Learning Objectives

1. Analyze the impact of instruction order on program execution by predicting the output of Scratch scripts with reordered blocks.
2. Compare the efficiency of sequential instructions versus repeated instructions using loop blocks in Scratch.
3. Construct a Scratch project that animates a sprite through a specific sequence of movements and actions.
4. Explain why the precise order of commands is critical for the successful operation of a computer program.

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.

Prepare & details

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.

Setup: Flexible workspace with access to materials and technology

Materials: Project brief with driving question, Planning template and timeline, Rubric with milestones, Presentation materials

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

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.

Prepare & details

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.

Setup: Flexible workspace with access to materials and technology

Materials: Project brief with driving question, Planning template and timeline, Rubric with milestones, Presentation materials

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

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.

Prepare & details

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.

Setup: Flexible workspace with access to materials and technology

Materials: Project brief with driving question, Planning template and timeline, Rubric with milestones, Presentation materials

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

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.

Prepare & details

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.

Setup: Flexible workspace with access to materials and technology

Materials: Project brief with driving question, Planning template and timeline, Rubric with milestones, Presentation materials

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

Teaching This Topic

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.

What to Expect

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

Common Misconception

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

What to Teach Instead

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?'

Common Misconception

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

What to Teach Instead

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.

Common Misconception

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

What to Teach Instead

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.

Assessment Ideas

Exit Ticket

After Predict-Reorder-Test, give each student a simple Scratch script (e.g., move, say, change costume). Ask them to write or draw the sprite’s final state and then predict what happens if two specific blocks are swapped. Collect responses to check for accurate sequencing predictions.

Quick Check

During Human Algorithm Relay, pause after one round and ask a student to explain why changing the order of instructions altered the final outcome. Use their response to gauge if the class recognizes the importance of sequence.

Discussion Prompt

After Loop Dance Builder, pose the discussion prompt: 'Imagine giving instructions to a friend to make a sandwich. Why is the order of your instructions more important than just listing all the ingredients?' Circulate to listen for connections between real-world sequencing and programming.

Extensions & Scaffolding

• Challenge: Ask students to create a Scratch animation where swapping two blocks changes the sprite’s entire behavior (e.g., from walking to jumping).
• Scaffolding: Provide pre-written blocks with missing gaps for students to fill in the correct order to achieve a simple goal.
• Deeper exploration: Introduce nested loops (e.g., a loop inside a loop) and ask students to predict and test the timing or behavior differences.

Key Vocabulary

Sequence	The order in which instructions are executed by a computer, one after another.
Algorithm	A set of step-by-step instructions designed to perform a specific task or solve a problem.
Sprite	A character or object in a Scratch project that can be programmed to move and interact.
Loop (Repeat Block)	A programming structure that allows a set of instructions to be executed multiple times without rewriting them.