New
New
Lesson 6 of 6
  • Year 6

Improving and sharing

I can evaluate and improve my coding project.

Lesson 6 of 6
New
New
  • Year 6

Improving and sharing

I can evaluate and improve my coding project.

These resources were made for remote use during the pandemic, not classroom teaching.

Switch to our new teaching resources now - designed by teachers and leading subject experts, and tested in classrooms.

Lesson details

Key learning points

  1. Ways to improve a game can be identified.
  2. Variables can be used to extend the functionality of a game.
  3. Games can be shared with others.

Keywords

  • Improve - to make changes that make your project better based on feedback or reflection

  • Evaluate - to reflect on what has gone well and what you could improve in a project

Common misconception

I've finished my game — there's nothing else to do.

A part of being a good programmer is knowing how to evaluate and improve your projects. Think about how your game could be even better.


To help you plan your year 6 computing lesson on: Improving and sharing, download all teaching resources for free and adapt to suit your pupils' needs...

It is useful to have a good all-round knowledge of Scratch for this lesson, as learners may choose a variety of different ways to improve their project.
Teacher tip

Equipment

Pupils will need access to a device with block-based programming software. Examples in this lesson use Scratch https://oak.link/scratch

Licence

This content is © Oak National Academy Limited (2025), licensed on Open Government Licence version 3.0 except where otherwise stated. See Oak's terms & conditions (Collection 2).

Lesson video

Loading...

Prior knowledge starter quiz

Download quiz pdf

6 Questions

Q1.
Why should you choose clear names for variables in your project?

to make your code look more colourful
to make your project run faster
Correct answer: to help you remember what each variable is for
to add more sprites

Q2.
What is the main purpose of a design in programming?

to create artwork
Correct answer: to plan how a program should work
to test your project
to make your project longer

Q3.
Put these steps in order for creating a Scratch project:

1 - plan your design
2 - create artwork
3 - write your code
4 - test your project

Q4.
Why is it important to test your code more than once?

Correct answer: to catch different mistakes at different times
to make your project longer
to add more artwork
to rename your variables

Q5.
What is the term for a mistake in a program that causes it to work incorrectly?

Correct Answer: bug

Q6.
What should you do if your project does not work as expected?

ignore it
add more sprites
change the artwork
Correct answer: test and check for mistakes

Assessment exit quiz

Download quiz pdf

6 Questions

Q1.
What does it mean to evaluate your Scratch game?

to play it with friends
to add new sprites
Correct answer: to reflect on what went well and what could be improved
to change the background

Q2.
Why should you share your game with others?

to make it private
Correct answer: to get feedback and see how others use it
to delete it
to make it longer

Q3.
Put these steps in order for improving a Scratch game:

1 - finish your game
2 - ask for feedback
3 - evaluate your project
4 - make improvements

Q4.
What is a good reason to use variables in your game?

to draw pictures
to make music
to change the colour of your sprite
Correct answer: to store information that can change, like a score

Q5.
Match each action to its purpose:

Correct Answer:sharing your game,helps others play and give suggestions

helps others play and give suggestions

Correct Answer:using variables,stores information that can change

stores information that can change

Correct Answer:evaluating your project,helps you see what worked and what could be better

helps you see what worked and what could be better

Correct Answer:making improvements,makes your project better after feedback

makes your project better after feedback

Q6.
Which of these is an example of improving a game?

Correct answer: adding a new level after testing
ignoring feedback
not testing your code
deleting all variables