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 a story about you. This can be something that actually happened in your life, something you want to happen, or a fantasy story. Display and demonstrate the sample project (or your own remixed version).

Video: Project Preview (0:54)
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?

3. Create a storyboard (10-15+ minutes):
Walk through the process of creating a storyboard by asking the following questions, then giving coders time to document their answers through physical or digital means:

1. Which of the following ideas will you use to create a story about yourself?
   a. My favorite memory is when . . .
   b. If I lived in the future . . .
   c. If I were alive a long time ago . . .
   d. If I could solve one problem in the world . . .
2. Can you describe what will happen in your story?
   a. What happens first?
   b. What happens next?
   c. What happens after that?
   d. How does your story end?
3. What kind of sprites and backdrops will you use?
4. What will each of these sprites do?
   a. What algorithms can you create to do that?
5. Will users be able to interact with your story?

When coders are ready, have them show you their storyboard and ask questions for clarification of their intent (which may change once they start coding and get more ideas). If approved, they may continue on to the next steps (logging in and creating their story); otherwise they can continue to think through and work on their storyboard.

Note: Coders may change their mind midway through a project and wish to rethink through their original storyboard. This is part of the design process and it is encouraged they revise their storyboard to reflect their new ideas.

Resource: Example storyboard templates
Resource: Storyboard questions for displaying

Note: Some coders do really well with open projects, while others thrive within constraints. It may make more sense to suggest a range of sprites and backdrops so coders aren’t overwhelmed with possibilities. This can also help with better predicting how long it might take to create the story.

Storyboarding Tip: Coders can color their storyboard (or mark with symbols) what they know, have questions about, and don’t know. For example: mark something green if coders know how to create the algorithm for that sprite/action; mark yellow if a coder has questions; mark red if a coder is unsure how to do something.

Suggestion: If coders need additional help, perhaps pair them with someone who might help them with the storyboarding process. Or, you could have coders meet with a peer to discuss their storyboard before asking to share it with yourself. This can be a great way to get academic feedback and ideas from a peer.

4. Log in (1-15+ minutes):
If not yet comfortable with logging in, review how to log into Scratch and create a new project.

If coders continue to have difficulty with logging in, you can create cards with a coder’s login information and store it in your desk. This will allow coders to access their account without displaying their login information to others.

Alternative login suggestion: Instead of logging in at the start of class, another approach is to wait until the end of class to log in so coders can immediately begin working on coding; however, coders may need a reminder to save before leaving or they will lose their work.

Why the variable length of time? It depends on comfort with login usernames/passwords and how often coders have signed into Scratch before. Although this process may take longer than desired at the beginning, coders will eventually be able to login within seconds rather than minutes.

What if some coders log in much faster than others? Set a timer for how long everyone has to log in to their account (e.g., 5 minutes). If anyone logs in faster than the time limit, they can open up previous projects and add to them. Your role during this time is to help out those who are having difficulty logging in. Once the timer goes off, everyone stops their process and prepares for the following chunk.