Ages 5-7: Little Inventors
- Play-based STEM and screen-light coding.
- VEX 123 robots, coding cards, maps, stories, patterns, and sequencing.
- Simple engineering habits: predict, try, observe, improve.
- Recommended class size: 6-8 students per adult.
Program Summary
Students design, code, build, test, and explain real projects.
Purpose
The program introduces elementary and middle-school students to STEM through playful robotics, beginner coding, 3D design, measurement, problem solving, and project-based teamwork.
School Fit
Lessons are structured for a classroom or library space, require no permanent installation, and can run as an after-school club, enrichment block, lunch program, or short-term pilot.
Age Groups
Three tracks keep the work developmentally appropriate.
Ages 8-10: Junior Makers
- Scratch or mBlock coding, robotics missions, Tinkercad design, and 3D printed take-home parts.
- Core coding ideas: events, loops, conditions, debugging, variables when ready.
- Recommended first pilot age group because students can build, read instructions, and collaborate well.
- Recommended class size: 8-10 students per adult.
Ages 11-12: Advanced Young Engineers
- More independent design challenges, sensors, introductory Python concepts, and deeper 3D design.
- Students plan final projects, document tests, and present design decisions.
- Recommended class size: 10-12 students per adult.
Equipment
Portable, school-appropriate equipment with adult-controlled fabrication.
STEM Robotics Kit
The core robotics platform will be the VEX 123 Classroom Bundles. VEX 123 is designed for young students and supports screen-free, touch-button, coding-card, and VEXcode 123 programming pathways.
- Best fit: ages 5-8, with extension challenges for older beginners.
- Classroom use: robot maps, coding cards, team missions, storytelling, sequencing, debugging.
- Ideal ratio: 1 robot per 2 students; acceptable ratio: 1 robot per 3 students.
3D Printer
The 3D printing platform will be a teacher-operated Bambu Lab X1C. The X1C has a 256 x 256 x 256 mm build volume, a hardened steel 0.4 mm nozzle, an enclosed frame, Bambu Studio software, and common classroom-friendly PLA support.
- Students design models in Tinkercad; adults slice, start, stop, and remove prints.
- Default material for school use: PLA filament.
- Projects are kept small so prints can be queued safely and predictably.
Equipment Not Included
No laser cutter is brought to the school, used at the school, or included in the student curriculum. Any previous laser-focused activities have been replaced with safe prototyping, cardboard engineering, 3D printed connectors, and classroom material challenges.
Class Format
Each class follows a predictable hands-on rhythm.
| Time | Activity | Purpose |
|---|---|---|
| 5 minutes | Welcome and question of the day | Focus attention and introduce the problem. |
| 5-10 minutes | Short demo or mini lesson | Teach one new concept before students build. |
| 25-45 minutes | Build, code, test, and improve | Give students the main hands-on learning time. |
| 5-10 minutes | Share and reflect | Practice explaining design choices and debugging. |
| 5 minutes | Cleanup and charging/storage | Build responsibility and protect equipment. |
12-Week Curriculum
Core course map, with the laser unit replaced.
1
What Is STEM?
Students learn that engineers solve problems by testing and improving.
Day 1: Welcome to Inventors Lab
Main idea: Engineers solve problems by building, testing, and improving.
Paper tower challenge, earthquake test, and one improvement explanation.
Day 2: Human Robot and Safety Bootcamp
Main idea: Coding means giving clear instructions. Safety rules make creativity possible.
Human robot maze, clear instructions, debugging, and maker safety routines.
2
Scratch / mBlock Basics
Students learn sprites, events, motion, sounds, loops, and patterns.
Day 3: My First Animation
Main idea: Programs start with events and run commands in order.
Create a simple animation that starts with an event.
Day 4: Loops and Patterns
Main idea: Loops repeat actions and make code shorter.
Use repeat blocks to make code shorter and easier to change.
3
Games and Debugging
Students learn conditions, if/then logic, bug-fixing, and test habits.
Day 5: If/Then Game Logic
Main idea: Programs can make decisions using conditions.
Build a catch-the-star game with working rule-based behavior.
Day 6: Debugging Detective
Main idea: Debugging is a normal part of coding.
Fix broken mini-programs and describe the bug and the solution.
4
Meet the Robot
Students connect coding instructions to physical robot behavior.
Day 7: First Robot Movement
Main idea: Robots sense, think, and act.
Move, turn, stop, and create a planned robot path using age-appropriate robot controls.
Day 8: Robot Maze Challenge
Main idea: Break a large path into smaller steps.
Use decomposition, testing, and adjustment to solve a maze mission.
5
Robotics Patterns and Data
Students observe robot behavior, collect simple results, and improve programs.
Day 9: Robot Route Planner
Main idea: Sensors and observations help robots make decisions.
Use coding cards or block code to plan a route and predict the outcome.
Day 10: Track Challenge
Main idea: Robots use feedback to correct movement.
Create a repeatable route, test it several times, and explain what changed.
6
Robotics Mission
Teams plan and run a themed mission with roles and constraints.
Day 11: Robot Rescue Planning
Main idea: Engineers plan before building.
Plan a rescue route using maps, pseudocode, and team roles.
Day 12: Robot Rescue Test Day
Main idea: Test, improve, and present a robot mission.
Test, improve, and demo a robot mission for reliability and teamwork.
7
3D Design With Tinkercad
Students learn length, width, height, shapes, grouping, alignment, holes, and layers.
Day 13: First 3D Design
Main idea: 3D designs are built from shapes.
Create a printable name tag, keychain, or robot-themed object.
Day 14: Design for Printing
Main idea: Printable designs need rules.
Improve the model for flat bottoms, no floating parts, size limits, and STL export.
8
3D Printing and Measurement
Students learn how 3D printers make objects layer by layer and how measurement affects fit.
Day 15: How 3D Printers Work
Main idea: 3D printers build objects layer by layer.
Observe a safe printer demo, inspect layer lines, and measure sample parts.
Day 16: Functional 3D Printed Part
Main idea: Designs can solve practical problems.
Design a cable clip, game token, pencil topper, phone stand, or robot accessory.
9
Safe Prototyping and Materials Engineering
This replacement unit uses cardboard, paper, tape, craft sticks, connectors, 3D printed parts, and recycled classroom materials.
Day 17: Structures and Mechanisms
Main idea: Materials and shapes change how strong, stable, and useful a prototype is.
Build bridges, ramps, gates, grippers, or robot obstacles while learning strength, stability, hinges, and constraints.
Day 18: Prototype, Test, Improve
Main idea: Prototypes improve when students measure results and reinforce weak points.
Run a materials challenge, measure performance, reinforce weak points, and explain one design improvement.
10
Final Project Planning
Teams choose a theme and plan a final build that combines code, robotics, design, and fabrication.
Day 19: Final Challenge Launch
Main idea: Combine coding, robotics, and fabrication into one project.
Choose from smart city, rescue course, carnival game, rover mission, habitat, cleanup robot, or museum guide.
Day 20: Prototype Day
Main idea: Prototype quickly before final building.
Build a cardboard prototype, start robot code, and start the 3D design file.
11
Build and Debug
Students move from prototype to final project through testing and revision.
Day 21: Production Build Day
Main idea: Teams build final components and manage workflow.
Label files, manage the print queue, build final parts, and conference with the instructor.
Day 22: Testing and Debugging Day
Main idea: Reliable projects come from testing and improving.
Test one thing at a time, record results, simplify when needed, and improve with evidence.
12
Showcase
Students practice explaining what they built, how it works, and what they improved.
Day 23: Final Polish and Practice
Main idea: Engineers communicate their design clearly.
Finalize demos and use sentence frames for a short, clear presentation.
Day 24: STEM Showcase
Main idea: Celebrate, demonstrate, and reflect.
Present final projects, demonstrate robot behavior, reflect, and receive certificates.
Safety and Operations
Students create; adults manage equipment and classroom safety.
General Safety
- Walk only in the maker area.
- Food and drinks stay away from electronics.
- Tools wait until the instructor gives permission.
- Students report heat, smells, smoke, sparks, damaged batteries, or broken parts immediately.
3D Printer Safety
- Students do not touch the printer while it is operating.
- The instructor slices files, starts prints, removes parts, and handles maintenance.
- PLA is the default material for school sessions.
- Safety glasses may be used when supports or small plastic pieces are removed by an adult.
Classroom Routines
- Start with hands empty and eyes on the demo.
- Teams rotate roles: builder, coder, tester, and safety captain.
- Debugging routine: check code, ask partner, check instruction card, then ask instructor.
- Cleanup includes saving work, returning parts, charging robots, and checking the floor.
Assessment
Progress is measured through observation, explanation, and teamwork.
| Skill | What We Look For | Simple 1-4 Scale |
|---|---|---|
| Coding | Student can sequence steps, use loops or conditions when appropriate, and debug one change at a time. | 1 = needs support, 2 = works with help, 3 = independent, 4 = explains and helps others. |
| Robotics | Student can predict robot behavior, test the route, and improve the program. | Progress is based on testing habits, not only on whether the robot succeeds immediately. |
| Design | Student can explain what the object is for and how the design changed after testing. | Students are encouraged to document mistakes as useful data. |
| Collaboration | Student participates in a role, listens to teammates, shares materials, and helps with cleanup. | Teamwork and safety are part of the learning goals. |
Materials List
Items needed for a pilot class.
Instructor Brings
- VEX 123 Classroom Bundle robots, coders, coding cards, fields, and charging/storage materials.
- Bambu Lab X1C 3D printer, filament, approved sample prints, and printer safety materials if approved by the school.
- Prototype supplies such as cardboard, paper, tape, craft sticks, string, binder clips, markers, rulers, and printed challenge cards.
- Lesson plans, role cards, reflection sheets, rubrics, and showcase certificates.
School Provides or Confirms
- Classroom, library, or maker-space area with tables and open floor testing space.
- Access to student computers/tablets when Scratch, mBlock, VEXcode 123, or Tinkercad lessons are used.
- Power outlet for charging robots and, if approved, supervised 3D printer use.
- Student roster, pickup procedure, allergy/safety notes, and school behavior expectations.
Recommended Pilot
A practical first launch for the school.
Best First Offer
Start with an 8-10 student pilot for ages 8-10, once per week for 8-12 weeks, then expand to younger VEX 123 sessions or older advanced design sessions after the first showcase.
Final Showcase
The program ends with a short showcase where students demonstrate robot missions, display 3D designed objects, explain one challenge, and describe one improvement they made.
References