Activity 01
Gallery Walk: Project Booths
Arrange student projects on devices around the room as booths. Each student or pair stands by their work, giving a 1-minute pitch on design and code when visitors arrive. Visitors ask one question and leave a sticky note feedback. Rotate roles after 10 minutes.
Explain the functionality and purpose of your coded project to a new audience.
Facilitation TipDuring the Gallery Walk, post guiding questions like 'How did your colour choices support your project’s purpose?' on booth tables to prompt deeper responses from presenters.
What to look forAsk students: 'What was the trickiest part of making your project work, and how did you fix it?' Encourage them to share specific code or design problems they overcame.
UnderstandApplyAnalyzeCreateRelationship SkillsSocial Awareness
Generate Complete Lesson→· · ·
Activity 02
Fishbowl Presentation: Demo Circle
Form an inner circle of 4-5 students presenting sequentially to the outer circle audience. Outer group listens, then swaps to provide feedback on clarity of explanations. Use a talking stick to manage turns. Repeat with new groups.
Critique the most challenging aspect of developing your interactive project.
Facilitation TipIn the Fishbowl Demo Circle, model how to pause and ask, 'Why did you use a loop here instead of repeating the same line?' to encourage reflective explanations.
What to look forAfter presentations, have students complete a simple feedback form for a partner. Include prompts like: 'One thing I liked about your project was...' and 'One idea I have to make it even cooler is...'
RememberUnderstandApplyAnalyzeSelf-ManagementRelationship Skills
Generate Complete Lesson→· · ·
Activity 03
Reflection Relay: Challenge Shares
In a circle, each student shares one coding challenge and solution using a prop like a printed screenshot. Pass a baton; next student builds on the previous by suggesting an enhancement. Record key ideas on a shared chart.
Hypothesize potential future enhancements or additions to your current project.
Facilitation TipFor the Reflection Relay, provide sentence stems such as 'The hardest part was... because...' to structure concise, focused responses.
What to look forAs students present, use a checklist to note if they clearly explained what their project does, mentioned at least one design choice, and described a part of their code logic (e.g., 'when I press the spacebar, the character jumps').
RememberUnderstandApplyAnalyzeSelf-ManagementRelationship Skills
Generate Complete Lesson→· · ·
Activity 04
Digital Showcase: Screen Recordings
Students rehearse and record a 2-minute video explanation of their project using a tablet app. Play videos in class for peer votes on 'most creative logic' and group discussion of strengths.
Explain the functionality and purpose of your coded project to a new audience.
Facilitation TipDuring Digital Showcase recordings, remind students to include both a project walkthrough and a brief reflection on what they would change next time.
What to look forAsk students: 'What was the trickiest part of making your project work, and how did you fix it?' Encourage them to share specific code or design problems they overcame.
RememberUnderstandApplyAnalyzeSelf-ManagementRelationship Skills
Generate Complete Lesson→A few notes on teaching this unit
Teachers should model clear explanations first, breaking down design choices and code logic into simple steps. Avoid rushing to fix problems for students; instead, guide them to articulate challenges themselves. Research shows that peer questioning and structured reflection deepen understanding more than direct instruction alone.
Successful learning looks like students explaining design choices with clear purpose, describing simple code logic in everyday language, and using peer feedback to refine their explanations. Presentations should move beyond demonstration to include reasoning and reflection.
Watch Out for These Misconceptions
During Gallery Walk, students may present their projects without explaining why design choices were made.
Provide booth hosts with a small notecard that asks 'What was your purpose? How did your design support it?' so they rehearse concise answers before peers arrive.
During Fishbowl Presentation, students struggle to explain code logic in simple terms.
Use a mini-lesson to model breaking code into steps with hand-drawn visuals, then have students practice explaining a single loop or sequence to a partner before presenting to the Fishbowl group.
During Reflection Relay, students focus only on what went wrong rather than future improvements.
Give each pair a 'challenge, fix, next step' prompt card to guide their discussion, ensuring they end with at least one forward-looking idea.
Methods used in this brief