Hour of Code

The Hour of Code is always an event that my students and I look forward to. This year, we were lucky to have some additional resources that allowed us to expand the coding experience past using websites like Code.Org and Tynker.

I'm very lucky to have a co-teacher that is excited to try new activities, like myself. We work very well when planning and smashing some of our ideas together to create a unique experience for our students.

As always, we began Hour of Code this year with the recent Code.org video. The kids always love looking into the world of code from the professional side, especially when it relates to the anticipated movie of Star Wars, the Force Awakens.

For this particular project, students were placed into groups of 4 or 5 depending on class size. I like to use our seating chart generator in Power School, just to really mix the members of the groups up after allowing them to pick their own groups for their previous project.

We then introduced our coding activity using a Numbers spreadsheet on the iPad. Until this year, I honestly didn't realize how convenient Numbers can be to create organized projects for students. In order to get the students a copy of the spreadsheet without having to airdrop to all individual students, we provided them a link/QR code in Edmodo that they could easily download and import into their own iPad.  We walked through each activity, reviewing directions for the stations and taking any questions that they had. We planned on using about 20 minutes per rotation.

Here are some of the stations we planned:
1. Computer Coding - we used code.org so students could create accounts and as teachers we could see their projects. Plus, many were interested in the new Minecraft and Star Wars modules.
2. Fun with Floors - I started using Pixel Press Floors, Floors in the App Store, a few years ago. It still continues to be a student favorite allowing them to code and create their own video game with a different type of code compared to block or script.
3. Ollie's Obstacles - students had to construct an obstacle course for Ollie and then try to maneuver him through.
4. BB8 Bowling - we are lucky enough to also have a BB8 Sphero this year. Students had to use the Tickle Coding App (Warning: Don't have your students search it in the app store) and block code BB8. We taped out a given path on the carpet and students had to work together to program him. Great connection to mathematics, as they had to use angles.
5. Cup Coding - this was an unplugged activity from Code.org. Continues to work on students communicating and collaborating together.
6. Bit Wars - At one of my schools, the class size is much larger, so I added a 6th rotation in using littleBits circuits where students had to create an equipment piece for a Star Wars character. This idea came from the challenge that was given on their website.

Due to winter break and school activities, this project took approximately 4 weeks to complete. Each student was responsible for documenting/reflecting on their experience through questions, fake Tweets, videos and images. Boy, did they love the robotics!

Floors Game Coding

Unplugged Cup Coding

Ollie's Obstacles

BB8 Bowling with Tickle App

For some of my self contained classes, we even tried a bit of Sphero Action Painting! I've always wanted to give it a try and the kids really enjoyed it!

No computer lab? STEAM to the rescue!

As we all know, sometimes PARCC testing can cause a mixup to our weekly routine schedules. In my case, that meant losing my computer lab due to it having to be used by classes for PARCC. Boy, I can't wait until my buildings are fully 1:1 next year!

While I may have been disappointed to lose my lab at first, it was one of the best things that could have happened for my classes! Not only was I able to push into their learning environment, which I rarely have time to visit with my schedule, but I was able to dive into more STEAM based activities as I became the traveling technology teacher for 3 weeks.

So what did I exactly have up my sleeves? 4 weeks of fun that not only challenged students, but focused on team work and reflection!

I began by introducing the challenges to the students with an iMovie. My video reviewed the meaning of STEAM, but then had short videos announcing the resources we would be using during this time. This really sparked their interest and their level of excitement began to rise.

Students were broken into groups of 5. I allowed them to pick their groups because I've always been a firm believer that the choice helps students stay motivated. Since we were without digital devices during these few weeks, I printed reflection packets that were handed out to each group. Yes, I know....I PRINTED! I felt out of my comfort zone standing at the copy machine prepping for this lesson when I try really hard to remain paperless.

Getting back to the excitement.....the students were to complete rotations between 4 different STEAM based activities.

1. Architecture Challenge - non-digital hands on problem solving (this one rotated weekly)
2. Big Sphero 6 - students learned how to navigate and build obstacles for our new Spheros.
3. Makey Makey - students shared 2 Makey Makey kits to connect and create.
4. littleBits - using electronic circuits to accomplish a variety of challenges

Not only were students rotating activities each week, but they were also rotating leadership positions within their group. One thing I've noticed throughout the year, was that teamwork was something that needed a focus, encouraging more collaboration and sharing of ideas.

Each group received a labeled envelope with an activity direction sheet enclosed. For the most part, there weren't too many directions to the activities, more so starters to push each group to explore without requiring a teacher to walk them through.

Overall, I'm glad I took the time to plan all of this out. My students and faculty enjoyed the change in instruction. This also opened the door for students being aware of the resources we have for them to explore further during our Innovation Lab (20% time).