Follow this step by step guide to turn a BBC micro:bit into a musical quiz buzzer: use it in class or at home whenever you feel the urge to work out who’s ready to answer a question first out of two teams / individuals.
This tutorial is designed for beginners with little or no programming experience in python but it’ll cover:
Loops: repeating code with a while loop
Lists: storing more than one piece of data in order
Conditional logic: using IF statements to let your code make decisions.
How to display text and images on a micro:bit screen
How to detect if a button has been pressed on a micro:bit
This post is the forth of six in a series with ideas and resources on how to make computing lessons engaging and demanding for as many students as possible. Click here for the original post.
Everyone loves to win a prize. Even if the prize is really lame. I love getting cheap and tacky Christmas presents because they’re recycled straight into prizes. The weirder the better. Most of the time though, prizes are unnecessary – students just love the respect and recognition of being appreciated, affirmed for winning – whatever that looks like in practice.
Competitions can be quick or last multiple lessons. You can compete on speed of completion, quality of ideas, depth of understanding, quantity of challenges solved, amount of help offered, level of independence / resilience displayed… pretty much anything can be made competitive.
When someone wins, others inevitably lose out so it’s never a good idea to rely too heavily on competitive projects, but an edge of competition in a lesson can do wonders to boost the pace through a dull or tricky topic.
Combine collaborative and competitive activities as a way of getting students to support each other whilst also boosting the pace and enjoyment of a lesson.
e.g. “You’re sat in teams for today’s lesson. There are four ways to win points for your team: 1) Be the first to correctly answer a question. 2) Be the first in the class to complete a challenge I set. 3) Be the first whole team to help each other complete a challenge I set. 4) Be the first whole team to be sat silently with screens off when I ask for your attention.
Mix up competitions so that sometimes you reward pace, sometimes quantity, sometimes quality, sometimes independence, sometimes assistance towards others and sometimes depth of understanding.
e.g. “Before we start the new topic today we’re going to see who’s the best at touch-typing in the class. You have 5 minutes enter as many races on play.typeracer.com as you can. The student with the highest WPM score and the student with the highest accuracy rating will win today’s …”
Liven up revision lessons or end of unit tests with interactive quizes. You can also get students to create these quizes for a homework.
e.g. “You have 20 minutes to revise “Binary / Decimal / Hex conversions”. You can use this self test quiz to help. At the end of your 20 minutes we’ll play a Kahoot to choose our binary champion.
What’s motivating my students to work quickly / carefully / creatively? What incentives are there to go beyond the minimum expectations?
Example Activity: Competitive Programming in Scratch
Split your class into teams and get them to compete as a team to solve a range of programming challenges. This link outlines how to do this in a way that promotes independence, resilience and collaboration as well as boosting computational thinking skills.
This series of posts aims is aimed at UK secondary school teachers to give some free ideas and resources in order to help make computing lessons engaging and inclusive in order to help attract more and more students to continue with the subject at GCSE and beyond.
When students are choosing their GCSE options they seem to love asking teachers why we chose to teach our subjects.
Often, I can almost see the cogs turning inside some of my students’ heads, weighing up whether they should choose Computing over Art; ticking off the benefits of each subject as they make the first real choice that might affect the rest of their lives.
Whatever they use to make up their mind – who teaches the subject / what their friends are choosing / what they’re good at / what they enjoy – there’s clearly a lot more that we can do to promote Computer Science as a viable, challenging, enjoyable and worthwhile option. The national figures show a pretty poor GCSE uptake of GCSE Computer Science compared to other eBacc subjects and an abysmal uptake by girls. Boys, whilst outnumbering girls at KS4 and beyond, are being outperformed by girls from KS2 onwards. So there’s definitely something not right there that needs addressing.
I’ve been slowly working through the brilliant advice on the CAS #include site about how to ensure that my Computing lessons aren’t just catering for people like me and it strikes me that the way to be inclusive for all also looks and sounds like the way to be engaging and stretching for all. This post aims to share some of the mistakes I’ve made as well as some of the things I’m trying to put right to make sure that all students get the most out of their computing lessons, hopefully also boosting recruitment at KS4 too.
I’ve come up with 6 Cs to use as a checklist for planning engaging and inclusive computing projects: