Organiser un atelier robotique pour étudiants : guide pas à pas

Quick answer

Plan a student robotics workshop by starting with one clear learning goal, matching kits to the age and experience in the room, and building the hardest model yourself before the session. Keep groups small, write a timed run sheet, and prepare a low-tech backup activity. If you want a proven starting point, a Makeblock workshop format using mBot-S for beginners or mBot Ranger for older students covers most school and club settings.

A robotics workshop fails for boring reasons: too many students per kit, a build that takes twice as long as planned, or a missing cable discovered at minute three. None of that is about robotics. It is about planning.

This guide walks through the same sequence we use when setting up a student robotics workshop, from the first goal statement to the final pack-down. It assumes you have a room, a budget, and a group of learners, and that you would rather find the problems during rehearsal than in front of thirty kids.

Step 1: Define one learning goal before you pick anything

Write down what a student should be able to do by the end of the session: build a robot that follows a line, program a sensor to react to light, or explain what a loop does. One goal, one sentence. This single decision filters your kit list, your timing, and your volunteer needs.

A workshop with three goals usually achieves none of them. If your goal is programming, buy kits that are quick to assemble so build time does not eat the coding time. If your goal is mechanics, choose a kit with more building components and accept that coding will be lighter.

• Checkpoint: if you cannot state the goal in one sentence, the workshop is not ready to plan.

Step 2: Match kits to age, group size, and room

For a beginner student robotics workshop, mBot-S Educational STEM Classroom Kits for Schools & Groups is built around one robot per one or two students, with expandable building components, electronics, and a toolkit included. That ratio matters more than any specification: shared kits create idle students, and idle students create behavior problems.

For older or more experienced groups, Makeblock mBot Ranger: 3-in-1 Robotics Kit for Building Robots from Scratch offers three build forms: a robot tank, a self-balancing robot, or a racing car. It supports both Scratch and Arduino C, so you can run a beginner track and an advanced track in the same room. Decide which build form you will teach before the day, or you will spend the session answering three different sets of questions.

• Common mistake: ordering exactly one kit per student and forgetting spare parts. Bring at least one spare kit for every ten.

Step 3: Rehearse the build and time it honestly

Build the model yourself, from a sealed box, with a timer running. Then multiply that time by two for a first-time student group and by three if the group is under ten years old. This is the single most useful number in your planning document.

During rehearsal, note every point where you had to reread an instruction or hunt for a part. Those are the moments where the room will stall. Prepare a short demo or a printed tip for each one.

• Checkpoint: if your rehearsal build exceeded half the total session time, simplify the model or split the workshop across two sessions.

Step 4: Write a timed run sheet with buffer

A run sheet lists each block with a start time, an end time, and a single owner. Typical blocks: welcome and safety, build, code, test and troubleshoot, showcase, pack-down. Put the showcase before pack-down, not after, so students leave on a high point rather than cleaning up.

Build in a ten-minute buffer after the build block. Something always runs long, and a buffer is cheaper than cutting the coding section that carries your learning goal.

• Common mistake: scheduling troubleshooting as free time. Name it as a block so helpers know to circulate.

Step 5: Prepare helpers, devices, and a backup plan

One helper per four to six students is a workable ratio for a first build. Brief them on the goal, the run sheet, and the two most common failure points you found in rehearsal. Give them a job title, not just a seat.

Charge every device and battery the day before, and test the app or software on the actual devices students will use. Have a no-power backup activity ready: a paper design task, a parts-identification challenge, or a walkthrough of the robot's components. If a kit fails, the group keeps learning instead of waiting.

• Checkpoint: label every kit box with its group number so pack-down and inventory take minutes, not an hour.

Step 6: Run the day, then capture what to change

Start with a two-minute demo of the finished robot so students know what they are aiming for. Circulate during the build instead of teaching from the front. When a group finishes early, give them an extension: change a parameter, add a sensor, or improve the design.

In the last ten minutes, note three things: what ran long, what confused students, and what you would cut. That note is the beginning of your next workshop plan, and it is worth more than any generic template.

• Common mistake: skipping the debrief because you are tired. Three bullet points is enough.

Robotics workshop planning checklist

1. Write the one-sentence goal: Decide whether the session is about building, coding, or both, and put it at the top of your planning document. Checkpoint: if you cannot state it in one sentence, stop and simplify.
2. Choose kits and set the student-to-kit ratio: Use mBot-S for beginners at one robot per one or two students, or mBot Ranger for mixed-ability groups that need three build forms and both Scratch and Arduino C. Checkpoint: one spare kit for every ten, and every box labeled by group.
3. Rehearse the build with a timer: Build it yourself from a sealed box, then double the time for students and triple it for younger groups. Checkpoint: if the build exceeds half the session, cut or split it.
4. Write the timed run sheet with a buffer: List each block with start, end, and owner. Put the showcase before pack-down and add a ten-minute buffer after the build. Checkpoint: troubleshooting gets its own named block.
5. Brief helpers and charge everything: One helper per four to six students, briefed on the goal, the run sheet, and the two most common failure points. Test apps on the actual student devices. Checkpoint: a no-power backup activity is ready before the first student arrives.
6. Debrief in three bullets: Note what ran long, what confused students, and what you would cut. File it with the run sheet for next time. Next step: reuse the run sheet and adjust only the blocks that failed.

Kits and workshops that fit this plan

• mBot-S Educational STEM Classroom Kits for Schools & Groups: Engages 1-2 students per pack with 1 robot, and includes expandable building components, electronics, and a toolkit. Bulk purchases can stack benefits, such as a battery pack when buying mBot and an Interactive Light Add-on Pack at six pieces. The 1-2 student ratio and included toolkit remove two common planning headaches: idle students and missing tools. Bulk benefits make it easier to equip a full class rather than a single group.
• Makeblock mBot Ranger: 3-in-1 Robotics Kit for Building Robots from Scratch: Builds three forms: a robot tank, a self-balancing robot, or a racing car. Supports both Scratch and Arduino C, and gives access to 16+ coding and robotics projects through the free apps and resources. One kit can serve a beginner track and an advanced track, which is useful when your student robotics workshop mixes experience levels. The three build forms also let you reuse the same kit across multiple sessions.
• [Workshop] Learn how to bring AI to your classroom with Makeblock - Canada: A two-session English-language workshop using CyberPi, with Session 1 on teaching machine learning and AI for grades 4-12 and Session 2 titled From Blocks to Bots. It takes place at the Sam Ibrahim Active Learning Spaces Building, University of Toronto Scarborough. If you are planning your first AI-focused workshop, attending a structured session first can show you pacing and grade-level expectations before you commit your own run sheet.

A robotics workshop is a logistics project with a learning goal attached. Nail the goal, the kit ratio, and the rehearsal, and the day runs itself. Start with one kit and one goal, and let the first workshop teach you how to plan the second.