1. Review and demonstration (2+ minutes):
Begin by asking coders to talk with a neighbor for 30 seconds about something they learned last time; assess for general understanding of the practices and concepts from the previous project.

Explain that today we are going to create an interactive collage that describes things that you like. Display and demonstrate the sample project (or your own remixed version).

Video: Project Preview (0:59)
Video: Lesson pacing (1:48)

This can include a full class demonstration or guided exploration in small groups or individually. For small group and individual explorations, you can use the videos and quick reference guides embedded within this lesson, and focus on facilitating 1-on-1 throughout the process.

Example review discussion questions:

• What’s something new you learned last time you coded?
  • Is there a new block or word you learned?
• What’s something you want to know more about?
• What’s something you could add or change to your previous project?
• What’s something that was easy/difficult about your previous project?

2. Discuss (3+ minutes):
Have coders talk with each other about how they might create a project like the one demonstrated. If coders are unsure, and the discussion questions aren’t helping, you can model thought processes: “I noticed the sprite moved around, so I think they used a motion block. What motion block(s) might be in the code? What else did you notice?” Open it up to a full group discussion. Another approach might be to wonder out loud by thinking aloud different algorithms and testing them out, next asking coders “what do you wonder about or want to try?”

Note: Discussions might include full class or small groups, or individual responses to discussion prompts. These discussions which ask coders to predict how a project might work, or think through how to create a project, are important aspects of learning to code. Not only does this process help coders think logically and creatively, but it does so without giving away the answer.

Example discussion questions:

• What would we need to know to make something like this in Scratch?
• What kind of blocks might we use?
• What else could you add or change in a project like this?
• What code from our previous projects might we use in a project like this?
• What kind of sprites might we see in an interactive collage?
  • What kind of code might they have?

3. Add and code sprites (20+ minutes):
3 minute review and demonstration
Review how to delete Scratch Cat and where to add sprites. Review how to filter by the categories and add a sprite related to one of your own interests.

Review adding a when this sprite clicked block and ask the class what type of blocks might allow us to make the sprites display a word bubble (looks blocks). Ask what type of looks blocks we could use to display text (any of the say or think blocks). Demonstrate how to use a say block to make the sprite describe something you like when you click on it.

Encourage coders to use the Tutorials to figure out what the other say and think blocks do.

17+ minute coding time and 1-on-1 facilitating
Give coders time to follow each step and leave your code on display so they have a reminder of what blocks to use. Encourage peer-to-peer assistance and facilitate 1-on-1 as needed.

Video: Add and code sprites (2:04)
Quick reference guide: Click here

A note on using the “Coder Resources” with your class: Young coders may need a demonstration (and semi-frequent friendly reminders) for how to navigate a browser with multiple tabs. The reason why is because kids will have at least three tabs open while working on a project: 1) a tab for Scratch, 2) a tab for the Coder Resources walkthrough, and 3) a tab for the video/visual walkthrough for each step in the Coder Resources document. Demonstrate how to navigate between these three tabs and point out that coders will close the video/visual walkthrough once they complete that particular step of a project and open a new tab for the next step or extension. Although this may seem obvious for many adults, we recommend doing this demonstration the first time kids use the Coder Resources and as friendly reminders when needed.

4. Change backdrops (10+ minutes):
3 minute demonstration
Review how to add a backdrop to your project. Add in at least two backdrops.

Demonstrate how we can add in code to make it switch backdrops when the sprite is clicked, have our sprite say something, then switch back to a neutral backdrop when the sprite is done saying something.

7+ minute coding time and 1-on-1 facilitating
Ask coders to add in a unique backdrop for each sprite and use code to make it switch backdrops whenever a sprite is clicked. Facilitate by walking around and asking questions about how coders might change their code so it’s not the same as yours.

Video: Change backdrops (2:23)
Quick reference guide: Click here