Outer Space
Experience: 1st year, 1st quarter
Practice: Developing and Using Abstractions, Creating computational artifacts, Testing and refining computational artifacts, and Communicating about computing
Concept: Control and Algorithms
Length: 40+
Overview and Purpose
Coders use a variety of blocks and sprites to create their own interactive diorama on outer space. The purpose of this project is to continue applying understanding from previous projects.
Lesson plan
Overview videoProject Extensions
Suggested extensions
Adding even more (5+ minutes):
If time permits, encourage coders to explore what else they can create in ScratchJr. Although future lessons will explore different features and blocks, early experimentation should be encouraged.
While facilitating this process, monitor to make sure coders don’t stick with one feature for too long. In particular, coders like to edit their sprites/backgrounds by painting on them or taking photos. It may help to set a timer for creation processes outside of using blocks so coders focus their efforts on coding.
Resources, suggestions, and connections
Standards reinforced:
- 1A-AP-10 Develop programs with sequences and simple loops, to express ideas or address a problem
Practices reinforced:
- Testing and refining computational artifacts
- Creating computational artifacts
Concepts reinforced:
- Algorithms
- Control
Suggested questions:
- What else can you do with ScratchJr?
- What do you think the other blocks do?
- Can you make your sprites do ____?
- What other sprites can you add to your project?
- What else might we find in outer space?
- What other simulated spaces might we create?
- How might we create simulations related to what we are learning in other classes?
Have coders explore the sample projects built into ScratchJr (or projects from other coders), and ask them to find code similar to what they worked on today.
Standard reinforced:
- 1A-AP-10 Develop programs with sequences and simple loops, to express ideas or address a problem
Practice reinforced:
- Testing and refining computational artifacts
Concepts reinforced:
- Algorithms
Note: Coders may need a gentle reminder we are looking at other projects to get ideas for our own project, not to simply play around. For example, “look for five minutes,” “look at no more than five other projects,” or “find three projects that each do one thing you would like to add to your project.”
Generic questions:
- How is this project similar (or different) to something you worked on today?
- What blocks did they use that you didn’t use?
- What do you think those blocks do?
- What’s something you like about their project that you could add to your project?
Differentiation
Less experienced coders
ScratchJr is simple enough that it can be picked up relatively quickly by less experienced coders. However, for those who need additional assistance, pair them with another coder who feels comfortable working cooperatively on a project. Once coders appear to get the hang of using ScratchJr, they can begin to work independently.
More experienced coders
Because ScratchJr is not inherently difficult, experienced coders might get bored with simple projects. To help prevent boredom, ask if they would like to be a “peer helper” and have them help their peers when they have a question. If someone asks for your help, guide them to a peer helper in order to encourage collaborative learning, and remind them the helper is “hands off” and does not take over working on another person’s project.
Another approach is to encourage experienced coders to experiment with their code or give them an individual challenge or quest to complete within a timeframe (e.g., a reverse engineering challenge).
Debugging Exercises (1-5+ minutes each)
Debugging exercises
Resources and suggestions
Standards reinforced:
- 1A-AP-14 Debug (identify and fix) errors in an algorithm or program that includes sequences and simple loops
Practices reinforced:
- Testing and refining computational artifacts.
Concepts reinforced:
- Algorithms
- Control
Display one of the debugging exercises and ask the class what they think we need to fix in our code to get our project to work correctly. Think out loud what might be wrong (e.g., did I use the wrong trigger block? Did I forget to repeat something? Did I put a block in the wrong place? Am I missing blocks?, etc.). Explain that mistakes in code are called bugs. To fix the bugs students need to find the bug and get rid of it. This is called debugging. Ask the class to talk with a neighbor about how we might fix the code. Have a volunteer come up to try and debug the code (or demonstrate how). Repeat with each debugging exercise.
Unplugged Lessons and Resources
Standards reinforced:
- 1A-AP-08 Model daily processes by creating and following algorithms (sets of step-by-step instructions) to complete tasks
Although each project lesson includes suggestions for the amount of class time to spend on a project, BootUp encourages coding facilitators to supplement our project lessons with resources created by others. In particular, reinforcing a variety of standards, practices, and concepts through the use of unplugged lessons. Unplugged lessons are coding lessons that teach core computational concepts without computers or tablets. You could start a lesson with a short, unplugged lesson relevant to a project, or use unplugged lessons when coders appear to be struggling with a concept or practice.
Suggested unplugged lessons:
- A beginner unplugged lesson on using algorithms to move a "robot" (coder) around a path.
- Events are a great way to add variety to a pre-written algorithm. Sometimes you want your program to be able to respond to the user exactly when the user wants it to. That is what events are for.
Reflection and Sharing
Reflection suggestions
Coders can either discuss some of the following prompts with a neighbor, in a small group, as a class, or respond in a physical or digital journal. If reflecting in smaller groups or individually, walk around and ask questions to encourage deeper responses and assess for understanding. Here is a sample of a digital journal designed for Scratch (source) and here is an example of a printable journal useful for younger coders.
Sample reflection questions or journal prompts:
- How did you use computational thinking when creating your project?
- What’s something we learned while working on this project today?
- What are you proud of in your project?
- How did you work through a bug or difficult challenge today?
- How did you help other coders with their projects?
- What did you learn from other coders today?
- What’s a fun algorithm you created today?
- What’s something you could create next time?
- What questions do you have about coding?
- What was challenging today?
- What new drawing tools did you learn about?
- Is this a realistic simulation of outer space?
- Why or why not?
- How could you make it more realistic (e.g., add gravity)?
- What actions did you give to the different sprites?
- Why?
- What could you simulate that you’re learning about in your other classes (e.g., plant growth cycle, solar system, rain cycle, parts of a plant, and other K-2 science standards)?
- More sample prompts (may need adapting for younger coders)
Sharing suggestions
Standards reinforced:
- 1A-AP-15 Using correct terminology, describe steps taken and choices made during the iterative process of program development
Practices reinforced:
- Communicating about computing
- Fostering an inclusive culture
Concepts reinforced:
- Algorithms
- Control
- Modularity
- Program development
Peer sharing and learning video: Click here (1:33)
At the end of class, coders can share with each other something they learned today. Encourage coders to ask questions about each other’s code or share their journals with each other. When sharing code, encourage coders to discuss something they like about their code as well as a suggestion for something else they might add
