BRAINBOX - YOUNG-ENGINEERS MARSHMALLOW CHALLENGE:

This activity is designed to provide an introductory activity for the BRAINBOX YOUNG-ENGINEERS projects.

The Marshmallow Challenge provides an excellent introduction to project-based, collaborative learning for young engineers.

• Use scientific method as a framework to make hypotheses and to record the process and discusss the results.
• Create a video documentary of the activity as you go…

1. Create groups of four students, where three are friends and one is an outsider
2. Prepare a table for each team

Before starting, assemble a Kit for each Team -Each kit to contain:

1. twenty sticks of spaghetti
2. one metre of masking tape
3. one metre of string
4. one full size (large but not jumbo) marshmallow.

Place ingredients into a paper lunch bag: simplifies distribution and hides the contents

1. Spaghetti: Ensure that you use uncooked spaghetti. Avoid spaghettini as it is too thin and breaks easily. Fettucini is too thick.
2. String: Include string that can be easily broken by hand. If the string is thick, include scissors in your kit.
3. Marshmallow: Use a name brand or private label brand of marshmallows that measure the ‘standard’ size, about an inch an a half across. Avoid mini or jumbo marshmallows. Also avoid stale marshmallows. You’ll want squishy marshmallows that give the impression of lightness.
4. Masking Tape: Get standard masking tape. Generally, you’ll want to put the tape on the side of the table, the back of a chair or a nearby wall. Rolling it in the bag tangles the tape.
5. Paper Lunch Bags: Standard size lunch bags work well as do letter size manilla envelopes.

Also ensure that you have the following tools to run the challenge:

1. Measuring Tape: Have a retractable measuring tape to measure the final height of the structures.
2. Countdown 'App' or Stopwatch: The challenge takes eighteen minutes. Eighteen minutes seems to be the magic time. Twenty minutes is too long and fifteen is too short. You can use a stopwatch, but better yet is to use a video projector and display the countdown time.
3. Video Projector and Sound System (optional): For more impact, use a video projector to deliver your presentation and for music to play during the challenge. Play exactly 18 minutes of music and end the challenge at the conclusion of the last song.

Deliver Clear Instructions - Be clear about the goals and rules of the Marshmallow Challenge. Use the Acrobat Presentation to introduce the challenge as well as to visually reinforce the instructions:

1. Build the Tallest Free-standing Structure: The winning team is the one that has the tallest structure measured from the table top surface to the top of the marshmallow. That means the structure cannot be suspended from a higher structure, like a chair, ceiling or chandelier.
2. The Entire Marshmallow must be on top: The entire marshmallow needs to be on the top of the structure. Cutting or eating part of the marshmallow disqualifies the team.
3. Use as Much or as Little of the Kit as you like: The team can use as many or as few of the 20 spaghetti sticks, as much or as little of the string or tape. The team cannot use the paper bag as part of their structure.
4. Break up the Spaghetti, String or Tape: Teams are free to break the spaghetti, cut up the tape and string to create new structures.
5. The Challenge Lasts 18 minutes: Teams cannot hold on to the structure when the time runs out. Those touching or supporting the structure at the end of the exercise will be disqualified.
6. Ensure Everyone Understands the Rules: Don’t worry about repeating the rules too many times. Repeat them at least three times. Ask if anyone has any questions before starting.

Start the countdown clock and the music with the start of the challenge.

1. Walk around the Room: Video to record the development of the structures as well as notice the patterns of innovation that teams follow.
2. Remind the Teams of the Time: Countdown the time. Usually, I call 12 minutes, 9 minutes (half-way through), 7 minutes, 5 minutes, 3 minutes, 2 minutes, 1 minute, 30 seconds and a ten-second count down.
3. Call Out How the Teams are Doing: Let the entire group know how teams are progressing. Call out each time a team builds a standing structure. Build a friendly rivalry. Encourage people to look around. Don’t be afraid to raise the energy and the stakes.
4. Remind the Teams that Holders will be Disqualified: Several teams will have the powerful desire to hold on to their structure at the end. Usually because the marshmallow, which they just placed onto their structure moments before, causing the structure to buckle.
5. The winning structure needs to be stable.

After the clock runs out, ask everyone in the room to sit down so everyone can see the structures. Likely, just over half the teams will have standing structures.

1. Measure the Structures: From the shortest standing structure to the tallest, measure and call out the heights. If you’re documenting the challenge, have everyone record the heights in their journals.
2. Identify the Winning Team: Ensure they get a standing ovation and a prize (if you’ve offered one).
3. Wrap up with the Lessons of the Marshmallow Challenge: Deliver the attached presentation or just describe some of the key lessons of the marshmallow challenge:
4. Kids do Better than Business Students: On virtually every measure of innovation, kindergarteners create taller and more interesting structures.
5. Prototyping Matters: The reason kids do better than business school students is kids spend more time playing and prototyping. They naturally start with the marshmallow and stick in the sticks. The Business School students spend a vast amount of time planning, then executing on the plan, with almost no time to fix the design once they put the marshmallow on top.
6. The Marshmallow is a Metaphor for the Hidden Assumptions of a Project: The assumption in the Marshmallow Challenge is that marshmallows are light and fluffy and easily supported by the spaghetti sticks. When you actually try to build the structure, the marshmallows don’t seem so light. The lesson in the marshmallow challenge is that we need to identify the assumptions in our project – the real customer needs, the cost of the product, the duration of the service – and test them early and often. That’s the mechanism that leads to effective innovation.

Source Tom Wujec