Teaching KS2 computing when you're not a specialist
Most primary teachers who teach computing aren't computing specialists, and they don't need to be. Year 5 and 6 computing is a small set of big ideas that come back again and again. If you know what those ideas are, what pupils usually get wrong, and how to check what they remember, you can teach it well. Here's a practical way in.
What the curriculum actually asks for
The national curriculum for computing in Key Stage 2 has just a handful of statements. In short, pupils should:
- Design, write and debug programs, including breaking a problem into smaller parts.
- Use sequence, selection and repetition in programs, work with variables, and use different kinds of input and output.
- Use logical reasoning to explain how simple algorithms work, and to find and fix mistakes.
- Understand computer networks, including the internet, and how they make the web, email and other services possible.
- Use search well, and judge whether what they find can be trusted.
- Use a range of software to create content and to collect and present data.
- Use technology safely, respectfully and responsibly, and know how and where to report concerns.
That's it. Every unit you teach in Years 5 and 6 is one of these in a different setting: a quiz program uses selection, a game uses variables, a spreadsheet presents data.
Learn the words, then teach the words
Much of computing is vocabulary. Once you're confident with about twenty words, most lessons fall into place. The ones that matter most in upper KS2 are:
- Algorithm: a set of steps to do a job, in the right order.
- Program: an algorithm written so a computer can follow it.
- Sequence: steps carried out one after another.
- Repetition (or a loop): steps that are repeated a number of times, or for ever.
- Selection: the program chooses what to do, using if… then… else.
- Condition: the question in an if that is either true or false.
- Variable: a named place to store a value that can change, such as a score.
- Debugging: finding and fixing mistakes (bugs) in a program.
- Input and output: information going into and coming out of a computer.
- Network, router, server, the internet and the World Wide Web (the web is pages on the internet; they're not the same thing).
Use the words every lesson, put them on the wall, and ask pupils to use them in their answers. Spelling the words matters too: it helps pupils read and remember them.
Know the common mix-ups
A few misconceptions come up in almost every class. Planning for them is the quickest way to teach like a specialist.
- "The internet and the web are the same." The internet is the network of connected computers; the web is one of the services that uses it.
- "A loop repeats everything." Pupils often put blocks outside a loop that should be inside it, or the other way round. Ask them to point to exactly what repeats.
- "Computers are clever." A computer only does exactly what the program says, in order. Acting out an algorithm, with one pupil following instructions word for word, makes this stick.
- "If the program runs, it's right." A program can run and still do the wrong thing. Ask pupils to predict what will happen before they press run, then compare.
- "Everything at the top of a search is true." Results can be adverts, and anyone can publish a web page. Teach pupils to ask who made it, when, and whether other sources agree.
Little and often beats one big test
Computing is often taught for one lesson a week, or in blocks, so pupils can go weeks without meeting an idea again. That's exactly when they forget it. Short, regular retrieval practice helps more than anything else: a few questions at the start of a lesson on last week's work, and a quick quiz on a unit from last term. The research on this is strong, and we've summarised it in our guide to retrieval practice in computing.
Keep it low-stakes. Five questions, no marks in a markbook, the answers explained straight away. The aim is remembering, not grading.
Make the thinking visible
- Predict, run, explain. Before running a program, pupils predict what it will do. Afterwards, they explain any difference.
- Unplugged first. Act out a loop, sort pupils with a branching database of yes/no questions, or "route" a message around the classroom like a network. Then do the same thing on screen.
- Debug together. Show a program with one deliberate mistake and ask the class to find it. Debugging is a skill in its own right, not a sign that something went wrong.
How RADevo helps
RADevo has KS2 computing quizzes for Years 5 and 6, with every answer explained in one plain sentence, so you can go over it with the class without being a specialist. Questions can be read aloud and there are no timers. Pupils earn blocks for right answers and use them to program a robot in Robot Rescue, which builds sequence, loops and debugging. Teachers get a simple view: play a game in class, set homework, and see who has done what and what the class finds hard. See RADevo for primary schools and the step-by-step teacher guide.
References
- Department for Education (2013). National curriculum in England: computing programmes of study.
- Education Endowment Foundation (2021). Cognitive science approaches in the classroom: a review of the evidence.
- Ofsted (2022). Research review series: computing.