Module 7 Study Guide: Building Something Real
Key Vocabulary
| Word |
What It Means |
| Design Thinking |
A way of thinking carefully before you build. You ask WHO, WHAT, and HOW before starting. |
| Brainstorming |
Coming up with lots of ideas without judging them. All ideas are welcome during brainstorming! |
| Storyboard |
A set of drawings that show what happens in your project, scene by scene. Like a comic strip of your plan. |
| Sprite |
A character or object in Scratch. Each sprite can have its own code, costumes, and sounds. |
| Backdrop |
The background image behind your sprites in Scratch. You can have multiple backdrops and switch between them. |
| Iteration |
Making something better by trying it, testing it, and improving it. Creators iterate many times! |
| User Testing |
Having someone else try your project so you can see what works well and what is confusing. |
| Feedback |
Telling someone what you think about their work. Good feedback is kind AND helpful. |
The Design Thinking Process
Design thinking has four main steps: Think, Plan, Build, and Test. Real creators go through these steps again and again to make their work better.
Step 1: Think (Lesson 1)
Ask yourself three big questions before you start:
WHO will use what I make?
WHAT should it do?
HOW will I make it?
During this step, brainstorm many ideas. Do not pick one yet -- just think of possibilities!
Step 2: Plan (Lesson 2)
Pick your best idea and make a plan on paper:
- Draw a storyboard showing what happens scene by scene
- List the sprites, backgrounds, and sounds you need
- Write down the steps in order (your sequence)
- Decide what Scratch blocks you will use
Example: For a quiz game about animals, your plan might say: "I need a cat sprite, 5 questions about animals, a way to check if the answer is right, and a score counter."
Step 3: Build (Lesson 3)
Open Scratch and build your project step by step:
- Set up backgrounds first
- Add your sprites
- Start with the "when green flag clicked" block
- Add a few blocks at a time, then test
- Keep your plan next to the computer
Build and test in small steps. Add a few blocks, click the green flag, see if it works. Then add more. This is how real programmers work!
Step 4: Test and Improve (Lesson 4)
Once your project is built:
- Test it yourself -- go through it like a brand-new user
- Have someone else try it without any explanation
- Watch what they do and where they get confused
- Ask for kind feedback
- Make improvements based on what you learned
Types of Projects You Can Build
| Project Type |
What It Does |
Skills Used |
| Interactive Story |
Reader clicks to make things happen in a story |
Sequences, conditionals, sprites, backgrounds |
| Quiz Game |
Asks questions and checks if answers are right |
Conditionals, variables, loops |
| Animation |
Characters move, dance, talk, or fly |
Sequences, loops, timing |
| Virtual Pet |
Take care of a pet by clicking to feed, play, etc. |
Conditionals, variables, events |
| Greeting Card |
Animated card with pictures, music, and a message |
Sequences, loops, sounds |
Giving Kind Feedback
The Feedback Sandwich:
- Top bread: Say something you liked.
- Filling: Share an idea for improvement.
- Bottom bread: End with encouragement.
Example: "I loved the space background! Maybe the alien could talk a bit slower so I can read everything. This is really fun -- great job!"
Important Things to Remember
Things almost never work perfectly the first time. That is completely normal and expected. Every mistake is a chance to learn and improve!
- Planning on paper first saves time and reduces frustration
- Start simple -- you can always add more later
- Test often -- do not wait until the end to see if it works
- It is okay to build over multiple sessions
- A finished simple project is better than an unfinished complicated one
- Celebrate what you made -- you should be proud!
Review Questions
- What are the three big questions in design thinking?
- What is a storyboard and why is it useful?
- Why should you build and test in small steps?
- What does "iteration" mean?
- Why is it important to have someone else test your project?
- What makes feedback kind and helpful?
- Is it normal for things not to work the first time? Why?