Computing · Year 7

Active learning ideas

Algorithmic Thinking: Pseudocode

Students learn pseudocode best when they see it as a bridge between their everyday language and formal logic. By writing and revising instructions for tasks they know well, pupils grasp how algorithms break down complexity into clear steps. Active tasks make the need for precision immediate and tangible.

• National Curriculum Attainment Targets
• KS3: Computing - Algorithms

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

Activity 01

• Peer Teaching
• 30 min · Pairs

Pair Programming: Daily Routine Pseudocode

Pairs write pseudocode for a morning routine, like getting ready for school. They swap scripts, follow instructions literally as 'computers', and note failures. Revise together for clarity and test again.

Translate a simple real-world process into pseudocode.

Facilitation Tip

During Pair Programming, circulate and listen for students to verbalize steps before writing, reinforcing the connection between action and code.

What to look for

Provide students with a simple real-world task, such as 'making a sandwich'. Ask them to write 3-5 steps of pseudocode to describe the process. Then, ask them to identify one potential ambiguity in their own instructions.

• Understand
• Apply
• Analyze
• Create
• Self-Management
• Relationship Skills

Activity 02

• Peer Teaching
• 45 min · Small Groups

Small Groups: Sorting Challenge

Provide number cards to groups. Students design pseudocode to sort them ascending. Groups perform the algorithm with cards, time it, then swap and improve rival versions for efficiency.

Evaluate the clarity and precision of a given pseudocode example.

Facilitation Tip

In Small Groups, limit sorting tools to physical items first (e.g., cards or books) to ground abstract concepts in concrete experience.

What to look for

In pairs, students exchange pseudocode for a sorting task (e.g., sorting books by height). Student A explains their pseudocode. Student B asks clarifying questions and identifies one step that could be more precise. They then swap roles.

• Understand
• Apply
• Analyze
• Create
• Self-Management
• Relationship Skills

Activity 03

• Peer Teaching
• 20 min · Whole Class

Whole Class: Human Algorithm

Teacher reads pseudocode for a simple task like traffic lights. Class members act as elements, demonstrating flow. Discuss breakdowns, then students volunteer improved pseudocode.

Design a pseudocode algorithm to solve a specific problem, such as sorting a list of numbers.

Facilitation Tip

For Human Algorithm, deliberately introduce a misstep in the human ‘code’ to model debugging and revision in real time.

What to look for

Display a short pseudocode example on the board (e.g., a simple IF statement). Ask students to write down what the pseudocode will do if the condition is TRUE and what it will do if the condition is FALSE.

• Understand
• Apply
• Analyze
• Create
• Self-Management
• Relationship Skills

Activity 04

• Peer Teaching
• 25 min · Individual

Individual: Recipe Refinement

Students convert a real recipe into pseudocode, adding decisions like 'if oven hot'. Self-evaluate using a checklist, then share one strength and fix with a peer.

Translate a simple real-world process into pseudocode.

What to look for

Provide students with a simple real-world task, such as 'making a sandwich'. Ask them to write 3-5 steps of pseudocode to describe the process. Then, ask them to identify one potential ambiguity in their own instructions.

• Understand
• Apply
• Analyze
• Create
• Self-Management
• Relationship Skills

A few notes on teaching this unit

Teach pseudocode as a rehearsal for programming, not just a separate skill. Model turning your own spoken instructions into pseudocode, then reverse the process: have students translate their pseudocode back into steps to check for gaps. Research shows that students benefit from seeing mistakes corrected in public, so deliberately include flawed examples for analysis. Avoid rushing to correct students; instead, prompt them to articulate why a step is unclear or incomplete.

Students will write pseudocode that others can follow without confusion. They will identify missing steps or vague language in peer work and refine their own instructions through feedback. By the end, they should confidently decompose small tasks into algorithmic steps using structured English.

---

Watch Out for These Misconceptions

• During Pair Programming, watch for students using casual phrases like 'get the cup' without specifying which cup or how to verify it is clean.

  Have pairs act out their instructions to expose vague steps. Ask, 'Which cup did you take?' and 'How do you know it is clean?' to guide them to add conditions like 'take clean cup' and 'check water level'.

• During Small Groups: Sorting Challenge, watch for groups treating the task as a single pass through the items rather than iterating until sorted.

  Ask groups to time their sorts and compare steps. Prompt them to add loops by asking, 'How many times did you need to look at each book?' to highlight the need for repetition in the pseudocode.

• During Recipe Refinement, watch for students changing a single word without considering the impact on the whole process.

  Have students swap recipes and underline any word that could cause confusion. Discuss how a change like 'add sugar' to 'add 2 spoons of sugar' affects the outcome, linking to debugging precision.

---

Methods used in this brief

• Peer Teaching