Computing · Year 6

Active learning ideas

Complex Scoring Systems

Active learning works for complex scoring systems because students need to see how variables interact in real time. Programming live score updates helps them grasp dependencies that static worksheets cannot show. Classroom talk about balancing fun and fairness turns abstract concepts into concrete decisions.

• National Curriculum Attainment Targets
• KS2: Computing - Programming and Algorithms
• KS2: Computing - Computational Thinking

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

Activity 01

• Collaborative Problem-Solving
• 45 min · Pairs

Pair Programming: Bonus Hunter Game

Pairs design a Scratch game where players collect items for base scores, with combo multipliers and time bonuses. They add if-statements for penalties on collisions. Test and swap roles to refine the algorithm.

Analyze how multiple variables can contribute to a complex scoring system.

Facilitation Tip

During Pair Programming: Bonus Hunter Game, ask each pair to take turns explaining why their score block fires before the other edits it.

What to look for

Present students with a simple game scenario (e.g., a platformer). Ask them to write down three variables that could be used in a scoring system and one rule for how each variable might change during gameplay.

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

Activity 02

• Collaborative Problem-Solving
• 35 min · Small Groups

Small Groups: Scoring Flowchart Challenge

Groups draw flowcharts for a racing game scoring system with variables for laps, speed penalties, and efficiency bonuses. Convert to Scratch code, then simulate runs to verify logic. Share one insight with the class.

Justify the inclusion of a bonus point system in a game based on player engagement.

Facilitation Tip

In the Scoring Flowchart Challenge, provide colored pencils so groups can highlight feedback loops between variables.

What to look for

In small groups, have students discuss this prompt: 'Imagine a racing game. Should finishing first always give the highest score, or could other actions like collecting items or performing stunts be more important for a high score? Justify your answer using the idea of rewarding different player skills.'

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

Activity 03

• Collaborative Problem-Solving
• 30 min · Whole Class

Whole Class: Game Critique Circle

Students demo their scoring games. Class votes on engagement using a rubric, noting variable impacts. Revise code based on collective feedback before final play.

Construct a scoring algorithm that rewards efficiency over speed in a challenge.

Facilitation Tip

For the Game Critique Circle, give students sticky notes to label parts of the scoring system they notice while playing peers' projects.

What to look for

Students share their game projects. Partners playtest for 2 minutes, then answer: 'Did the scoring system feel fair? Were there any surprising bonuses or penalties? What is one suggestion to make the scoring more interesting or balanced?'

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

Activity 04

• Collaborative Problem-Solving
• 40 min · Individual

Individual: Efficiency Puzzle Modifier

Each student modifies an existing Scratch puzzle to add a scoring system rewarding fewest moves with bonuses. Document changes and test against personal benchmarks.

Analyze how multiple variables can contribute to a complex scoring system.

Facilitation Tip

During Efficiency Puzzle Modifier, remind students that shorter code is easier to debug but must still reflect the scoring rules.

What to look for

Present students with a simple game scenario (e.g., a platformer). Ask them to write down three variables that could be used in a scoring system and one rule for how each variable might change during gameplay.

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

A few notes on teaching this unit

Start with a whole-class demo that breaks a simple game’s scoring into labeled parts. Model tracing values with print statements, then have students replicate the process in pairs. Use think-alouds to show how to adjust one variable and watch ripple effects. Avoid rushing to solutions; let missteps become teachable moments.

Students will combine variables into working score formulas and explain how each part affects gameplay. They will adjust multipliers, bonuses, and penalties based on feedback and justify their choices. Projects show balanced designs that reward different player actions without feeling random.

---

Watch Out for These Misconceptions

• During Pair Programming: Bonus Hunter Game, watch for students who split work without discussing how their variables connect, causing mismatched updates.

  Pause the pair after five minutes and ask each student to trace the score update step-by-step using print statements, then swap roles and repeat.

• During Scoring Flowchart Challenge, watch for sequences that ignore conditional triggers for bonuses or penalties.

  Hand out post-it arrows and have groups attach them to the flowchart where conditions should be checked, then revise until all arrows point to clear decision diamonds.

• During Game Critique Circle, watch for comments that praise scoring systems without linking features to player engagement.

  Provide sentence stems like ‘The decaying timer made me feel pressured because…’ to guide specific, evidence-based feedback.

---

Methods used in this brief

• Collaborative Problem-Solving