Skip to content

DBE Coding and Robotics Curriculum – Meeting Agenda

Meeting focus: Curriculum overview, 5-day workshop structure, and next steps
Suggested duration: 60–90 minutes
Repository: github.com/msovara/dbe-coding-robotics-curriculum

1. Welcome and introductions (5–10 min)

  • Brief introductions (name, role, school/organisation)
  • Meeting purpose and outcomes
  • Any immediate questions before we start

2. Curriculum overview (10–15 min)

  • What it is: 5-day teacher training workshop for DBE educators in coding and robotics
  • Target audience: DBE teachers (mixed experience levels)
  • Integration: Aligned with CHPC Training DSI Coding School (CHPC_INTEGRATION.md)
  • Learning outcomes: Teachers able to teach coding/robotics, run similar workshops, and integrate into DBE subjects
  • Recent updates: Days 3–5 restructured to Arduino → Micro:bit Part 1 → Micro:bit Part 2 (Code Club intro); cloud and hardware content kept as reference in resources/

3. Five-day workshop structure (15–20 min)

Day Theme Main focus
Day 1 Introduction to Coding with Scratch Computational thinking, Scratch basics, events & control, classroom use
Day 2 Advanced Scratch Programming Cloning, broadcasting, complex games, curriculum integration
Day 3 Physical Computing with Scratch for Arduino Arduino hardware, S4A setup, sensors/actuators, robotics applications
Day 4 Coding & Robotics with Micro:bit – Part 1 Micro:bit & MakeCode, inputs/outputs, flashing, robotics ideas
Day 5 Coding & Robotics with Micro:bit – Part 2 (Code Club Intro) Micro:bit Part 2, Code Club intro, mini Code Club, wrap-up & action planning
  • Daily schedule: 09:00–17:00 | Lunch 13:00–14:00 | Tea 10:30–11:00, 15:30–16:00
  • Materials per day: Lesson plan, guide(s), activities, project templates, assessment rubric
  • Reference material: Cloud computing and hardware (former Day 3/4 content) in resources/cloud-computing/ and resources/hardware/

4. Repository and key resources (10 min)

5. Discussion (20–25 min)

Choose topics that fit your meeting purpose; adjust time per topic.

  • Rollout and timing: When and where could the first workshop(s) be run? Who will facilitate?
  • Resources and procurement: What equipment is already available (Arduino, Micro:bits, computers)? Gaps and procurement priorities?
  • CHPC alignment: How will this curriculum be used alongside CHPC DSI Coding School materials? Who needs access to both?
  • Code Club: Interest in setting up Code Clubs at schools after the workshop? Support needed?
  • Training of facilitators: Do facilitators need a separate train-the-trainer session before leading the 5-day workshop?
  • Feedback and updates: How will feedback from pilots be collected and used to improve the curriculum?

6. Next steps and action items (5–10 min)

  • Agree 3–5 concrete next steps (e.g. confirm pilot dates, assign facilitator(s), finalise venue, share repo link)
  • Who is responsible for each action?
  • Next meeting or check-in date (if applicable)

7. Q&A and close (5–10 min)

  • Open questions
  • Summary of decisions and actions
  • Thank you and close

Agenda prepared for curriculum review/planning meeting. Edit as needed for your context.