Technologies · Year 5

Active learning ideas

Creating Interactive Stories with Code

Active learning works for interactive storytelling because students need to see immediate cause-and-effect between their code and narrative outcomes. When students test choices in real time, they grasp how conditionals shape user experience, reinforcing both algorithmic thinking and creative design. This hands-on approach turns abstract logic into tangible results.

• ACARA Content Descriptions
• AC9TDI6P04
• AC9TDI6P06

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

Activity 01

• Project-Based Learning
• 45 min · Pairs

Pair Programming: Choose-Your-Adventure Start

Pairs use Scratch to code an opening scene with two branching choices leading to different outcomes. One student codes while the other sketches the logic flowchart first. They test both paths and swap roles midway, then combine into a full scene.

Construct an interactive narrative using conditional logic.

Facilitation Tip

During Pair Programming: Choose-Your-Adventure Start, circulate to ensure both partners take turns coding and discussing logic, not just one student driving.

What to look for

Ask students to write down one 'if-then' statement that could be used in their interactive story. For example, 'If the user chooses to go left, then the story moves to the forest scene.'

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

Activity 02

• Project-Based Learning
• 50 min · Small Groups

Small Groups: Storyboard and Code Relay

Groups storyboard a full interactive story with 3-4 branches on paper. Each member codes one branch, then the group assembles and tests the complete program. They record how user inputs change the ending.

Evaluate how user choices impact the storyline in an interactive program.

Facilitation Tip

For Storyboard and Code Relay in small groups, set a strict 5-minute timer per station so students practice rapid prototyping and collaboration.

What to look for

Have students playtest each other's interactive stories. Provide a checklist: Did the story branch? Were there at least two choices? Did the ending change based on a choice? Students can provide one suggestion for improvement.

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

Activity 03

• Project-Based Learning
• 40 min · Whole Class

Whole Class: Demo and Debug Challenge

Students present their stories to the class via projector. The class plays through choices and notes bugs. Presenters fix issues live, explaining their conditional logic to the group.

Design different pathways for a story based on user input.

Facilitation Tip

In the Demo and Debug Challenge, require students to present their most challenging bug first to normalize debugging as part of the process.

What to look for

Facilitate a class discussion: 'Imagine your story character is at a crossroads. What are two different paths they could take, and what might happen on each path? How would you code that decision?'

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

Activity 04

• Project-Based Learning
• 30 min · Individual

Individual: Personal Pathway Design

Students design and code a custom story branch based on class feedback. They evaluate their own work by playing all paths and logging decision impacts before final submission.

Construct an interactive narrative using conditional logic.

Facilitation Tip

For Personal Pathway Design, provide a template with pre-labeled scenes so students focus on branching logic rather than visual layout.

What to look for

Ask students to write down one 'if-then' statement that could be used in their interactive story. For example, 'If the user chooses to go left, then the story moves to the forest scene.'

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

A few notes on teaching this unit

Teaching this topic works best when you model debugging live, showing how to trace a user’s path through the story. Avoid letting students rush to add more features before testing existing pathways, as this reinforces the misconception that code only needs to run once. Research suggests that iterative testing with peers builds stronger habits than isolated individual work, so structure time for frequent playtesting.

Successful learning looks like students confidently designing multiple narrative paths with clear conditionals and testing each branch for consistent outcomes. They should explain their code logic, troubleshoot errors in pathways, and provide constructive feedback to peers on story flow and user choices.

---

Watch Out for These Misconceptions

• During Pair Programming: Choose-Your-Adventure Start, some students may think story outcomes happen randomly rather than based on inputs.

  Have pairs write down their exact conditionals on paper before coding, then test the same input multiple times to confirm consistent results. If outputs vary, they’ll see the need to check their logic.

• During Storyboard and Code Relay, students might assume untested branches work correctly without checking.

  After each relay station, require groups to swap stories and follow a printed checklist to verify all pathways, not just the main one. This builds systematic testing habits.

• During Personal Pathway Design, students may believe stories must follow one straight path.

  Ask students to color-code their storyboard to show branches before coding, then label each branch with its conditional statement to make the logic visible.

---

Methods used in this brief

• Project-Based Learning