Computing · Year 4

Active learning ideas

Prototyping and Iteration

Active learning works well for prototyping and iteration because students need to experience the messiness of early drafts and the value of feedback to truly grasp the design process. Moving from theory to hands-on practice helps them see why rough versions save time and lead to better final products.

• National Curriculum Attainment Targets
• KS2: Computing - Programming and Algorithms
• KS2: Computing - Information Technology

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

Activity 01

• Project-Based Learning
• 35 min · Pairs

Pairs: Animation Feedback Swap

Students build a basic Scratch animation of a moving character with one interaction. They swap with a partner for 5 minutes of playtesting and note two strengths and two changes. Pairs then revise their prototype incorporating the feedback and share final versions.

Justify why it is useful to share an unfinished project with a friend for feedback.

Facilitation Tip

During the Animation Feedback Swap, model how to give specific, kind feedback using the checklist as a guide.

What to look for

Students share their unfinished animation or program with a partner. The partner is given a checklist with questions like: 'What did you like about this project?' and 'What was confusing or hard to use?' Students then discuss the feedback with their partner.

• Apply
• Analyze
• Evaluate
• Create
• Self-Management
• Relationship Skills
• Decision-Making

Activity 02

• Project-Based Learning
• 45 min · Small Groups

Small Groups: Game Level Prototype

Groups design a simple maze or obstacle course in Scratch with core mechanics. One member tests while others observe and suggest priorities for features like scoring. Groups iterate twice based on group votes before presenting improvements.

Evaluate how to decide which features are the most important to build first.

Facilitation Tip

While groups build their game level prototype, circulate to ask each group which feature they think is most essential to test first.

What to look for

Ask students to write down two features they included in their prototype and explain which one they think is more important for the final project and why. They should use the term 'feature' in their answer.

• Apply
• Analyze
• Evaluate
• Create
• Self-Management
• Relationship Skills
• Decision-Making

Activity 03

• Project-Based Learning
• 30 min · Whole Class

Whole Class: Feature Prioritisation Walk

Students post printed or screen-captured prototypes around the room with feature lists. Class walks the 'gallery,' votes sticky notes on must-have elements first. Individuals or pairs then iterate one prototype using top-voted ideas.

Explain what changes were made in a design after seeing how someone else used it.

Facilitation Tip

For the Feature Prioritisation Walk, project the criteria list so students can refer to it as they compare projects.

What to look for

During the building phase, ask students: 'If you had to stop building right now, what would be the most important part to show someone?' This helps them think about core functionality and prioritization.

• Apply
• Analyze
• Evaluate
• Create
• Self-Management
• Relationship Skills
• Decision-Making

Activity 04

• Project-Based Learning
• 25 min · Individual

Individual: Iteration Journal

Each student sketches or codes a personal animation prototype, tests it solo, notes issues. They seek one peer comment, then log changes in a journal with before-after screenshots. Share journals in plenary.

Justify why it is useful to share an unfinished project with a friend for feedback.

What to look for

Students share their unfinished animation or program with a partner. The partner is given a checklist with questions like: 'What did you like about this project?' and 'What was confusing or hard to use?' Students then discuss the feedback with their partner.

• Apply
• Analyze
• Evaluate
• Create
• Self-Management
• Relationship Skills
• Decision-Making

A few notes on teaching this unit

Teach prototyping as a habit, not a one-time step. Use consistent language like ‘version 1,’ ‘test,’ and ‘change’ so students see iteration as normal. Avoid rushing to polished work—focus on quick tests and honest feedback to build resilience and problem-solving skills.

Successful learning looks like students comfortably sharing incomplete work, actively listening to feedback, and making purposeful changes based on what they learn. They should explain their design choices clearly and prioritise features that matter most to users.

---

Watch Out for These Misconceptions

• During the Animation Feedback Swap, watch for students who wait until their animation is perfect before sharing.

  Remind students that rough drafts are expected during this activity. Use the checklist to focus feedback on clarity and fun, not polish. Celebrate brave sharing by highlighting how early testing prevents bigger problems later.

• During the Game Level Prototype activity, watch for students who believe iteration means only fixing bugs.

  Ask groups to list two new features they could add based on how peers played their prototype. Use the phrase ‘iteration includes improvements, not just fixes’ to guide discussions toward expansion, not just correction.

• During the Feature Prioritisation Walk, watch for students who dismiss peer feedback because they think their own ideas are best.

  Have students stand near the project they’re reviewing and jot down one new idea or change on a sticky note. Collect these notes and read a few aloud to show how outside views spark better design choices.

---

Methods used in this brief

• Project-Based Learning