Computing · Year 3 · Events and Actions: Interactive Games · Summer Term

Sharing and Evaluating Games

Students share their interactive games with peers, gather feedback, and reflect on their design choices.

• National Curriculum Attainment Targets
• KS2: Computing - Digital Literacy
• KS2: Computing - Information Technology

About This Topic

In Year 3 Computing, sharing and evaluating games builds on students' creation of interactive experiences by having them present work to peers for playtesting and structured feedback. Pupils play each other's games, note what works well such as intuitive controls or engaging events, and suggest improvements like clearer instructions or balanced challenges. They then reflect on their own designs, justifying choices around sprites, actions, and user flow while predicting refinements. This meets KS2 digital literacy through critical appraisal of digital products and information technology via collaborative tech use.

The process fosters computational thinking skills like decomposition and evaluation, alongside communication and resilience. Students learn to distinguish helpful feedback from vague comments, articulating how design decisions impact user experience. Group discussions reveal patterns in feedback, helping pupils connect individual critiques to broader design principles and prepare for iterative development.

Active learning excels in this topic because hands-on playtesting and real-time peer exchanges make abstract evaluation concrete. When students rotate through games, discuss findings in pairs, and revise on the spot, they grasp feedback's value through direct involvement, boosting ownership and retention of design reflection skills.

Key Questions

1. Evaluate the effectiveness of a peer's game based on user feedback.
2. Justify the design choices made in your own game.
3. Predict how you would improve your game based on the feedback received.

Learning Objectives

• Analyze peer feedback to identify specific strengths and weaknesses in an interactive game.
• Evaluate the effectiveness of game design elements, such as controls and events, based on user experience.
• Justify design choices made in their own game, explaining their purpose and intended effect.
• Propose concrete improvements to their game by synthesizing feedback received from peers.
• Critique their own game's user flow and engagement based on observed playtesting.

Before You Start

Creating Interactive Stories or Games

Why: Students need to have already created a basic interactive game or story to have something to share and receive feedback on.

Basic Programming Concepts (Events and Actions)

Why: Understanding how events trigger actions is fundamental to both creating and evaluating the mechanics of an interactive game.

Key Vocabulary

User Feedback	Information and opinions provided by someone who has used a product or service, in this case, a game. This helps identify what works well and what needs improvement.
Design Choice	A specific decision made by a game creator about how the game looks, sounds, or plays. This includes choices about characters, backgrounds, sounds, and how actions happen.
Iterative Design	A design process that involves repeating cycles of designing, testing, and refining. This game sharing activity is a step in this process.
Usability	How easy and intuitive a game is to play. Good usability means players can understand the controls and objectives without confusion.

Watch Out for These Misconceptions

Common Misconception

My game needs no changes because I like it.

What to Teach Instead

Peer playtesting uncovers usability issues the creator overlooks, such as unclear event triggers. Group rotations and shared feedback sheets help students compare experiences, building skills to weigh evidence over personal bias.

Common Misconception

A good game is only about being fun.

What to Teach Instead

Effective games also need clear navigation and fair challenges. Active play in pairs reveals when fun breaks due to bugs, prompting discussions that balance enjoyment with functionality.

Common Misconception

Every piece of feedback must be used.

What to Teach Instead

Not all comments suit the design vision. Reflection carousels let students practise justifying selections, learning through peer debate to filter and prioritise constructively.

Active Learning Ideas

Gallery Walk: Game Playtesting

Display student games on classroom computers or tablets. Groups rotate every 5 minutes to play a game, recording one strength, one challenge, and a suggestion on feedback sheets. After rotations, students review notes from all players on their own game.

45 min·Small Groups

Feedback Pairs: Design Justification

Partners play each other's game for 4 minutes then switch: the designer explains choices while the player shares observations. Each pair agrees on two key improvements. Pairs report one insight to the class.

30 min·Pairs

Reflection Carousel: Improvement Planning

Post feedback sheets around the room. Students visit three sheets, adding their own game parallels or tips. Back at stations, they prioritise changes and sketch quick prototypes.

35 min·Small Groups

Whole Class Debrief: Feedback Trends

Project anonymised feedback quotes. Class votes on common themes like 'confusing start screen' and brainstorms solutions. Each student updates their game log with one action.

25 min·Whole Class

Real-World Connections

• Game designers at companies like Nintendo or PlayStation regularly share early versions of their games with playtesters. They collect feedback to refine gameplay, fix bugs, and ensure the game is enjoyable before its public release.
• App developers often use beta testing programs where selected users try out new apps and provide detailed feedback. This helps them improve the app's features and user experience based on real-world usage.

Assessment Ideas

Peer Assessment

Students play a partner's game for 5 minutes. Provide them with a simple checklist: 1. What did you like most about the game? 2. What was confusing or difficult? 3. Suggest one change to make it better. Students then discuss their checklist with the game creator.

Discussion Prompt

After sharing, ask students: 'Think about the feedback you received. Which piece of feedback was most helpful and why? How will you use this feedback to change your game?' Record student responses or have them write down their answer.

Quick Check

Ask students to hold up fingers to indicate how confident they feel about explaining one of their game's design choices (1=not confident, 5=very confident). Then, ask them to write down one specific design choice they made and why they made it.

Frequently Asked Questions

How do Year 3 pupils give effective feedback on Computing games?

Teach simple frameworks like 'What I liked, what confused me, one idea to improve.' Model with class demos, then use sticky notes or digital forms during playtesting. Follow with paired discussions to refine comments, ensuring feedback stays specific, kind, and actionable. This builds communication skills aligned to digital literacy.

What active learning strategies best support game evaluation in Year 3?

Strategies like gallery walks and peer playtesting rotations engage students directly with others' games, making feedback immediate and multi-perspective. Pair justifications followed by group debriefs turn passive review into collaborative sense-making. These approaches, lasting 30-45 minutes, help pupils internalise evaluation criteria through doing, reflection, and iteration, far beyond worksheets.

How does sharing games fit UK National Curriculum Computing for KS2?

It directly supports digital literacy by evaluating digital content effectiveness and information technology through sharing tech-created work. Key questions on justifying designs and predicting improvements develop reflection and iteration, core to computational thinking. Integrate across units by linking to prior game-building, showing design as a cycle.

How to handle emotional reactions to game feedback?

Normalise feedback as helpful clues, not criticism, via pre-sharing talks on growth mindset. Use anonymous sheets first, then paired positive starts. Debrief circles let students share feelings and wins, reinforcing resilience. Follow with quick wins like one easy fix, turning discomfort into pride in progress.