All pages
Powered by GitBook
1 of 7

Teaching Team

Role
Topic

Coach

Leads small group sessions, providing feedback on student milestone presentations

Session Owner

Leads regular classes, introduces new concepts and project milestones

Session Assistant

Manages Zoom logistics and supports students during classes

Backup Teacher

Provides emergency coverage when regular teachers are unavailable

Practice Session Owner

Leads practice sessions, helping students apply concepts through exercises

Coach

Overview

A coach supports 4-5 students in the Coaching session, providing feedback and guidance on project milestones. During these 2-hour sessions, students present their work and receive personalized support in small groups.

Session Structure

  • Before Session:

    • Review the week's project milestone and expected deliverables

    • Check the Students & Project Milestones tracker in the Course Sheet

  • During Session (2 hours):

    • Join Zoom 5 minutes early and claim the host

    • Create breakout rooms for student groups

    • Per student: 5 minutes presentation + 10 minutes feedback/support

    • Track progress in the Course Sheet

  • After the Session:

    • Complete handover in Course Sheet, "Students Progress" tab

Effective Feedback Guidelines

  1. Stay Positive: Balance constructive criticism with praise

  2. Be Hands-on: In the 10 min feedback/support part after every presentation, we can give feedback on what to improve or use pair programming for direct code assistance.

  3. Guide Don't Solve: Provide improvement suggestions while encouraging independent problem-solving

AI Usage Policy

Students may use AI tools to support learning but must demonstrate understanding. If a student appears to rely too heavily on AI:

  • Ask them to explain their code's reasoning

  • Remind them AI should enhance, not replace, learning

  • Document concerns in student feedback for future coaches

Resources

  • Session guidelines available in Gitbook

  • Core Sheet for tracking progress

  • Coaching slides for session structure


FAQ

How do students present their milestones?

Ideally, students first show the UI of their solution. Secondly, they walk you through the code.

Do students deliver the weekly milestone on their own or as a group?

Each student has to deliver their milestone individually.

What if we finish early?

No problem! If you see that some students still don't feel very comfortable with the milestone or haven't finished it, you can use the rest of the time to help them drive the milestone.

What if the students didn't finish their weekly milestone?

This can happen. Let's still encourage the student to present what they have or where they are at. The goal of this session is to help the students progress - not to evaluate their status quo.

Where do students submit their weekly milestone for me to review?

Students only submit their Projects on Google Classroom during the recap week. Before that, students don't submit their projects or milestones. They just present it in the coaching sessions.

What should I do if I have the impression a student fully coded their milestone using AI and does not understand the reasoning behind the code?

Students are allowed to use AI to enhance and support their learning journey. However, it should not replace it. If you sense that a student solely copied code from a GenAI tool without fully grasping what it was about, do ask them to explain to you the reasoning of why they coded that way. You can also remind them that AI should be used wisely and cannot substitute their learning. Write in the individual feedback of the studentat that point so the next coach can check if there is an improvement in the next session.


❤️ Thank you for supporting the students' progress ❤️

Session Owner

Overview

As a session owner, you lead the weekly Regular Class, introducing key concepts and guiding students through exercises. You can use prepared materials. However, you have the freedom to adapt them to your teaching style.

