Skip to content
Technologies · Year 2

Active learning ideas

Interactive Stories: Digital Storytelling

Active learning works for this topic because students need to experience both the cause and effect of event-based programming. When they test sequences in pairs or trigger each other's stories, they see how user actions shape the narrative, making abstract concepts concrete and memorable.

ACARA Content DescriptionsAC9TDI2P03AC9E2LT02
25–45 minPairs → Whole Class4 activities

Activity 01

Role Play35 min · Pairs

Pair Programming: Storyboard to Code

Pairs sketch a three-part story on paper first: beginning setup, middle challenge, end resolution. Then, they code it in ScratchJr using start blocks and tap triggers to sequence scenes. Test together and debug by swapping roles.

Construct an interactive narrative that guides a user through a sequence of events.

Facilitation TipDuring Pair Programming: Storyboard to Code, ask pairs to take turns explaining their sequence aloud before coding to solidify their planning.

What to look forStudents will write down one 'event block' they used in their story and describe what action it triggered. They will also list one way they used sound or visuals to make their story more interesting.

ApplyAnalyzeEvaluateSocial AwarenessSelf-Awareness
Generate Complete Lesson

Activity 02

Role Play45 min · Small Groups

Small Groups: Event Enhancement Stations

Set up stations for sound effects, background changes, and motion triggers. Groups rotate, adding one element per station to their shared story. Record how each improves interactivity before combining.

Explain the role of 'event blocks' in making a story interactive.

Facilitation TipAt Event Enhancement Stations, rotate groups every 10 minutes so students experience different types of event triggers firsthand.

What to look forStudents take turns playing each other's interactive stories. They provide feedback by answering: 'What was the beginning, middle, and end of the story?' and 'What was one thing you liked about how the story responded to you?'

ApplyAnalyzeEvaluateSocial AwarenessSelf-Awareness
Generate Complete Lesson

Activity 03

Role Play30 min · Whole Class

Whole Class: Story Share and Vote

Students present stories via projector; class votes on most engaging event using thumbs up/down. Discuss why certain triggers or effects worked best, then revise one class favorite collaboratively.

Evaluate how sound effects and visual changes enhance the user's experience in a digital story.

Facilitation TipIn Story Share and Vote, have students record the story structure they observe on a shared chart to reinforce the beginning-middle-end framework.

What to look forTeacher observes students as they build their stories. The teacher asks: 'What happens when you click this button?' or 'How did you make the character move to the next scene?' to check understanding of event blocks and sequencing.

ApplyAnalyzeEvaluateSocial AwarenessSelf-Awareness
Generate Complete Lesson

Activity 04

Role Play25 min · Individual

Individual: Personal Twist Challenge

Each student adds a unique branch to their story using broadcast events for choices. Test solo, then pair-share to compare user paths and refine based on feedback.

Construct an interactive narrative that guides a user through a sequence of events.

What to look forStudents will write down one 'event block' they used in their story and describe what action it triggered. They will also list one way they used sound or visuals to make their story more interesting.

ApplyAnalyzeEvaluateSocial AwarenessSelf-Awareness
Generate Complete Lesson

A few notes on teaching this unit

Teach event-based programming by modeling how to break stories into small, testable parts. Avoid giving students all the answers; instead, guide them to debug their own sequences by asking, 'What do you expect to happen next?' Research shows that debugging in pairs builds stronger reasoning than solo work. Use visual timelines to help students map events before coding.

By the end of these activities, students will create an interactive story with clear beginning, middle, and end. They will use event blocks to respond to user input and explain how sound or visuals enhance the experience. Peer feedback will show they understand sequencing and triggers.


Watch Out for These Misconceptions

  • During Pair Programming: Storyboard to Code, watch for students who skip testing their sequences until the very end.

    Set a timer for a 2-minute test after every 3 event blocks are added. Ask pairs to predict what will happen next, then verify their prediction by running the code.

  • During Event Enhancement Stations, watch for students who assume visuals and sounds play automatically.

    Have students explicitly add a 'when tapped' block to every visual or sound trigger. Demonstrate how to drag these triggers into the event stack during station rotations.

  • During Story Share and Vote, watch for students who describe engagement without linking it to specific events.

    Require voters to name one event block they liked and explain how it improved the story. Provide sentence stems like, 'I liked the _____ block because it made the story _____ when I _____.'


Methods used in this brief