Technologies · Foundation

Active learning ideas

Simple Conditional Logic: If/Else

Active learning works for this topic because children physically move and test decisions, which makes abstract conditions concrete. When students pair up or manipulate objects, they see how code branches instantly change behavior, turning logic into something they can feel and adjust right away.

• ACARA Content Descriptions
• AC9TDEFP01

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

Activity 01

• Role Play
• 30 min · Pairs

Pair Coding: Conditional Dance

Pairs select sprites and backgrounds. They add if/else blocks so the sprite dances differently if touching a music note (play sound) versus a stop sign (freeze). Test by dragging sprites and swap roles to debug.

Explain how an 'if' statement allows a program to make a decision.

Facilitation Tip

During Pair Coding: Conditional Dance, remind pairs to take turns acting as the ‘computer’ to clarify which path runs when.

What to look for

Give students a simple ScratchJr project with an 'if/else' block. Ask them to draw what the character will do. Then, ask them to write one sentence explaining why the character will do that specific action.

• Apply
• Analyze
• Evaluate
• Social Awareness
• Self-Awareness

Activity 02

• Role Play
• 45 min · Small Groups

Small Groups: Object Collector

Groups build a game where a character collects stars: if touching star, grow bigger and cheer; else, say 'keep looking'. Include obstacles that trigger warnings. Groups demo and vote on best features.

Design a program where a character changes behavior based on a condition (e.g., touching an object).

Facilitation Tip

For Small Groups: Object Collector, rotate the collector sprite manually to show how the condition updates in real time.

What to look for

Present students with two scenarios: 1. A character touches a blue square. 2. A character does not touch a blue square. Ask them to choose the correct block sequence for each scenario: 'If touching blue, say hello' or 'If not touching blue, say hello'.

• Apply
• Analyze
• Evaluate
• Social Awareness
• Self-Awareness

Activity 03

• Role Play
• 25 min · Whole Class

Whole Class: Prediction Challenge

Project a simple if/else program. Class predicts sprite actions for different starting positions. Run code, discuss matches, then pairs recreate and modify it.

Predict the path a program will take given a specific condition.

Facilitation Tip

In Whole Class: Prediction Challenge, pause after each scenario to ask students to vote on outcomes before testing, reinforcing prediction habits.

What to look for

Ask students: 'Imagine you are designing a game where a character needs to collect coins. How could you use an 'if' statement to make the character get a point only when it touches a coin?' Listen for their use of 'if', 'touching', and 'score'.

• Apply
• Analyze
• Evaluate
• Social Awareness
• Self-Awareness

Activity 04

• Role Play
• 20 min · Individual

Individual: Weather Responder

Each student codes an avatar that changes costume or message based on 'sunny' or 'rainy' backgrounds using if/else. Share one screen-wide.

Explain how an 'if' statement allows a program to make a decision.

Facilitation Tip

For Individual: Weather Responder, circulate to check that students test edge cases, like pressing the rain button when the sun is already showing.

What to look for

Give students a simple ScratchJr project with an 'if/else' block. Ask them to draw what the character will do. Then, ask them to write one sentence explaining why the character will do that specific action.

• Apply
• Analyze
• Evaluate
• Social Awareness
• Self-Awareness

A few notes on teaching this unit

Start by modeling a simple if/else in block code and narrating each step aloud. Avoid rushing to the else block; pause after the if so students notice when nothing happens if the condition is false. Research shows that young learners grasp conditional logic best when they physically act out the branches before coding them.

Successful learning looks like students using if/else blocks to make clear choices in their programs. They should explain why only one outcome happens at a time, debug mismatches between condition and action, and describe how changing inputs alters program behavior in predictable ways.

---

Watch Out for These Misconceptions

• During Pair Coding: Conditional Dance, watch for students who move both dance moves at once, assuming both paths execute.

  Have them freeze after each move and ask, ‘Which one happened first?’ Use the dance cards to highlight that only one block runs based on the condition.

• During Small Groups: Object Collector, watch for students who think the ‘else’ block runs if the object is already collected.

  Guide them to reset the object’s position between trials and ask, ‘What is the starting state?’ to reinforce that conditions check the current moment.

• During Whole Class: Prediction Challenge, watch for students who ignore the initial setup and guess randomly.

  Ask them to point to the background color or sprite position before selecting the block, making conditions visible and explicit.

---

Methods used in this brief

• Role Play