Session Preparation

  1. Review previous class feedback in Slack

  2. Review milestone of the week and material (Course Content)

  3. Test exercises

  4. Coordinate with the teaching assistant

  5. Add material to Google Classroom (24h before) (how to use Google Classroom")

Class Structure (2 hours)

  • Join as co-host (5 min early)

  • Previous content recap (10 min)

  • Introduce key concepts with live coding and or exercises (45 min)

  • Hands-on practice (45 min)

  • Introduce next milestone (10 min)

Teaching Materials

  • Head over to the: Course Content

Time Management Tips

  • Focus on core concepts introduction

  • Point students to additional resources for deeper learning

  • Use recap weeks to cover missed content

  • Direct students to Q&A/support sessions for extra help

Resources

  • Teaching Guidelines

  • Session instruction slides

  • Student Hub - Gitbook

  • Class Engagement Resources


FAQ

What if it is too much content to cover?

We fully understand this concern! Usually, the input sessions cover quite a vast range of topics, as there is only one regular class per week. The idea for the regular class is to give an idea of the concepts and an introduction to how to get started with the concept. The students dive deeper into the concepts by working with them during the weekly milestones. The students can get support in Practice Sessions and coaching if a concept is unclear.

What if I didn't manage to cover all the content?

This happens! You can share the respective resources in Gitbook with the students to help them review the concepts that weren't covered. Furthermore, the recap week offers space to review concepts that need more clarification.

Session Assist

Overview

As a session assistant, you provide technical and administrative support during Regular Classes. You open the Zoom call, track attendance, help answer questions, and provide support in break-out rooms.

Key Responsibilities

  1. Technical setup and support

  2. Student attendance tracking

  3. Question moderation

  4. Breakout room management

Session Checklist

Before Class:

  • Coordinate with the session owner

  • Review class content

During Class:

  • Join Zoom Call (link pinned in Slack and Google Calendar)

  • Claim the host (host key pinned in Slack)

  • Make the Session Owner co-host on Zoom (safety measure)

  • Start cloud recording

  • Monitor student questions

  • Support breakout activities

  • Track attendance

After Class:

  • Share feedback on the class and student engagement in the Slack handover bot for team visibility

Important Links

All essential links (attendance tracker, Zoom) are bookmarked in Slack.


FAQ

I can't find the attendance tracker

The link to the attendance tracker is pinned in Slack

I can't find the Zoom link

The Zoom Link is in your Google Calendar

Backup Teacher

Overview

Backup teachers provide emergency coverage when teachers cannot attend class. No session attendance is required unless called upon.

Substitution Process

  1. Absent teacher posts in #teachers Slack channel and tags @backup teacher

  2. Backup teacher confirms availability

  3. Role assignment:

    • If assistant is absent: Backup becomes assistant

    • If lead is absent: Assistant becomes lead, backup becomes assistant

Practice Session Owner

Overview

As Practice Session Owner, you lead a 2-hour weekly session where students practice concepts from the previous class and get help with their weekly milestone. The focus is on hands-on exercises and clarifying questions.

Session Preparation

  • Review concepts from the previous class

  • Prepare practice exercises

  • Review weekly milestone requirements

Running the Session

  1. Start Zoom session (5 min early)

  2. Claim host and start recording

  3. Guide students through practice exercises

  4. Address questions about concepts and milestone

  5. Document key points covered in Slack afterward

Session Management Tips

  • Balance exercise time with Q&A

  • Use breakout rooms for group practice

  • Provide additional examples when needed

Practice Material

  • Head over to Course Content


FAQ

What if I finish early?

In general, that is not a problem! You can go deeper into a particular issue or recap on a topic more extensively. However, it is fine to finish early.

What shall I do if there are too many questions?

Let's start with the questions that you think could be the biggest roadblockers.

What if there is a student with a question that is very specific to their machine?

Let's answer these questions last. Alternatively, ask if other teachers can support the student bilaterally on Slack.

What if I cannot solve a question?

This is absolutely normal. You can ask the other teachers on Slack to give an answer in the thread.

❤️ Thank you for helping the students progress ❤️

Project Reviewer

The Project Reviewer reviews the project submissions of the students.

Review Tool

Project are reviewed from Google Classroom. Students submissions land under the "Grades" section. Just click on the submission link and add comments for review via the chat function. Everything be kept private and only visible to the reviewer and the students themselves.

Why to work in projects?

💡Learning by Doing - The best way to learn about a concept is by applying and trying it out yourself. Let’s help the students to fully understand the concepts by actively working on them.🚀 Grow through Practice - Through projects students practicing, coding, crafting and revising the material. The more they practice, the better the students get! Let’s help them grow. ❓Get Feedback - Students try out the concepts in milestones. In the project submissions, teachers might get a better understand which concepts need further elaboration.

Project Submission & Feedback Process

  1. Assign the project submission in Google Classroom, including a specific date and time.

  2. Review the submitted project and provide constructive feedback.

Tips for reviewing

  1. Positivity - It can happen easily that feedback only points out the mistakes, but it’s important to give positive feedback as well. Commenting on aspects that you liked about the code is crucial to make the students more confident. We also learn from what we did well.

  2. Specific - Try to make your feedback as specific as possible, so the students know which part of the code or result needs improvement.

  3. Suggestions - Good feedback contains suggestions for improvement. This way, the students will have ideas on how to improve the code, and you will push them in the right direction. Keep in mind the balance between suggestions and self-study; giving away the solution is not always the best thing to do.

Take a look at Google Classroom to know how to ask students to submit their project and assess their work.