Lesson 5: Simon Says
Overview
In this lesson, students will play a game intended to get them thinking about the way commands need to be given to produce the right result. This will help them more easily carry over to Sprite Lab in the upcoming lessons.
Purpose
This lesson is designed to prepare students to think about one of the core programming concepts in Sprite Lab, behaviors.
Agenda
Warm Up (10 min)
Main Activity (20 min)
Wrap Up (15 min)
View on Code Studio
Preparation
- Play through the puzzles to find any potential problem areas for your class.
- Make sure every student has a journal.
Support
Report a Bug
Teaching Guide
Warm Up (10 min)
Introduction
Discussion Goal
Goal: Help students think about times when they must keep track of multiple tasks or instructions simultaneously. The main activity will get students performing silly actions, either in sequence or simultaneously. This will eventually lead to connections about a new way to write programs, but you don't need to get the discussion there yet.
Think-Pair-Share: Think of hobby, sport, or activity that you know how to do well. What does it take to do it well? Are there times when you need think about multiple things or perform different actions at the same time?
- What parts of your body are you using? Does this change at different points?
- Are there times when you need to stop one action before you can begin another? (For example, you must stop dribbling the basketball before you can shoot.)
Remarks
Today we're going to play a game where you'll need to keep track of multiple tasks simultaneously. It's a little bit like Simon Says.
Main Activity (20 min)
Simon Says
Remarks
In the game Simon Says, one player takes the roll of “Simon” or the leader who gives command to other players. Players must follow the leader’s commands if and only if they are prefaced with the phrase “Simon Says”. The point of the game is to think quickly and to distinguish between real and fake commands. In this version of the game, the rules are a little different.
Rules
All commands should be prefaced with either “begin” or “stop”.
When players are told to “begin” a behavior, they should continue it until told to “stop”. For example, players should not told be told to clap once, but might be told to “begin clapping”. Their clapping should continue until they are told to “stop clapping” even if they are given other new behaviors in between.
The leader can also call for the players to “stop everything”.
This should result in everyone just standing at rest regardless of all previous commands.
You as the teacher should take on the role of the leader. You can try make up your own sequences, but here are some you can try. Be sure to give a little space between commands. For each of these sections, consider running through the entire sequence without any discussion and later repeating it again after everyone has had a chance to debrief and process any confusion.
Basic:
- Begin marching in place.
- Stop marching in place.
- Begin clapping.
- Stop clapping.
- Begin marching in place.
- Begin clapping.
- Stop everything.
Debrief: What happened when you were told to clap but you were already marching in place? What happens if you are told to begin two different behaviors at once?
Intermediate:
- Begin waving your arms in the air.
- Begin bobbing your head.
- Stop waving your arms in the air.
- Stop bobbing your head.
- Begin shaking your knees.
- Begin flapping your arms like a bird.
- Stop shaking your knees.
- Begin bobbing your head.
- Begin marching in place.
- Stop flapping your arms like a bird.
- Stop everything.
Debrief:
What kinds of instructions caused people to make mistakes?
What strategies do you think are helpful for making sure you follow instructions correctly?
Why is it important to keep track of each behavior separately?
Challenging
- Begin crouching.
- Begin tapping your head.
- Stop crouching.
- Stop tapping your head.
- Begin jumping up and down.
- Begin tapping your head.
- Stop everything.
- Begin clapping.
- Begin flapping your arms like a bird.
- Stop everything.
- Begin crouching.
- Begin jumping up and down.
- Stop everything.
- Begin tapping your knees.
- Begin tapping your head.
- Stop everything.
- Begin spinning to the left.
- Begin spinning to the right.
- Stop spinning to the left.
- Stop spinning to the right.
Debrief: What happens if two behaviors seem to conflict with each other?
What should you do when told to clap your hands and flap your arms at the same time?
How can you jump up and down while crouching?
What happens if you need to tap your knees and your head at the same time?
When you were told to spin in two opposite directions what did you see people do? What would happen if you were told to spin left and right at the exact same time?
Extension
If you want to make things even more complicated, you can consider changing the rules so that only some players follow some commands. For example, you could try commands like “All girls begin spinning to the left”, “All boys begin clapping your hands”, or “Everyone stop everything.”
Wrap Up (15 min)
Reflection
Journal: Think back to the activity or hobby you discussed at the beginning of class. Using "begin" and "stop" commands write down the instructions you could give someone if you wanted them to act like they were they were doing it. Be sure to remember when they might need to stop something before beginning something new.
- Levels
- 1
Student Instructions
Simon Says
Play a game and think about what commands are needed to get the right result.
Standards Alignment
View full course alignment
CSTA K-12 Computer Science Standards (2017)
AP - Algorithms & Programming
- 1B-AP-12 - Modify, remix or incorporate portions of an existing program into one's own work, to develop something new or add more advanced features.