Cover lesson · Science and Technology · Year 2 · Intermediate
DCF: Data and computational thinking → Problem-solving and modelling
Also assessed, LNF: Numeracy → Geometry and measurement → Position
What this practises: giving a robot instructions with arrows (an algorithm), following code step by step, finding and fixing a bug, and spotting repeats. Pupils also count squares and use position words (above, below, next to), which is numeracy marked from the sheet. A floor robot is great if your school has one, but no robots or computers are needed.
Print: Part 2 of this sheet (the pupil page, 2 sides), one per pupil. Pupils need a pencil and a coloured pencil for drawing routes.
Run: 5 min Step 1, hook · 10 min Step 2, be the robot · 8 min Step 3, Task 1 · 10 min Step 4, Task 2 · 8 min Step 5, Task 3 · 7 min Step 6, Task 4 · 7 min Step 7, Task 5 · 5 min Step 8, Task 6 and share. Total 60 minutes.
Collect: the pupil page. DCF evidence: Tasks 1 to 4 (following, writing, debugging and shortening code). Numeracy evidence: the squares counted in Task 1, the route in Task 2, the counted repeats in Task 4 and the position words in Task 5. Quick checks: Task 1 lands on the red flower after 5 squares. Task 3 lands one square above the blue flower; the last ↑ is the bug. Task 4 is 4 → 2 ↑. Task 5: above, next to, below.
Read the words in the blue boxes aloud. Show tells you what to hold up or point to, and Ask gives you questions with the answers to listen for.
Bees fly from flower to flower to collect a sweet drink called nectar. As they fly, they carry yellow dust called pollen from one flower to the next. That helps the plants make seeds.
Today you will program a robot bee. A robot only does what the code tells it, so our code must be just right.
Show: draw a 3 by 3 grid on the board and draw a bee in the bottom left square and a flower in the top right square.
Our robot bee understands 4 arrows. Up, down, left and right. Each arrow moves it 1 square.
Draw the 4 arrows on the board. Ask pupils to tell you arrows to get the bee to the flower, and move your finger 1 square for each arrow. Then do it wrong on purpose: follow “up” when a pupil says “right”.
Ask: “What went wrong?” Listen for: you went the wrong way; the code was wrong.
A mistake in code is called a bug. Fixing it is called debugging.
Look at the garden map. Put your finger on the bee. Follow the arrows in Task 1, one square at a time. Where does it land?
Check together: up, right, right, right, down. It lands on the red flower after 5 squares.
Now you write the code. Get the bee to the yellow flower. Look out for the web! The bee cannot go through it.
Ask: “Why can’t the bee go straight up?” Listen for: there is a web in the way. Many codes work; check them by following each arrow.
This code is meant to go to the blue flower. Follow it with your finger. Did it work? Draw a cross where it lands. Which arrow is the bug?
Listen for: there is one up arrow too many.
Your fixed code has 4 right arrows in a row. Programmers write repeats the short way: 4, right arrow. Write your fixed code the short way.
Look at the map. The yellow flower is above the web. Above means higher up. Below means lower down. Next to means right beside.
Read each sentence aloud. Pupils choose a word from the word bank and copy it.
Today you wrote code, found a bug and fixed it. Colour a face to show how you did.
Ask 2 pupils to read their Task 2 code aloud while everyone follows it on their own map.
Name: Class: Date:
The bee starts here every time. It must not land on a web .
| ↑ up 1 square | ↓ down 1 square | ← left 1 square | → right 1 square |
How many squares did the bee fly?
Watch out for the web! Draw your route on the map first.
This code should take the bee to the blue flower.
Follow it on the map. Draw a cross where the bee lands.
Circle the arrow that is wrong. Write the fixed code.
→ → → can be written as 3 →
Write your fixed code from Task 3 the short way.
Word bank: above · below · next to
Write a code that takes the bee to the blue flower and then home to the hive.