Learning Objectives
Students will know the steps in an iterative design process - plan, code, test, debug (5.4)
Students will know that that the sequence of their code is important and impacts how it runs (5.1a)
Students will be able to use events to switch scenes & sprites (5.3)
Students will know to expect bugs in their code (5.3)
Students will know how to use debugging (problem solving) strategies to fix bugs in their code (5.3)
Students will be able to debug their project (5.3)
Activity
Introduce students to the activity. Tell students that they should finish creating/gathering images for sprites and backdrop images and start coding events into their project.
Demo to the class how to use events [SOL 5.1] to switch scenes (watch the Using events to switch scenes video for help). You can find sample code here.
Students work on their projects.
During work time, encourage experimentation, risk taking and using peer mentors [CS teaching strategies] and to debug [SOL 5.3] problems they encounter.
Be sure that by the end of class, that students have clicked Share on their projects in Scratch.
Discussion
Have students share out their works-in-progress, ask what was difficult and how they solved their problems (or ask other students for ideas if they haven’t solved problems).
Ask students about if and how they have had to change their plans.
Exit ticket
What did you accomplish today? (Describe tasks you finished and/or new things you learned.)
What are you going to work on next?
What, if anything, is blocking you from making progress?