The idea of launching a satellite into space might sound like a rocket science. Design Sprint 2.0 case study of Cubesat's are miniature satellites typically used for space research, technology testing, and educational purposes. Due to their small size and relatively low cost, Cubesat's have democratised access to space, making it possible for even K-12 students to participate in space missions. In this blog, we’ll explore how a CubeSat Design Sprint 2.0 can be used in K-12 education to inspire the next generation of engineers, scientists, and innovators.

 

Why CubeSats?

CubeSats are typically small, standardised satellites with dimensions of 10x10x10 cm (1U) or larger, making them accessible for student projects. Schools and educational institutions worldwide have embraced CubeSat missions as a way to:

• Inspire STEM Learning: CubeSat projects integrate science, technology, engineering, and mathematics in a real-world context.
• Promote Project-Based Learning: Building a CubeSat involves a variety of skills, from coding and electronics to problem-solving and teamwork.
• Encourage Innovation and Experimentation: Students can design unique experiments, test new technologies, and even develop new software or sensors.

By running a Design Sprint 2.0 focused on cubesat development, educators can guide students through the rapid prototyping of a satellite mission—from defining the mission goals to building a functional prototype. Let’s break down this five-day journey.

---

Day 1: Understand and Define — Setting the Mission Objectives

The first day of the Design Sprint is all about understanding the problem space and defining a clear mission. Students are introduced to CubeSats, their applications, and the constraints they must consider—such as size, weight, and power limitations.

Key Activities:

• Mission Briefing: Students learn about different types of CubeSat missions—Earth observation, technology testing, communications, and educational outreach. They also explore real-world CubeSat missions by NASA and other organizations.
• Problem Definition Workshop: Break into teams and discuss potential problems a CubeSat could address. Teams might choose a specific challenge like monitoring environmental changes, testing new materials in space, or capturing high-resolution images of Earth.
• User and Stakeholder Analysis: Identify who the end-users of the data or technology would be. Is the mission designed to provide data for climate researchers, help students learn, or inspire the general public?
• Defining Mission Objectives: By the end of the session, each team will have a clear mission statement that answers: What problem are we trying to solve? and How will our CubeSat address it?

Outcomes:

• Teams have a defined problem statement.
• Each team has drafted clear mission objectives, including what data the CubeSat will collect and how it will be used.

---

Day 2: Ideate — Brainstorming CubeSat Design and Experiments

Now that teams have defined their mission, it’s time to get creative. Day 2 is focused on brainstorming potential solutions and designing the core components of the CubeSat, including the payload (the instruments and sensors), communication systems, and power supply.

Key Activities:

• Brainstorming with Design Thinking Tools: Use tools like Crazy 8s to rapidly sketch eight potential solutions in eight minutes. Students are encouraged to think outside the box and explore different configurations, payload designs, and missions.
• Payload and Sensor Design Workshop: Introduce students to potential sensors and instruments that could be used in a CubeSat. For example, a camera for Earth imaging, a magnetometer for space weather research, or a radiation sensor for cosmic ray detection.
• Feasibility Analysis: Each team reviews their ideas for feasibility, taking into account size, weight, power, and data transmission constraints. They prioritise ideas based on impact and feasibility.

Outcomes:

• Teams have selected a primary design concept for their CubeSat.
• Teams have identified the key sensors and components required to achieve their mission objectives.

---

Day 3: Prototyping and Programming — Creating the CubeSat Blueprint

Day 3 is all about decision-making and creating a detailed plan for the CubeSat prototype. Students refine their ideas and create a step-by-step blueprint for building and programming their CubeSat.

Key Activities:

• Decision-Making Framework: Use tools like dot-voting to select the best design options from Day 2’s brainstorming session.
• Storyboard the Mission Journey: Students create a storyboard that outlines the journey of their CubeSat—from launch to mission completion. This includes key stages such as launch deployment, data collection, and transmission.
• Technical Blueprinting: Map out the technical specifications of the CubeSat, including the type of microcontroller to be used (e.g., ESP32 or Arduino Nano), power management systems (solar panels and batteries), and communication protocols.
• Writing Pseudocode: Develop pseudocode for core functionalities such as sensor data collection, onboard data storage, and communication with the ground station.

Outcomes:

• A complete technical blueprint and mission storyboard.
• Clear pseudocode for key functions, making Day 4’s prototyping smoother.

---

Day 4: Prototype — Building and Testing the CubeSat

This is where the magic happens. Day 4 is dedicated to building a functional prototype of the CubeSat using hardware like the mPython Board, sensors, and other components.

Key Activities:

• Hardware Assembly: Students build the physical structure of their CubeSat prototype. They mount sensors, integrate the mPython Board, and set up the communication modules.
• Coding and Programming: Teams start coding their CubeSat’s core functions, including data collection, storage, and transmission. Using the pseudocode from Day 3, they turn their ideas into a working program.
• Testing and Debugging: As students build their prototypes, they test each component separately—making sure sensors collect accurate data, communication protocols work, and power management is stable.

Outcomes:

• A functional CubeSat prototype that can perform basic mission operations (e.g., collecting and transmitting data).
• A list of refinements and improvements based on initial testing.

---

Day 5: Validate — Lightning Demos and Iteration

The final day is all about testing, validation, and showcasing the CubeSat prototypes. Teams present their prototypes, gather feedback, and refine their designs for maximum impact.

Key Activities:

• Lightning Demos: Each team presents a 5-minute demo of their CubeSat, explaining the mission objectives, technical challenges, and their solution. Peers and mentors ask questions and provide feedback.
• User Testing and Validation: Conduct usability testing if applicable. For example, how intuitive is the user interface? Does the prototype effectively perform its intended function?
• Iteration: Based on feedback, students make quick iterations to improve their design. This could include refining the code, adjusting sensor placement, or improving power management.
• Final Presentation: Teams present their improved prototypes along with a report on how the CubeSat meets the mission objectives.

Outcomes:

• A refined, functional CubeSat prototype.
• Final presentations showcasing the learning journey, technical skills gained, and impact of the solution.

---

Final Thoughts: Launching Student Innovation into Space

Running a CubeSat Design Sprint 2.0 is an exciting and challenging journey for both students and educators. It’s a powerful way to integrate STEM learning with real-world applications, inspiring students to think big and solve complex problems. By the end of the sprint, students will have a deeper understanding of satellite technology, project management, and rapid prototyping.

Key Takeaways:

1. Structured Innovation: The Design Sprint 2.0 framework helps students stay focused and achieve tangible results in a short timeframe.
2. Interdisciplinary Learning: Building a CubeSat involves electronics, coding, project management, and communication skills.
3. Empowerment through Prototyping: Seeing a real, functioning prototype motivates students and shows them what’s possible with teamwork and creativity.

So, are you ready to launch your own CubeSat Design Sprint 2.0? Empower your students to reach for the stars—literally—and watch as they become the next generation of space explorers and innovators.