Only this pageAll pages
Powered by GitBook
Couldn't generate the PDF for 281 pages, generation stopped at 100.
Extend with 50 more pages.
1 of 100

Teacher Hub

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Timeline

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Full Stack Track

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

About ReDI School

We are ReDI

Founded in 2015, ReDI School of Digital Integration is a non-profit tech school providing migrants and marginalized locals free and equitable access to digital education.

We offer our learners high-quality coding and basic computer courses in combination with a unique career and mentorship program, which includes the chance to collaborate with tech companies, startups, and digital industry leaders.

We aim to provide our learners with valuable digital skills, a growth mindset, strengthened career skills, and a strong network of tech professionals to help create new opportunities for all.

Digital Career Program

We provide advanced tech skills training and career support to tech-savvy refugees and people with a forced migration background to accelerate their professional integration in the tech industry. Available in Berlin, Munich, NRW, and Hamburg.

Our Mission

ReDI School offers education to break down barriers and connect the leaders of tomorrow. We use technology to connect human potential with employment opportunities with dignity and humility.

Our Vision

To provide access to free digital education and create pathways to employment in the tech industry.

Our Learners

Our students come from diverse backgrounds and are in different situations. Every semester we get a different batch. Last semester we had:

  • Students from over 32 different nationalities

  • On average 31 years old

  • Backgrounds ranging from Finance to Engineering to Biology. The majority of our students have a bachelor's degree.

  • Employment status once joining the course:

    • Underemployed: Around 40% are underemployed and want to change careers.

    • Unemployed: Around 35% are unemployed and actively looking for a job.

    • Students: 25% are university students preparing for the job market.

Our students take the course to get a job in the industry.

ReDI Community in Numbers

Volunteer Rights

🎖️What's in for you by joining our Mission

  • Help close the digital divide and empower others through the transformative power of technology

  • Make a lasting impact on individuals striving to rebuild their lives and embrace new opportunities

  • Join a vibrant, diverse community of dedicated volunteers—share your experiences, learn from others, and grow together

  • Develop valuable soft skills that enhance both your personal and professional life, and showcase your growth with a recognized certificate at the end of the course

💌 Know your Rights!

  • You can ask for a recommendation letter

  • Always have the right to feel safe and supported, and that your work is respected

  • You have the right to be trained in teaching skills

  • You can change, amend and negotiate the class rules with your students

  • You don’t have to deal with every situation on your own!

  • Please reach out to us if you need any kind of support, regarding a student in your group who may be falling behind, technical set-up, content ideas... you name it, we are here for you!

Ask for support when needed! You find contact details here:

ReDI Team

Community Guidelines

ReDI Values

At ReDI, we follow the four values, which give an orientation on our behaviours and actions, both within the community and within ourselves as a team. Here what the ReDI values mean to us:

In the sense of impactful. We are a community moved by the wish to help others grow and are actively oriented towards this goal. Being helpful means trying to generate a real change in the life of others.

This is the most important value and has to do with experimenting in a fun and playful fashion. It refers to trying out new things and, if need be, making mistakes together and learning from them. It also means trying to build the "ideal learning environment" we all wanted to have in our own personal experiences.

Means trustful, in relation to the scope of our actions. We want to deliver the best quality of learning services to our learners because they are themselves relying on us for their education and deserve high-quality training from professionals like you.

We are "partners in crime" for our community to do things they didn’t even think they’d be capable of doing at the beginning. It means empowering others to understand they can cross their own limits, far beyond what they might have originally thought. Change is reflected the students also by the teachers because, through their flexibility and willingness to change, they are leading students to achieve their goals.

Our DEI Statement

Our Code of Conduct

ReDI School aims to be a safe learning environment for all of its community members. The ReDI Code of Conduct sets the standards that allow us to keep our community safe and healthy, both online and offline. It establishes standards necessary to maintain and protect an environment conducive to learning and in keeping with the objectives of the program. The code of conduct is important to:

  • maintain and protect an environment conducive to learning and in keeping with the objectives of our ReDI School programs

  • protect our community and ensure that EVERYONE feels safe and comfortable in the online environment

By signing the Volunteer Agreement at the beginning of their teaching experience, volunteers agree to respect the ReDI Code of Conduct during their volunteer experience and interactions with students, other volunteers, as well as with the ReDI team and community.

Code Outline
  • The ReDI community comprises students and volunteers united by their participation in and commitment to respectful intellectual exchange. Therefore, ReDI School commits to providing an environment where the rights, safety, dignity and worth of every individual are respected.

  • The intellectual exchange also implies acting responsibly in a community setting, with respect for the rights of other students and volunteers and for the property, shared resources, and agreements associated with that community.

  • Since the code is directed toward maintaining the standards of the ReDI community and the local community, ReDI School reserves the right to dismiss students or volunteers whose conduct is objectionable and/or interferes with the educational objectives of the School or another member of the community.

How does ReDI define objectionable conduct?

Objectionable conduct is defined as harassment, unwanted contact, or otherwise objectionable behavior, whether directed at or independent of other ReDI School community members. This includes:

  • Insults, gestures, or abusive words, in the immediate presence and/or directed to another person that may reasonably cause emotional distress or provoke a violent response. How this applies to an online environment:

    • The direct or indirect use of insults, degrading language, or disrespectful comments on the opinions of others during video calls and/or in written instant communication are not tolerated under any circumstances.

    • Community members are expected to refer to their colleagues by their preferred names and personal pronouns (such as “he/him,” “she/her,” or “they/them”), as long as they have been communicated. Failure to do so on purpose will be considered abusive behaviour and will not be tolerated under any circumstances.

  • Lewd or indecent conduct during a ReDI School sponsored activity. This includes, but is not limited to, any unauthorised use of electronic or other devices to make an audio or video record that would be an invasion of privacy. How this applies to an online environment:

    • The video recording or taking of screenshots involving other community members during classes, events and any other ReDI activity will only be tolerated with the explicit permission of all the parties involved. Successive use of such media content in different platforms and contexts will require the explicit written permission of all the parties involved. Failure to secure an explicit authorisation will constitute a breach of the Code of Conduct and will not be tolerated under any circumstances.

  • Other types of prohibited discrimination are discriminatory harassment, nonconsensual personal contact, and sexual harassment as defined by law. How this applies to an online environment:

    • Instant messages, emails, voice messages, or video gestures containing discriminating attitudes towards other ReDI community members will not be tolerated under any circumstances, irrespective of whether they take place during a ReDI event or outside of this context.

    • Nonconsensual personal contact in an online environment includes unauthorised contact of another community member for sexual and/or romantic purposes or in a way that could reasonably cause emotional distress.

What to do if you experience any of the situations above?

If you experience any of these situations or feel uncomfortable for any reason, ask for support from the ReDI Team safety officers!

What we can do for you:

  • Just listen if anything at ReDI is making you uncomfortable

  • Address complaints

  • Offer conflict coaching

Who to contact:

  • Pierluigi Delgiudice - Local Head DCP Online - pierluigi@redi-school.org - Slack: @gigi

  • Tamara Fantinato - Program Manger - tamara@redi-school.org - Slack: @Tamy

Building Inclusive Learning Spaces

This engaging session covers essential topics such as teamwork, leadership, inclusion, and practical techniques to turn classroom diversity into a strength.

It will equip you with valuable skills for leading groups effectively, fostering collaboration, and creating safe spaces for open discussion. You’ll learn strategies to enhance communication and promote shared responsibility within your classroom.

Additionally, you'll explore how to build trust, motivate your team, and use tools to strengthen group cohesion. Through empathy-driven approaches, you’ll gain insights on how to support both yourself and your students, fostering a more inclusive and compassionate learning environment.

Finally, the session offers techniques to appreciate and leverage the diversity of perspectives in your classroom, helping you lead inclusive sessions that inspire active participation, mutual respect, and a strong sense of belonging.

Help

I cannot teach

What to do if you cannot teach

First of all, no worries! Let's ask the team for a substitute.

  • Up to one week before the session, inform your team and ask for a substitute. Use @channel to get visibility.

Training by , tailored specifically for ReDI's volunteer teachers.

Two days before or sooner, reach out to your team channel AND contact your to ask for support.

Alejandro Reyes Alpízar
Community Guidelines
I cannot teach
I am dropping out
Volunteer Rights
Get in Touch for Support
course manager

Welcome

Starting in Spring 2025, the volunteer team will consist of volunteers from different locations in Germany. If you are a continuing volunteer, the course format might be new for you. In this hub, you will find more information on each course, how it is set up, and how to support it. The resulting course offer is the following:

Courses

More Info on all Courses and Tracks:

Full Stack Track:

Data & AI Track

Tech & Design Basics

Career Services

Why offering Career Services?

At ReDI, we believe career success is driven by both skills and connections. That’s why unique Career Services complement our tech training to help learners enhance soft skills and grow their professional networks. Through collaborations with companies in the German tech sector, we create direct pathways for learners to connect with industry professionals, recognizing that career transitions are about both what you know and who you know.

Spring 2025 Offer

Starting this semester Career Services will be divided into two parts:

  • Career Orientation for starters, versus intermediate and advanced tech classes

  • Bootcamps Career Project for Bootcamps participants (still in development)

The career services listed above are recommended to students of the courses listed below. However, we leave to our learners the choice and chance to participate in career activities, based on individual needs.

Starter Courses in DCP Online
Int & Adv Courses in DCP Online

HTML / CSS

JavaScript

Python Foundations

Data Analytics

Infrastructure Basics

Machine Learning / AI

Creative Communications

Data & Full-Stack Circles

Resources & Support Systems for Learners

  • Learning Plans on IBM SkillsBuild Platform

  • Non-mandatory career support onboarding sessions for learners, with details about career events

  • Online Open Hour every week to answer questions about career services

  • Dedicated slack channel #25s_talent_and_career_support

Hello, volunteer! Thanks for checking out the teacher hub and for supporting the ReDI students!

Here the three most impactful career services we offer to our students. .

: Career services info, tips and tricks, partners info

Contacts: Slack user @Paulina - Email:

⭐
⭐
HTML / CSS
Javascript
Full Stack Bootcamp
Full Stack Circle
Python Foundations
Data Analytics (Online)
Machine Learning / AI (Online)
Data Circle
UX/UI Bootcamp
More here
Talent Success Learner Hub
career@redi-school.org

Planning Session

The Planning Session is the first meeting where the volunteer teaching team comes together as a group for the first time.

It is recommended to come to the session having reviewed:

  1. The lesson content

  2. The course structure

  3. The roles and their responsibilities

  4. The available tools

This will help clarify any doubts or questions that may arise from the beginning.

Before the session, it’s important to share your availability in advance, as this meeting is where we’ll assign the roles each person will take on throughout the semester. Role distribution will be based on your interest, experience, and availability in relation to the content.

The goal is to ensure that everyone understands their role — in the classroom, in the course, and as part of the team — and can collaborate effectively to provide students with the best learning experience possible throughout the semester.

I am dropping out

Drop Out

We understand that sometimes, due to personal or professional circumstances, a teacher may make the decision to leave the class. We want to express our respect for their choice and appreciate the time and effort they have dedicated so far. We are here to support in the transition and ensure that the process is as smooth as possible for everyone involved.

  • After that, notify your team; you can mention your reasons

  • You will be removed from the Course Slack Channel and Google Calendar

  • Let us know if you need any proof of volunteering

Please notify someone from the about your decision

Finally, fill out

ReDI Team
this questionnaire

Get in Touch for Support

ReDI DCP Online Course Managers Team

This semester, instead of having separate Student and Volunteer Managers following up on students or teachers across different courses, we have Course Managers, each overseeing three to four courses on both volunteers and learners side.

Course Managers will actively monitor course health and suggest improvements to the program management and tech lead based on the information they collect, in order to enhance the learning and volunteering experience for each course. If you have any questions or feedback, or need support, your Course Manager will be your main point of contact.

ReDI DCP Online Safety Officers

Safety Officers play a crucial role in protecting the community and ensuring that everyone feels safe, respected, and comfortable in the online environment. If you experience any situations where you feel like our community guidelines or code of conduct have been breached, or you feel uncomfortable for any reason, ask for support from the ReDI Team safety officers!

What they can do for you or our students:

  • Just listen if anything at ReDI is making you uncomfortable

  • Address complaints

  • Offer conflict coaching

Who to contact:

  • Pierluigi Delgiudice - Local Head DCP Online

  • Tamara Fantinato - Program Manger

Feedback that Works

This session, designed for ReDI’s volunteer teachers, you'll explore effective strategies for giving and receiving feedback and creating a constructive feedback culture.

Through real scenarios from your own experiences, you'll learn how to deliver clear, supportive, and effective feedback. You'll also develop skills to receive feedback openly, process it constructively, and turn it into meaningful improvements—feedback that truly works!

Don’t miss this opportunity to enhance collaboration, improve communication, and create a more supportive and productive environment!

**Please note: 2 courses in Spring 2025 are entirely managed and run by corporate volunteer teams: Infrastructure Basics (online) and Creative Communication (hybrid in Hamburg). Therefore those opportunities are not listed here.

Reduce Teacher Talking Time

This training covers strategies to reduce Teacher Talking Time (TTT) and create learner-centered classrooms, focusing on student engagement, maximizing participation, and effectively using silence.

Throughout this interactive session, you will discover practical strategies and hands-on activities to develop a classroom focused on student learning. You’ll learn how to design lessons that promote participation and assess comprehension without over-explaining. We will also cover when teacher input is most valuable and how to use intentional silence to give students time to think, process, and respond meaningfully.

Ultimately, the goal is to empower you to create an environment where students become more engaged and independent, resulting in a dynamic and inclusive classroom.

This session is designed to help you reduce teacher talk, build student-centered classrooms, and encourage student autonomy. With 's vast experience in teacher training, online education, and language learning, she will share effective techniques to engage students actively and minimize unnecessary explanations.

Carla Montrucchio

Timeline

Preparation Phase

Teachers Onboarding & Planning Sessions

⏰ Feb 12th - 20th, 2 meetings per course

A ReDI volunteer journey starts with a welcome to the ReDI community! During teachers onboarding & planning sessions, we:

  • Welcome new & returning volunteer teachers to the community

  • Share semester mission, goals & timeline

  • Plan / review the outline of the coursw

  • Align on teaching roles & processes

  • Prepare for students selection process and course kick off

Students Screening / Interviews

⏰ Feb 24th - 28th, 1 session, 2 hours, optional briefing 30 min before event

The interview is the last step to become a ReDI students, after completing a prework and submitting an official application. We interview in order to:

  • Get to know the students

  • Ensure their time availability

  • Check their understanding of course content

  • Understand their motivation to join

We interview every candidate who is not a returning students who passed with achievement in the past semester. *For Circles & Bootcamps we will interview both new & returning students.

We recommend the candidate a course if motivation, understanding of the content and time commitment fit. Based on your decision, we recommend your course, a lower or more advanced one.

Interview Preparation

  • You will receive the information on this page, as well as the interview form for your course along with your calendar invite for the interviews. Please accept or decline the invitation by February 19th to confirm your attendance so we can plan accordingly.

  • A non mandatory 30-minute briefing will also be held on interview day to review the process and address any questions before we start.

On Interview day

  1. Join the Zoom call from your calendar invite.

  2. The ReDI Team will welcome you and assign you to a breakout room.

  3. A max of 6 students will be sent to you one at a time for 1:1 interviews (20 minutes total):

    • 15 minutes conversation

    • 5 minutes for notes and recommendation

  4. A dedicated Slack channel will be set up for real-time communication throughout the interviews and breakout sessions. Once you complete an interview, notify the team on Slack, and the next student will be sent your way.

Teachers Training

⏰ March 3rd-12th, non mandatory We'll offer trainings to our wonderful volunteer teachers to make sure they feel confident sharing their knowledge in the classroom. Training plan and additional information will be presented during onboarding & planning meetings.

Kick Off Preparation

⏰ Courses kick off on March 17th or 18th

During our teachers / students kick-off day, you welcome the students to the class. The session is facilitated by each teaching team as a collaborative effort. You find the materials for the kick off session in your course sheet. You need to sign up for a role by adding your name to the meeting agenda. You prepare for the event by finalising the materials needed for your role. The main goals of the meetings are:

  • Getting to know each other, create a welcoming class atmosphere

  • Introducing the teaching team to the students

  • Presenting the course & class tools

Teaching Phase

Mid-Semester Students Feedback Session - ReDI Led

⏰ May 5th - 7th, 1 session per class, 2 hours Exact date available in your course sheet LINK

The ReDI team will meet with the students to collect feedback on the course as well as suggestions from the students. The session is moderate entirely by the ReDI team and results are brought to the teaching team at the teachers touch point one week later.

Teachers Touch Points

⏰ May 12th - 14th, 1 session per team, 2 hours Exact date available in your course sheet LINK We meet at mid semester with the teaching team to:

  • hear feedback from the students and ideate solutions,

  • celebrate our achievements and

  • plan the rest of the semester.

Teachers touch points happen while students are attending ReDI's career week.

Career Week

The Career Week at ReDI School is a week of training webinars designed to help students connect with industry professionals, improve job-related skills, explore career opportunities and boost their job readiness. More LINK CAREER SERVICES ✅ Students need to attend 2 career events during the semester (within or outside the career week) in order to graduate. Students choose topics most interesting to them. ✅ Other career events during the semester might include: company visits, networking opportunities, mentoring matching events.

During career week, classes are on hold. We use this time to organize teaching team touch points.

Project Phase

⏰ Last 2 or 3 weeks of classes are dedicated to project Exact dates available in your course sheet LINK The Project Phase at ReDI School is the part of the course where learners apply what they've learned by working on a real-world projects. It is also a way to boost students confidence and improve job readiness. It usually happens towards the end of the program and is designed to help building practical experience and a strong portfolio. For learners, this is a chance to foster:

🔹 Team Collaboration – Work in teams with other students, just like in a real job. 🔹 Hands-on Learning – Apply coding, design, or data skills to solve real problems. 🔹 Mentor Support – Get guidance from teachers on real case scenarios. 🔹 Final Presentation – Showcase their project to classmates, mentors, and sometimes even company representatives.

Community Events

Local Community Events at ReDI School are gatherings where students, alumni, mentors, and industry professionals come together to network informally and share some quality time. These events help you connect with the tech community in your city (Berlin, Hamburg, or NRW). We'll organize 2 community events per each location this semester.

Let's go to the next section and dive into the tools:

Essential Tools

Kick-Off

🚧 Under Construction 🚧

HTML / CSS

Get Started

Most important Resources

Course Material


Teaching Roles Overview

Weekly Class Schedule

About ReDI

Help

  • Reach out to Sevval, your Course Manager, for help via Slack.

❤️ Thank you for supporting the ReDI students ❤️

Are you new to this course:

Start your Onboarding:

Tools
Description
How to use it
Material
Description
How to use it
Role
Topic
Session
When
Purpose

Find out more about ReDI:

Find out about the career services ReDI offers:

Check out: , , .

Course Overview
Get Started
About ReDI
Career Services
I can't teach tonight
I am dropping out
I feel uncomfortable

Course management

Course Sheet

Share material & project review

Google Classroom

Zoom link for the sessions

Zoom

Track student attendance

Attendance Tracker

slides and teaching files

Course Content

Leads regular classes, introduces new concepts

Manages Zoom logistics and supports students during classes

Provides emergency coverage when regular teachers are unavailable

Tuesday 19:00-21:00

Thursday 19:00-21:00

New concepts introduced with theory and practice

Course Sheet
Google Classroom
Zoom Link
Attendance Tracker
Google Drive
Session Owner
Session Assistant
Backup Teacher
Regular Class

Essential Tools

Here's an overview of the key tools we use for teaching and communication. Please set up these tools now to ensure effective collaboration with your team and students.

Slack

This is our main communication tool, both with teachers and with the students. You'll have access by default to your teaching team channel and the students' channel. Additionally, you can join our community channels in Berlin, NRW, and Hamburg to learn about local events. Please check Slack regularly during the semester and communicate with your teaching team via Slack if you cannot make it to class.

Action


Google Calendar

We use Google Calendar to send semester meeting appointments to teachers and students.

Actions


Zoom

Our online sessions are running on Zoom. We highly recommend installing and updating the Zoom app on your device, as the online version doesn't cover all functionalities. Please note: The class Zoom link is the same for the entire semester.

Actions


Google Classroom

We use Google Classroom to share material with the students and to collect and give feedback to projects and homework.

Actions


Open the Email with the Slack invitation from ReDI. .

to your Laptop (and or mobile phone).

Watch the "" video

Done?

Please complete all steps before going to the next section of the self-onboarding. If you face any issues, please reach out to the ReDI team via E-Mail or Slack. Once you are done, let's dive into the .

Enter ReDI Slack
Download Slack
how to use Google Classroom
✅
Content Introduction

Teacher Touchpoints

The Teacher Touchpoint is a mid-semester session designed to bring the teaching team together in a collaborative and reflective space.

Feedback session about the semester During this session, we’ll review student feedback and take a moment to reflect on your teaching experience so far. It's also a valuable space to share your thoughts on your volunteering journey — including suggestions to improve the content, enhance classroom dynamics, strengthen team collaboration, or identify ways the ReDI Team can better support you, whether this semester or in the future. It’s a great opportunity to celebrate what’s working well, exchange ideas, and contribute to creating an even better learning experience for everyone involved.

Presentations for Demo Day We’ll also discuss the format of the final presentations for Demo Day. In some courses, if needed, we will also define the expected topics or key concepts that should be reflected in the final project outcomes.

Availability for the second half of the semester Additionally, we’ll check availability for the second half of the semester and assign roles for the upcoming sessions.

Get Started

Welcome to the HTML / CSS Course! 👋

Welcome to our teaching team! We're excited to have you join us in supporting ReDI students on their journey in tech. The HTML / CSS course is an 14-week journey where students build realistic projects while learning modern web development skills.

As a teacher, your first step is to complete the self-onboarding process:

This hub contains everything you need to start and support your teaching journey. If you have any questions along the way, don't hesitate to contact our team on Slack.

Explore the to learn more about the course

Check out the

Review and get onboarded in the

Complete your onboarding in

Ready to begin? Head over to the section!

Course Overview
Timeline
Essential Tools
Complete your self-onboarding
Course Overview

Course Overview

Welcome to ReDI School! We really appreciate that you are part of our community. In this page, you'll find an overview of the course. By volunteering, you contribute to our main goal: help our students gain the necessary skills to find a job in tech. ReDI School has now helped over 17.000 people advance their tech skills. This is only possible with the support of our volunteers <3

ReDI Students

Our student community brings together people from over 138 countries. Your course won't be different. Your students will come from a wide range of countries. They also come from diverse professional backgrounds - some are currently unemployed or underemployed, while others are students looking to prepare for their careers. With an average age of 32, many of our students hold a university degree and have several years of work experience. What unites all students is their passion for technology and their aim to build a career in the tech industry.

Sessions

Roles

On-site Activities

Two sessions during the course will take place on a hybrid format - students in Hamburg will have a session on site, while the other students a parallel session online. We are organizing on-site activities in our three main locations. Find out more below.

We invite you to four on-site community events throughout the semester if you are located in Berlin and the surrounding. The Onboarding will also take place in person in Berlin. You are more than welcome to join!

We invite you to four on-site community events throughout the semester if you are located in Berlin and surrounding. The Onboarding and Demo Day will also take place in person in Düsseldorf. You are more than welcome to join!

Four in-person sessions are taking place in Hamburg: Onboarding, two regular course sessions, and Demo Day. If you are based in Hamburg, it would be fantastic if you could support the course in one or more of these sessions.

Conclusion

❤️ Thank you for supporting our students as they take another step in their journey! To learn more about ReDI students and our community, visit .

We hope that by reading this, you have a better idea of the course and what it means to volunteer at ReDI. Let's explore the now 📅.

About ReDI School
Weekly Sessions
Teaching Team
Timeline

Complete your Self-Onboarding

Thank you very much for going through your Self-Onboarding! This ensures a smooth onboarding into your volunteer experience. Please complete the following typeform to finish the self-onboarding. If you face any problems, you can indicate them in the typeform.

That's it! Thanks for completing your self-onboarding. Feel free to browse around the teacher hub. See you soon!

Complete your Self-Onboarding

Thank you very much for going through your Self-Onboarding! This ensures a smooth onboarding into your volunteer experience. Please complete the following typeform to finish the self-onboarding. If you face any problems, you can indicate them in the typeform.

That's it! Thanks for completing your self-onboarding. Feel free to browse around the teacher hub. See you soon!

Done

Done

🙌
🙌

Tools & Platforms

Course Overview
Zoom
Attendance Tracker
Google Classroom

Course Sheet

Course Sheet

  • Link: The link to your Course Sheet is pinned in Slack.

  • Course Management: We use the Course Sheet to organize the course.

  • Availability & Ownership: Volunteers assign themselves to the session. They show when they are available to teach.

  • Feedback: The coursesheet has a feedback tab where we collect feedback about the session.

Not available anymore?

  • Mark it in the Course Sheet so that others can see it!

Zoom

Zoom

  • Zoom? It is our video conferencing tool for the classes.

  • Zoom Link: You find it pinned in Slack. The Zoom link is the same for the whole semester.

  • Recordings: We record the session. More: Recordings

  • Claim Host: Credentials are pinned in Slack. How to Join Zoom & Claim Host

  • Join early? The Zoom call opens 45 min ahead of time. Feel free to join early.


How to Join Zoom & Claim Host

  1. Find the link to the class meeting either in your calendar invite for the session or pinned in the teachers slack channel. Join with one click

  2. Go to the participants list and “Claim host”. Sign in with the host key to become the host. You can find the host key (a series of 6 numbers) pinned in the teacher Slack channel.

  1. Please make your co-teachers for the sessions co-hosts by right-clicking on their name from the participants list.

  2. Please do not forget to record the class. We record only Input and Q&A Sessions.

Recordings

Recordings automatically save into a drive students have access to as viewers. This Drive is pinned to the students slack channel. Recordings are available for whole semester. Break out rooms cannot be recorded.

Default Zoom Settings

  • When starting the meeting, audio is off, your video is off and recording is off.

  • Hosts are allowed to add co-hosts.

  • Possibility to send files via meeting chat.

Use the App: Install the for all functionality.

Breakout rooms enabled. How to setup breakout rooms: , .

Zoom app
Video
Guide

Student Interviews

The student interview is the final step in the application process to become a ReDI student.

Student Admission Process:

  1. Prework

  2. Application

  3. Interview

  4. Acceptance

As part of your volunteer teacher experience, we invite you to support this process by helping us interview prospective students.

Why do we conduct interviews?

The goal of the interview is to:

  • Get to know the applicants personally

  • Ensure they have enough time to commit to the course

  • Check their understanding of the course content

  • Understand their motivation to join ReDI

Why should you, as a teacher, take part?

  • You help select students who are genuinely motivated and aligned with the course goals

  • Your involvement increases the likelihood of having committed and engaged students, which leads to a more dynamic and rewarding class experience

  • You gain early insight into your students' backgrounds, goals, and needs

  • You support ReDI’s mission to provide equal access to tech education by helping ensure a fair and thoughtful selection process

Our goal

We aim to ensure the best match between the students’ skills and motivation and the course level. Based on your evaluation, we may recommend:

  • The course you’re teaching

  • A more basic or more advanced course

  • A different track if it suits the student better

Tone and values

These interviews are not exams and not professional job interviews. They are informal conversations designed to get to know the students better. We aim for a relaxed and welcoming environment while keeping a professional tone.

The interviews should reflect ReDI’s values of inclusivity, collaboration, and empowerment. Keep the conversation natural and friendly to help applicants feel comfortable and open to sharing.

Ask about their motivation and previous experience in a way that shows empathy and genuine interest. This first contact sets the tone for their ReDI experience — let’s make it a positive one.

Support from ReDI

You won’t be doing this alone. ReDI will provide:

  • A guideline for the interview process

  • A set of questions you can use as a structure

  • Support in case you have doubts or special situations

We want to make the process smooth and meaningful for both you and the students.

Teacher Trainings

Here you’ll find materials generously shared by our trainers, who have offered their time pro bono to support the ReDI volunteer community. These resources have been thoughtfully designed and adapted to support you in your role as a teacher. We hope you find them helpful. If you're interested in exploring specific topics or would like to connect with a trainer for future semesters, feel free to reach out to us at dcp-volunteering@redi-school.org.

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

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

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

Attendance Tracker

Attendance Tracker

  • Who: The teaching assistant tracks attendance

  • When: Every regular class (usually 20 minutes into the session)

  • Access: Credentials are pinned in your teaching teams' Slack channel


Why track attendance?

We ask learners to join at least 80% of the sessions to obtain a certificate. We believe students can only learn if they attend. That's why attendance tracking is essential. ReDI follows up regularly with students with low attendance to offer support.

Attendance Status per Session

100% – Present: Arrive on time, actively participate, and keep the camera on.

50% – Excused: Notify in advance if unable to attend

50% – Late: Arrival more than 15 minutes late. Please mark as "Excused". If no excuse is known, select "Other." No explanation from students is required.

50% – Early Leave: Leaving before the break. Please mark as "Excused". If no excuse is known, select "Other." No explanation from students is required.

0% – Absent: No prior communication of absence

Camera on Policy

Students will only be marked as "present", if they join the class with their camera on.

If a student should experience internet connection problems during the class, they should either write it in the chat or unmute themselves to inform teachers and fellow students. If this is not possible, students should inform the class through a message in their students slack channel.


How to track Attendance?

Final Project

🌟 Final Project Phase – Spring 2025

The Final Project is the highlight of the semester and an essential part of the learning journey at ReDI. During this phase, learners apply the skills they’ve developed to create a personal or team project that showcases their knowledge in HTML & CSS.

🚀 About the Project Phase

The project phase begins after the core curriculum is completed.

Learners will:

  • Work individually or in small groups (up to 3 people)

  • Choose their own project topic with teacher guidance

  • Build a working website or feature relevant to the course

💡 Goal: Apply the concepts learned in class in a hands-on, creative project

🧑‍💻 Project Requirements

Each project must include:

  • A code-based solution using HTML & CSS

  • A presentation and a live demo (showing a working website)

Students choose their own project topic with teacher guidance. Project types may include:

  • A personal website

  • A thematic landing page

  • A community-focused mini project

  • Anything aligned with the course content and realistic for the timeframe

📅 Timeline (Spring 2025)

📌 Attendance and presentation in the Class Demo Day are required for students to receive a certificate.

🗣️ Presentation Guidelines

To help learners prepare their pitch, here’s a suggested format:

  • Length: Max. 5 minutes

  • Mode: Slides or Live Demonstration

  • Proposed Structure:

    1. Intro – What’s the project, and what problem does it solve?

    2. Demo – Show the live website

    3. Challenges & Learning – What went well? What was hard? What did you learn?

🧑‍🏫 Encourage learners to rehearse and help each other practice!

🧾 Certification Requirements

To receive a ReDI certificate, learners must:

  • Attend at least 80% of the course

  • Participate in 2 Career Workshops

  • Complete and present a Final Project

  • Attend the Internal Demo Day

  • Complete 2 IBM SkillsBuild Courses

🤝 Class Culture & Support

💬 “We grow by doing, and by helping each other.”

  • Encourage a supportive, collaborative learning environment.

  • Foster confidence through feedback.

  • Use class time for project work, check-ins, and guidance.

Project Phase Guidelines

Project Session Tips


Link:

Final Project Ideas

Milestone
Date

Let’s celebrate the end of the semester together

Attendance Tracker

Project Launch

Thursday, May 22

We introduce students to the project phase

Class Demo Day

Tuesday, June 17

All learners present to their class. One project will be selected for the official Demo Day.

Demo Day

Date to be confirmed.

Selected projects from each course are showcased to the full ReDI community. We aim to run an on-site Demo Day in each location.

💡
🎉
Prior Projects

Class Engagement

We provide additional tools that you can use to engage students more in your sessions! At ReDI, we like to use the following tools and icebreakers:

Mentimeter (Interactive Polls)

  • Create live polls, word clouds, and Q&A

  • Perfect for:

    • Icebreakers: Ask students about their expectations or background knowledge.

    • Quick polls: Check understanding of a topic in real-time.

    • Exit tickets: Gather feedback at the end of a session.

  • Login credentials in teachers' Slack channel

Kahoot (Learning Games)

  • Quiz-based learning with competitive elements

  • Perfect for Revision & Recaps - You create a quiz, and students participate live in class via browser or cell phone.

  • Login credentials in teachers' Slack channel

Icebreaker Ideas

You can use quick icebreakers at the start of your sessions to energize participants, build connections, and create an engaging and interactive learning environment. Here is a list of icebreakers. They shouldn't take more than 5 minutes to run.

1. Two Truths and a Lie

  • Description: Participants share three statements about themselves—two true and one false. The group has to guess which one is the lie.

  • How to Run: Use breakout rooms for smaller groups or let everyone participate in the main room.

  • Objective: Participants get to know each other in a fun way.

2. Virtual Scavenger Hunt

  • Description: Give participants a list of items to find in their home within 1-2 minutes (e.g., something red, something that makes noise).

  • How to Run: Ask them to bring the items back to the camera and share a quick story about one of them.

  • Objective: The activity is an energizer.

3. Emoji Reactions

  • Description: Pose a question or statement (e.g., "How are you feeling about today’s session?") and ask participants to respond using emojis only.

  • How to Run: Use the chat in Zoom.

  • Objective: It is an easy way for participants to share how they are doing.

More Resources

Mentimeter.com
Kahoot.com
13 online icebreakers
Ice breakers using slido
Ice breakers in Kahoot
Ice breakers in Menti
Attendance Tracking App Demo
Attendance Tracking Steps Visualised
Slide Deck

Teaching Team

Demo Day

🚧 Under Construction 🚧

Essential Tools

Here's an overview of the key tools we use for teaching and communication. Please set up these tools now to ensure effective collaboration with your team and students.

Slack

This is our main communication tool, both with teachers and with the students. You'll have access by default to your teaching team channel and the students' channel. Additionally, you can join our community channels in Berlin, NRW, and Hamburg to learn about local events. Please check Slack regularly during the semester and communicate with your teaching team via Slack if you cannot make it to class.

Action


Google Calendar

We use Google Calendar to send semester meeting appointments to teachers and students.

Actions


Zoom

Our online sessions are running on Zoom. We highly recommend installing and updating the Zoom app on your device, as the online version doesn't cover all functionalities. Please note: The class Zoom link is the same for the entire semester.

Actions


Google Classroom

We use Google Classroom to share material with the students and to collect and give feedback to projects and homework.

Actions


Open the Email with the Slack invitation from ReDI. .

to your Laptop (and or mobile phone).

Watch the "" video

Done?

Please complete all steps before going to the next section of the self-onboarding. If you face any issues, please reach out to the ReDI team via E-Mail or Slack. Once you are done, let's dive into the .

Enter ReDI Slack
Download Slack
how to use Google Classroom
✅
Content Introduction

Regular Class

Purpose

Weekly class where students learn new concepts and get introduced to their next project milestone.

Session Details

  • When: Thursdays, 19:00 - 21:00

  • Where: Zoom (link in Slack)

  • Team: Session Owner leads the session and Session Assist supports

Class Structure

  1. Review previous content

  2. Introduce weekly milestone

  3. Present new concepts

  4. Guided practice ("We Do")

  5. Group practice in breakout rooms ("You Do")

More Resources

  • Course Content

  • Session Owner

  • Session Assist

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

Course Content

Key Resources

  • Prior Material? If you taught in the past semester at ReDI, you might have existing material you would like to reuse. That is fantastic! Add it to our Google Drive.

Homework?

How do I create more engagement in class?

Best practices for teaching?

Material
Description
How to use it

slides and teaching files

Looking for more material? Maybe check out from the Berlin HTML & CSS Course.

GitHub Repo
Homework
Class Engagement
Teaching Guidelines
Course Content
Google Drive

Final Project

🌟 Final Project Phase – Spring 2025

The Final Project is the highlight of the semester and an essential part of the learning journey at ReDI. During this phase, learners apply the skills they’ve developed to create a personal or team project that showcases their knowledge in JavaScript.

🚀 About the Project Phase

The project phase begins after the core curriculum is completed.

Learners will:

  • Work individually or in small groups (up to 3 people)

  • Choose their own project topic with teacher guidance

  • Build a working web app or website

💡 Goal: Apply the concepts learned in class in a hands-on, creative project

🧑‍💻 Project Requirements

Each project must include:

  • A code-based solution using JavaScript

  • A presentation and a live demo (showing a working web app or website with interactivity)

Students choose their own project topic with teacher guidance. Project types may include:

  • A quiz or trivia game

  • A to-do list or productivity tool

  • An interactive landing page or form

  • A weather or news app using APIs

  • Anything aligned with the course content and realistic for the timeframe


📂 Prior Projects

Need inspiration? Check out these projects from previous semesters:

📅 Timeline (Spring 2025)

Milestone
Date

Project Launch

Tuesday, June 3

We introduce students to the project phase

Class Demo Day

Tuesday, June 17

All learners present to their class. One project will be selected for the official Demo Day.

Demo Day

Date to be confirmed.

Selected projects from each course are showcased to the full ReDI community. We aim to run an on-site Demo Day in each location.

📌 Attendance and presentation in the Class Demo Day are required for students to receive a certificate.

🗣️ Presentation Guidelines

To help learners prepare their pitch, here’s a suggested format:

  • Length: Max. 5 minutes

  • Mode: Slides or Live Demonstration

  • Proposed Structure:

    1. Intro – What’s the project, and what problem does it solve?

    2. Demo – Show the live website

    3. Challenges & Learning – What went well? What was hard? What did you learn?

🧑‍🏫 Encourage learners to rehearse and help each other practice!

🧾 Certification Requirements

To receive a ReDI certificate, learners must:

  • Attend at least 80% of the course

  • Participate in 2 Career Workshops

  • Complete and present a Final Project

  • Attend the Internal Demo Day

  • Complete 2 IBM SkillsBuild Courses

🤝 Class Culture & Support

💬 “We grow by doing, and by helping each other.”

  • Encourage a supportive, collaborative learning environment.

  • Foster confidence through feedback.

  • Use class time for project work, check-ins, and guidance.

Project Phase Guidelines

Project Session Tips


Final Project Ideas

Let’s celebrate the end of the semester together

💡
🎉
Demo Day Highlights – Previous Cohort

Google Classroom

Google Classroom

  • Link: The link to your classroom is pinned in Slack.

  • Purpose: We use Google Classroom as our learning platform. We use it for two functions: Sharing material with the students and reviewing projects. You can also use it to create material.

  • Google Drive: Your Google Classroom is connected to a Google Drive where material is stored.

  • Calendar: Students are invited to the sessions through the calendar from the classroom

How to Upload Materials on Google Classroom

Go to Classwork. Go to Create. Select material to upload material, which is shared with the students. Select Topic to create a new section that can hold multiple materials.

Draft function: drafts are only visible to teachers - not to the students (yet). You can already work on material before sharing it with students. In order to share it, you publish the material.

Review Projects

  • Go to the Grades section. You find all the students; you can see who turned in the homework. Once you click on it, you can review their work, write a comment, and return it.

Are you not in Google Classroom?

You should have received an email invitation from ReDI. Please check your emails and spam folder. Otherwise, please get in touch with the ReDI team via Slack.

Weekly Sessions

Slides

Get Started

Welcome to the Full Stack Bootcamp! 👋

Welcome to our teaching team! We're excited to have you join us in supporting ReDI students on their journey in tech. The Full Stack Bootcamp is an 18-week journey where students build realistic projects while learning modern web development skills.

As a teacher, your first step is to complete the self-onboarding process:

  1. Explore the Course Overview to learn more about the course

  2. Check out the Timeline

  3. Review and get onboarded in the Essential Tools

  4. Check out the Content Introduction

  5. Complete your onboarding in Complete your Self-Onboarding

This hub contains everything you need to start and support your teaching journey. If you have any questions along the way, don't hesitate to contact our team on Slack.

Ready to begin? Head over to the Course Overview section!

Course Overview

Welcome to ReDI School! We really appreciate that you are part of our community. In this page, you'll find an overview of the course. By volunteering, you contribute to our main goal: help our students gain the necessary skills to find a job in tech. ReDI School has now helped over 17.000 people advance their tech skills. This is only possible with the support of our volunteers <3

ReDI Students

Our student community brings together people from over 138 countries. Your course won't be different. Your students will come from a wide range of countries. They also come from diverse professional backgrounds - some are currently unemployed or underemployed, while others are students looking to prepare for their careers. With an average age of 32, many of our students hold a university degree and have several years of work experience. What unites all students is their passion for technology and their aim to build a career in the tech industry.

❤️ Thank you for supporting our students as they take another step in their journey! To learn more about ReDI students and our community, visit About ReDI School.

Curriculum

The Full Stack Bootcamp is an 18-week intensive program that combines 14 weeks of technical training with a 4-week career project. Each cohort consists of 25 students who progress through the program together, meeting three times per week in the evenings (Monday, Wednesday, and Thursday from 19:00-21:00). The program follows a project-based learning approach where students work through three main projects: an E-Commerce Store focusing on React basics, a Twitter Clone exploring Next.js, and a Capstone Project incorporating full stack development. Each project spans four weeks and includes weekly milestones and a recap week for review.

Structure

The weekly schedule includes three distinct session types: Monday's Practice Session for exercises and Q&A, Wednesday's Coaching Session where students present their progress in small groups, and Thursday's Regular Class introducing new concepts. The teaching team consists of various roles including Session Owners who lead regular classes, Coaches who guide small groups, and Practice Session Owners who run exercise sessions. Volunteers typically commit to one role for the entire semester, investing 3-4 hours per week in direct teaching plus preparation time.

While the program is primarily conducted online via Zoom, it maintains a hybrid format with four on-site community events throughout the semester. The bootcamp is available in three locations (Berlin, NRW, and Hamburg), with local events specific to each city. Students are expected to dedicate approximately 14 hours per week to self-study in addition to attending the scheduled sessions.

Sessions

Day
Session
Description
Roles

Monday 19:00 - 21:00

This is a practice and Q&A session. Students can ask questions about the newly learned concepts and get support when they are stuck on the project. Furthermore, we have run exercises to practice the content.

Session Owner, Session Assist

Wednesday 19:00 - 21:00

Learners present their solutions to the weekly milestones in small groups (breakout rooms). Coaches give feedback and help the students advance.

4-5 Coaches

Thursday 19:00 - 21:00

This regular class is taught in pairs, with one person assigned as a session owner (the lecturer) and one as a teaching assistant. The class introduces the students to the new topic of the week through theory and practice.

Session Owner, Session Assist

Roles

Role
Topic
Time Invest

A coach supports 4-5 students in weekly coaching sessions, providing feedback on project milestones and helping students progress. During these 2-hour sessions, students present their work and receive personalized guidance in small groups.

4 hours per week

A session owner leads the weekly regular class, introducing new concepts and guiding students through exercises using prepared materials. They have the flexibility to adapt the teaching materials to their style while ensuring all key concepts are covered.

4 hours per week

A session assistant manages the technical aspects of online classes, including Zoom setup, attendance tracking, and breakout room management. They also support students during exercises and help answer questions in the chat.

3 hours per week

A backup teacher stands ready to cover any role if a scheduled teacher is unable to attend. They don't need to attend sessions unless called upon, but should be familiar with the course content and different teaching roles.

2 hours per week

A practice session owner leads weekly sessions focused on practicing concepts from the previous class through hands-on exercises. They guide students through practice activities and answer questions about both concepts and project milestones.

4 hours per week

On-site Activities

We are organizing on-site activities in our three main locations. Find out more below.

We invite you to four on-site community events throughout the semester if you are located in Berlin and the surrounding. The Onboarding will also take place in person in Berlin. You are more than welcome to join!

We invite you to four on-site community events throughout the semester if you are located in Berlin and surrounding. The Onboarding and Demo Day will also take place in person in Düsseldorf. You are more than welcome to join!

Four in-person sessions are taking place in Hamburg: Onboarding, two regular course sessions, and Demo Day. If you are based in Hamburg, it would be fantastic if you could support the course in one or more of these sessions.

Conclusion

Timeline

Preparation Phase

Teachers Onboarding & Planning Sessions

⏰ Feb 12th - 20th, 2 meetings per course

A ReDI volunteer journey starts with a welcome to the ReDI community! During teachers onboarding & planning sessions, we:

  • Welcome new & returning volunteer teachers to the community

  • Share semester mission, goals & timeline

  • Plan / review the outline of the coursw

  • Align on teaching roles & processes

  • Prepare for students selection process and course kick off

Students Screening / Interviews

⏰ Feb 24th - 28th, 1 session, 2 hours, optional briefing 30 min before event

The interview is the last step to become a ReDI students, after completing a prework and submitting an official application. We interview in order to:

  • Get to know the students

  • Ensure their time availability

  • Check their understanding of course content

  • Understand their motivation to join

We interview every candidate who is not a returning students who passed with achievement in the past semester. *For Circles & Bootcamps we will interview both new & returning students.

We recommend the candidate a course if motivation, understanding of the content and time commitment fit. Based on your decision, we recommend your course, a lower or more advanced one.

Interview Preparation

  • You will receive the information on this page, as well as the interview form for your course along with your calendar invite for the interviews. Please accept or decline the invitation by February 19th to confirm your attendance so we can plan accordingly.

  • A non mandatory 30-minute briefing will also be held on interview day to review the process and address any questions before we start.

On Interview day

  1. Join the Zoom call from your calendar invite.

  2. The ReDI Team will welcome you and assign you to a breakout room.

  3. A max of 6 students will be sent to you one at a time for 1:1 interviews (20 minutes total):

    • 15 minutes conversation

    • 5 minutes for notes and recommendation

  4. A dedicated Slack channel will be set up for real-time communication throughout the interviews and breakout sessions. Once you complete an interview, notify the team on Slack, and the next student will be sent your way.

Teachers Training

⏰ March 3rd-12th, non mandatory We'll offer trainings to our wonderful volunteer teachers to make sure they feel confident sharing their knowledge in the classroom. Training plan and additional information will be presented during onboarding & planning meetings.

Kick Off Preparation

⏰ Courses kick off on March 17th, 2 hours

During our teachers / students kick-off day, you welcome the students to the class. The session is facilitated by each teaching team as a collaborative effort. You find the materials for the kick off session in your course sheet. You need to sign up for a role by adding your name to the meeting agenda. You prepare for the event by finalising the materials needed for your role. The main goals of the meetings are:

  • Getting to know each other, create a welcoming class atmosphere

  • Introducing the teaching team to the students

  • Presenting the course & class tools

Teaching Phase

Project Cycles / Feedback / Touch Points

At the end of each project, we send out a survey to the students and collect their feedback. This is then shared with you in our teachers touch points. Aim aim of the touch points are to:

  • hear feedback from the students and ideate solutions

  • celebrate our achievements and

  • plan the rest of the semester

Community Events

Local Community Events at ReDI School are gatherings where students, alumni, mentors, and industry professionals come together to network informally and share some quality time. These events help you connect with the tech community in your city (Berlin, Hamburg, or NRW). We'll organize 2 community events per each location this semester.

Career Project

We are currently adapting the format of the final career project. More information will follow soon on this aspect!

We hope that by reading this, you have a better idea of the course and what it means to volunteer at ReDI. Let's explore the Timelinenow .

Let's go to the next section and dive into the tools: .

📅
Coach
Session Owner
Session Assist
Backup Teacher
Practice Session Owner
Essential Tools
Practice Session with Q&A
Coaching Session
Input Session

Javascript

Get Started

Most important Resources

Tools
Description
How to use it

course management

share material & project review

Zoom link for the sessions

Track student attendance

Course Material

Material
Description
How to use it

projects

slides and teaching files

knowledge base for students


Teaching Roles Overview

Role
Topic

Leads regular classes, introduces new concepts and practices it with the students. Creates the homework.

Manages Zoom logistics and supports students during classes

Provides emergency coverage when regular teachers are unavailable

Weekly Class Schedule

Session
When
Purpose

Tuesday 19:00-21:00

New concepts introduced with theory and practice

Thursday 19:00-21:00

New concepts introduced with theory and practice

About ReDI

Help

  • Reach out to Abdullah, your Course Manager, for help via Slack.

❤️ Thank you for supporting the ReDI students ❤️

Full Stack Bootcamp

Get Started

Most important Resources

Course Material

Teaching Roles Overview

Weekly Class Schedule

About ReDI

Help

  • Reach out to Sevval, your Course Manager, for help via Slack.

❤️ Thank you for supporting the ReDI students ❤️

Get Started

Welcome to the JavaScript Course! 👋

Welcome to our teaching team! We're excited to have you join us in supporting ReDI students on their journey in tech. The JavaScript course is an 14-week journey where students build realistic projects while learning modern web development skills.

As a teacher, your first step is to complete the self-onboarding process:

This hub contains everything you need to start and support your teaching journey. If you have any questions along the way, don't hesitate to contact our team on Slack.

Are you new to this course:

Start your Onboarding:

Find out more about ReDI:

Find out about the career services ReDI offers:

Check out: , , .

New to this course:

Start your Onboarding:

Tools
Description
How to use it
Session
When

Find out more about ReDI:

Find out about the career services ReDI offers:

Check out: , , .

Explore the to learn more about the course

Check out the

Review and get onboarded in the

Check out the

Complete your onboarding in

Ready to begin? Head over to the section!

Course Overview
Get Started
About ReDI
Career Services
I can't teach tonight
I am dropping out
I feel uncomfortable

Practice Session with Q&A

Monday 19:00-21:00

Coaching Session

Wednesday 19:00-21:00

Regular Class

Thursday 19:00-21:00

Course Sheet
Google Classroom
Zoom
Attendance Tracker
Course Content
Course Content
Course Content
Course Overview

Teaching Guidelines

Teaching Method: I Do, We Do, You Do

The "I Do, We Do, You Do" method is a teaching method designed to help students learn new concepts by first observing, then practicing with guidance, and finally working independently.

  • I Do: The teacher demonstrates the task while explaining the steps and thought process aloud. This stage is about modeling the correct way to approach the task and highlighting key concepts and techniques.

  • We Do: The session owner walks the students through an activity. The students follow along (code or design along). This collaborative stage allows students to apply what they've seen with support, ask questions, and receive immediate feedback.

  • You Do: Students work independently on the task. This stage allows them to practice the skill on their own.

Example: Introducing Javascript

  • I Do: The teacher introduces JavaScript and demonstrates a simple script that shows an alert when clicking a button. Key concepts like variables, functions, and events are explained briefly.

  • We Do: The teacher walks the students through creating a function that changes a heading's color when clicking a button. The students follow and code along. The teacher shares their screen and gives the students time to code along. Together, the teacher and the students write the function, select the element, and add an event listener, with the teacher guiding and asking questions to engage students.

  • You Do: Students independently write JavaScript to change the text of a paragraph when a button is clicked in a breakout room. They practice using variables, functions, and event listeners and then share their work for feedback.

Tips and Tricks

  • Context before content - We experienced that explaining why a concept is important helps a lot in understanding what the concept is about. Why should you learn this concept? Try to give the context. Maybe explain where you use it in your daily work life. Or explain how this concept can help to solve a bigger problem

  • Engage with Students: Ask questions to check understanding. Use their names and keep the tone friendly and encouraging.

  • Be Prepared but Flexible: Have a plan but adapt based on student needs.

  • Feedback is Key: Provide constructive feedback to help students improve. Celebrate small wins to keep motivation high.

More Resources

  • Ice Breakers and Energizers - Do you want to start the session with an energizer? Have a look at Class Engagement

Course Sheet
Google Classroom
Zoom Link
Attendance Tracker
GitHub
Google Drive
Session Owner
Session Assistant
Backup Teacher
Regular Class
Regular Class
Get Started
Course Content
Teaching Team
About ReDI
Career Services
I can't teach tonight
I am dropping out
I feel uncomfortable
Course Overview
Timeline
Essential Tools
Content Introduction
Complete your self-onboarding
Course Overview

course management

Course Sheet

share material & project review

Google Classroom

Zoom link for the sessions

Zoom

Track student attendance

Attendance Tracker

Homework

Overview

  • Homework is given every Thursday session via Google Classroom

  • The Session Owner of the Thursday session prepares the homework

  • Students have until the following Tuesday session to complete the homework

  • The Homework Reviewer reviews their homework from Tuesday until Thursday

  • Homework is not graded. The goal is for students to learn by working on their homework. If it is not complete or perfect, it’s okay. We ask students to complete at least 80% of the homework.

Why homework?

  • Learning by Doing - Through homework, students practice and code more. The more they practice, the better the students get!

  • Students try out the concepts in homework. The review helps students to know if they are on track.

  • By reviewing the homework, we might better understand which concepts need further elaboration.

Homework Process

1. Create Homework

Session Owner creates homework.

2. Add to Google Classroom

3. Present Homework in Class

Session Owner presents the homework assignment on Thursday

4. Students hand in homework

Students hand in the homework until the start of the next session (Tuesday)

5. Show solution

Session Owner shows the solution of the homework in the Tuesday session

6. Teachers review homework

Homework Reviewer reviews submissions until Thursday

How much homework?

Focus the homework on one achievable, practical problem. That means:

  • Give only one problem, not multiple, it would overwhelm and lower chances of completion.

  • Achievable - make it equally hard or slightly harder than the last practice exercise in class. Make it feasible in terms of the time required. If you need 5 minutes to solve it, it will probably take the students 30 minutes or longer. Don’t go over 5min for yourself.

  • Optional - to accommodate the more advanced students in the class, you can add optional extra questions.

How to add Homework to Google Classroom?

Homework Guidelines

Session Owner creates a homework assignment in Google Classroom at least 1 day before class. .

Go to , Go to Create, and select Assignment.

Give title, instructions and set the due date to the next session on Tuesday ().

Support: .

Course Sheet
Google Classroom
Zoom Link
Attendance Tracker
Google Classroom
template
Video for Google Classroom
Template

Tools & Platforms

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 material and test coding exercises (Course Content)

  3. Coordinate with the teaching assistant

  4. Prepare Homework (for Thursday Sessions)

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

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.

Content Introduction

Key Resources

Let's have a look at the Material

How to work with the material?

You are free to change the material as you like! If you believe slides are needed to explain a concept, do it! If you would explain a concept differently, go for it.

How to teach? Best Practices!

We share several best practices in the Course Content section. For example, the concept of "How little is enough?" or the "I Do, We Do, You Do" methodology. In the end, it is your decision how you want to teach it. We recommend to browse through the concepts before teaching a session: Course Content.


Course Overview

Welcome to ReDI School! We really appreciate that you are part of our community. In this page, you'll find an overview of the course. By volunteering, you contribute to our main goal: help our students gain the necessary skills to find a job in tech. ReDI School has now helped over 17.000 people advance their tech skills. This is only possible with the support of our volunteers <3

ReDI Students

Our student community brings together people from over 138 countries. Your course won't be different. Your students will come from a wide range of countries. They also come from diverse professional backgrounds - some are currently unemployed or underemployed, while others are students looking to prepare for their careers. With an average age of 32, many of our students hold a university degree and have several years of work experience. What unites all students is their passion for technology and their aim to build a career in the tech industry.

Curriculum

The JavaScript Course is a 14-week program designed to build upon HTML & CSS skills, introducing students to interactive web development using JavaScript. Each cohort consists of 25 students who meet twice a week (Tuesdays and Thursdays from 19:00-21:00).

Structure

The weekly schedule consists of two regular classes. Tuesday begins with a review of the previous week’s content. Students participate in live coding exercises and problem-solving activities. Homework from the previous week is discussed and feedback is provided. On Thursday, teachers introduce new concepts. Students engage in hands-on coding demonstrations and guided exercises. The session concludes with the assignment of the weekly homework task.

Between sessions, students are expected to dedicate 10-12 hours per week to coding assignments, and independent study.

Homework

We aim to give homework each Thursday. We ask students to complete the homework by next Tuesday (before the session starts). The homework reviewer corrects the homework and returns it to the students via Google Classroom.

Sessions

Day
Session
Description
Roles

Tuesday 19:00-21:00

This regular class is taught in pairs, with one person assigned as a session owner (the lecturer) and one as a teaching assistant. The class introduces the students to the new topic.

Session Owner, Session Assist

Thursday 19:00 - 21:00

This regular class is taught in pairs, with one person assigned as a session owner (the lecturer) and one as a teaching assistant. The class introduces the students to the new topic.

Session Owner, Session Assist

Roles

Role
Topic
Time per week

As a session owner, you lead the Regular Class. You prepare the session and coordinate with the teaching assistant.

4 hours per week

As a teaching assistant, you support the session owner in the input session. You open the Zoom call, track attendance, help answer questions, and provide support in break-out rooms.

3 hours per week

As a backup teacher, you are available and ready to jump in the case one of the teachers assigned for the day should have issues, or get sick. As a backup teacher, you don’t need to attend the session unless an emergency arises.

2 hours per week

Reviews the homework

2 hours per week

On-site Activities

Two sessions during the course will take place on a hybrid format - students in Hamburg will have a session on site, while the other students a parallel session online. We are organizing on-site activities in our three main locations. Find out more below.

We invite you to four on-site community events throughout the semester if you are located in Berlin and the surrounding. The Onboarding will also take place in person in Berlin. You are more than welcome to join!

We invite you to four on-site community events throughout the semester if you are located in Berlin and surrounding. The Onboarding and Demo Day will also take place in person in Düsseldorf. You are more than welcome to join!

Four in-person sessions are taking place in Hamburg: Onboarding, two regular course sessions, and Demo Day. If you are based in Hamburg, it would be fantastic if you could support the course in one or more of these sessions.

Conclusion

Complete your Self-Onboarding

Thank you very much for going through your Self-Onboarding! This ensures a smooth onboarding into your volunteer experience. Please complete the following typeform to finish the self-onboarding. If you face any problems, you can indicate them in the typeform.

That's it! Thanks for completing your self-onboarding. Feel free to browse around the teacher hub. See you soon!

Add material to Google Classroom (24h before) (")

Resource Type
Platform
Description

Slides + Exercises

Contains all slide decks and exercises.

Further Material

Slide decks from previous semesters.

GitHub: All files are in our . Have you seen the lessons and teacher guides?

That was a lot of content! Thanks for staying with us. Let's complete the self-onboarding in the next page:

❤️ Thank you for supporting our students as they take another step in their journey! To learn more about ReDI students and our community, visit .

The course has two online sessions per week. For on-site events, check out . The session format differs from what you might have seen before.

We hope that by reading this, you have a better idea of the course and what it means to volunteer at ReDI. Let's explore the now 📅.

Done

Zoom
Attendance Tracker
Course Sheet
Google Classroom
how to use Google Classroom
Teaching Guidelines
Session instruction slides
Class Engagement Resources
GitHub Repo
Complete your Self-Onboarding
About ReDI School
Timeline
🙌
On-site Activities
GitHub
Google Drive
Regular Class
Regular Class
Session Owner
Session Assistant
Backup Teacher
Homework Reviewer

Homework Reviewer

Overview

  • The homework reviewer reviews the homework submissions of the students.

  • More about Homework

Review Tool

Homework 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.

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 needs improvement.

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.

Homework Guidelines

Course Sheet

Course Sheet

  • Link: The link to your Course Sheet is pinned in Slack.

  • Course Management: We use the Course Sheet to organize the course.

  • Availability & Ownership: Volunteers assign themselves to the session. They show when they are available to teach.

  • Feedback: The coursesheet has a feedback tab where we collect feedback about the session.

Not available anymore?

  • Mark it in the Course Sheet so that others can see it!

Google Classroom

Google Classroom

  • Link: The link to your classroom is pinned in Slack.

  • Purpose: We use Google Classroom as our learning platform. We use it for two functions: Sharing material with the students and reviewing projects. You can also use it to create material.

  • Google Drive: Your Google Classroom is connected to a Google Drive where material is stored.

  • Calendar: Students are invited to the sessions through the calendar from the classroom

How to Upload Materials on Google Classroom

Go to Classwork. Go to Create. Select material to upload material, which is shared with the students. Select Topic to create a new section that can hold multiple materials.

Draft function: drafts are only visible to teachers - not to the students (yet). You can already work on material before sharing it with students. In order to share it, you publish the material.

Review Projects

  • Go to the Grades section. You find all the students; you can see who turned in the homework. Once you click on it, you can review their work, write a comment, and return it.

Are you not in Google Classroom?

You should have received an email invitation from ReDI. Please check your emails and spam folder. Otherwise, please get in touch with the ReDI team via Slack.

Attendance Tracker

Attendance Tracker

  • Who: The teaching assistant tracks attendance

  • When: Every regular class (usually 20 minutes into the session)

  • Access: Credentials are pinned in your teaching teams' Slack channel


Why track attendance?

We ask learners to join at least 80% of the sessions to obtain a certificate. We believe students can only learn if they attend. That's why attendance tracking is essential. ReDI follows up regularly with students with low attendance to offer support.

Attendance Status per Session

100% – Present: Arrive on time, actively participate, and keep the camera on.

50% – Excused: Notify in advance if unable to attend

50% – Late: Arrival more than 15 minutes late. Please mark as "Excused". If no excuse is known, select "Other." No explanation from students is required.

50% – Early Leave: Leaving before the break. Please mark as "Excused". If no excuse is known, select "Other." No explanation from students is required.

0% – Absent: No prior communication of absence

Camera on Policy

Students will only be marked as "present", if they join the class with their camera on.

If a student should experience internet connection problems during the class, they should either write it in the chat or unmute themselves to inform teachers and fellow students. If this is not possible, students should inform the class through a message in their students slack channel.


How to track Attendance?

Attendance Tracking App Demo
Attendance Tracking Steps Visualised

Zoom

Zoom

  • Zoom? It is our video conferencing tool for the classes.

  • Zoom Link: You find it pinned in Slack. The Zoom link is the same for the whole semester.

  • Recordings: We record the session. More: Recordings

  • Claim Host: Credentials are pinned in Slack. How to Join Zoom & Claim Host

  • Join early? The Zoom call opens 45 min ahead of time. Feel free to join early.


How to Join Zoom & Claim Host

  1. Find the link to the class meeting either in your calendar invite for the session or pinned in the teachers slack channel. Join with one click

  2. Go to the participants list and “Claim host”. Sign in with the host key to become the host. You can find the host key (a series of 6 numbers) pinned in the teacher Slack channel.

  1. Please make your co-teachers for the sessions co-hosts by right-clicking on their name from the participants list.

  2. Please do not forget to record the class. We record only Input and Q&A Sessions.

Recordings

Recordings automatically save into a drive students have access to as viewers. This Drive is pinned to the students slack channel. Recordings are available for whole semester. Break out rooms cannot be recorded.

Default Zoom Settings

  • When starting the meeting, audio is off, your video is off and recording is off.

  • Hosts are allowed to add co-hosts.

  • Possibility to send files via meeting chat.

Link:

Use the App: Install the for all functionality.

Breakout rooms enabled. How to setup breakout rooms: , .

Attendance Tracker
Zoom app
Video
Guide

Class Engagement

We provide additional tools that you can use to engage students more in your sessions! At ReDI, we like to use the following tools and icebreakers:

Mentimeter (Interactive Polls)

  • Create live polls, word clouds, and Q&A

  • Perfect for:

    • Icebreakers: Ask students about their expectations or background knowledge.

    • Quick polls: Check understanding of a topic in real-time.

    • Exit tickets: Gather feedback at the end of a session.

  • Login credentials in teachers' Slack channel

Kahoot (Learning Games)

  • Quiz-based learning with competitive elements

  • Perfect for Revision & Recaps - You create a quiz, and students participate live in class via browser or cell phone.

  • Login credentials in teachers' Slack channel

Icebreaker Ideas

You can use quick icebreakers at the start of your sessions to energize participants, build connections, and create an engaging and interactive learning environment. Here is a list of icebreakers. They shouldn't take more than 5 minutes to run.

1. Two Truths and a Lie

  • Description: Participants share three statements about themselves—two true and one false. The group has to guess which one is the lie.

  • How to Run: Use breakout rooms for smaller groups or let everyone participate in the main room.

  • Objective: Participants get to know each other in a fun way.

2. Virtual Scavenger Hunt

  • Description: Give participants a list of items to find in their home within 1-2 minutes (e.g., something red, something that makes noise).

  • How to Run: Ask them to bring the items back to the camera and share a quick story about one of them.

  • Objective: The activity is an energizer.

3. Emoji Reactions

  • Description: Pose a question or statement (e.g., "How are you feeling about today’s session?") and ask participants to respond using emojis only.

  • How to Run: Use the chat in Zoom.

  • Objective: It is an easy way for participants to share how they are doing.

More Resources

Mentimeter.com
Kahoot.com
13 online icebreakers
Ice breakers using slido
Ice breakers in Kahoot
Ice breakers in Menti

Teaching Team

Role
Topic

Leads regular classes, introduces new concepts and practices it with the students

Manages Zoom logistics and supports students during classes

Provides emergency coverage when regular teachers are unavailable

Reviews the homework

Session Owner
Session Assistant
Backup Teacher
Homework Reviewer

Demo Day

🎤 Class Demo Day

The Class Demo Days are an internal presentation day held in the final week of the course. Each student presents their project in front of their classmates and teachers. It’s a supportive environment focused on:

  • Showcasing the project

  • Practicing technical presentations

  • Sharing challenges and lessons learned

  • Celebrating the team’s work

🧑‍🏫 This day helps students build confidence and receive feedback from peers and instructors.


🎉 Demo Day

The Demo Day is a public, on-site event where selected student teams present their projects to the broader ReDI community, including partners.

  • The event highlights excellence, creativity, and collaboration

  • Students present in a more formal setting with networking opportunities

  • It’s a moment of celebration and recognition for everyone involved


📅 Timeline (Spring 2025)

📌 Attendance and presentation at the Class Demo Day are required for students to receive a certificate.


🗣️ Presentation Guidelines

To help learners prepare their pitch, here’s a suggested format:

  • Length: Max. 5 minutes

  • Mode: Slides or Live Demonstration

  • Proposed Structure:

    1. Intro – What’s the project, and what problem does it solve?

    2. Demo – Show the live website

    3. Challenges & Learning – What went well? What was hard? What did you learn?

🧑‍🏫 Encourage learners to rehearse and help each other practice!


🧾 Certification Requirements

To receive a ReDI certificate, learners must:

  • Attend at least 80% of the course

  • Complete and present all three Projects

  • Attend the Internal Class Demo Day

  • Complete 2 IBM SkillsBuild Courses


🤝 Class Culture & Support

💬 “We grow by doing, and by helping each other.”

  • Foster a positive, collaborative learning

  • Dedicate class time to mentoring, code reviews, and feedback

  • Celebrate all wins—big or small—as students build real web apps


🎉 Let’s end the Bootcamp by cheering each other on!

Milestone

Date

Class Demo Days

16.06.2025 18.06.2025

Demo Day

Date to be confirmed

Course Content

Key Resources

How do I update material?

GitHub - Request access to the GitHub repo. Update the slide deck for your session through a pull request.

Homework Guidelines?

How do I create more engagement in class?

Best practices for teaching?

More material, feedback or ideas?

If you find good material, ReDI could use, and if you have feedback or further ideas, feel free to contact Julian via Slack or email (julian@redi-school.org).

Resource Type
Platform
Description

Course Content

Contains all slide decks and exercises.

Student Hub

Hub for students with information about ReDI, the course, the sessions and relevant links

Homework
Class Engagement
Teaching Guidelines
GitHub
Gitbook

Teaching Guidelines

Teaching Method: I Do, We Do, You Do

The "I Do, We Do, You Do" method is a teaching method designed to help students learn new concepts by first observing, then practicing with guidance, and finally working independently.

  • I Do: The teacher demonstrates the task while explaining the steps and thought process aloud. This stage is about modeling the correct way to approach the task and highlighting key concepts and techniques.

  • We Do: The session owner walks the students through an activity. The students follow along (code or design along). This collaborative stage allows students to apply what they've seen with support, ask questions, and receive immediate feedback.

  • You Do: Students work independently on the task. This stage allows them to practice the skill on their own.

Example: Introducing Javascript

  • I Do: The teacher introduces JavaScript and demonstrates a simple script that shows an alert when clicking a button. Key concepts like variables, functions, and events are explained briefly.

  • We Do: The teacher walks the students through creating a function that changes a heading's color when clicking a button. The students follow and code along. The teacher shares their screen and gives the students time to code along. Together, the teacher and the students write the function, select the element, and add an event listener, with the teacher guiding and asking questions to engage students.

  • You Do: Students independently write JavaScript to change the text of a paragraph when a button is clicked in a breakout room. They practice using variables, functions, and event listeners and then share their work for feedback.

Tips and Tricks

  • Context before content - We experienced that explaining why a concept is important helps a lot in understanding what the concept is about. Why should you learn this concept? Try to give the context. Maybe explain where you use it in your daily work life. Or explain how this concept can help to solve a bigger problem

  • Engage with Students: Ask questions to check understanding. Use their names and keep the tone friendly and encouraging.

  • Be Prepared but Flexible: Have a plan but adapt based on student needs.

  • Feedback is Key: Provide constructive feedback to help students improve. Celebrate small wins to keep motivation high.

More Resources

  • Student Gitbook (LINK)

  • Ice Breakers and Energizers - Do you want to start the session with an energizer? Have a look at Class Engagement

Teaching Guidelines

Teaching Method: I Do, We Do, You Do

The "I Do, We Do, You Do" method is a teaching method designed to help students learn new concepts by first observing, then practicing with guidance, and finally working independently.

  • I Do: The teacher explains and demonstrates a concept by explaining the steps and thought process aloud. The teacher can use live coding to show the steps. Explain why you're creating variables, choosing certain loops, or implementing specific functions. Demonstrate not only successful code but also introduce common errors and how to troubleshoot them. This helps students understand that mistakes are a normal part of the coding process and builds their debugging skills from the start.

  • We Do: Once students have observed your demonstration, transition to the guided practice or "We Do" phase. The teacher walks the students through an activity. You might provide partially completed code for students to finish and ask for suggestions on what comes next. The students code along. This collaborative stage allows students to apply what they've seen with support, ask questions, and receive immediate feedback.

  • You Do: The final phase is independent practice, or "You Do." Assign coding tasks similar to those you've demonstrated and practiced together, but allow students to work through them independently. Provide clear instructions and success criteria so students know what's expected. During this time, circulate through the classroom to offer assistance where needed, but resist the urge to take over. This is when students develop coding confidence and problem-solving abilities.

Example: Introducing Javascript

  • I Do: The teacher introduces JavaScript and demonstrates a simple script that shows an alert when clicking a button. Key concepts like variables, functions, and events are explained briefly.

  • We Do: The teacher walks the students through creating a function that changes a heading's color when clicking a button. The students follow and code along. The teacher shares their screen and gives the students time to code along. Together, the teacher and the students write the function, select the element, and add an event listener, with the teacher guiding and asking questions to engage students.

  • You Do: Students independently write JavaScript to change the text of a paragraph when a button is clicked in a breakout room. They practice using variables, functions, and event listeners and then share their work for feedback.

How do you teach a session with I Do, We Do, You Do?

We see two ways to apply the method to a session:

  1. You split the whole session by the method:

    1. I Do - Introduce concepts for ~45min and try to live code them)

    2. We Do - live code the same concepts and ask students to follow along for ~ 45min)

    3. You Do - let students apply the concepts independently in a slightly different way for ~ 20min

  2. You introduce every concept by the method:

    1. Concept A (example: Intro to React) - I Do (15 min), We Do (15 min), You Do (15 min). After introducing concept A with the method, you introduce concept B once again with the method.

    2. Concept B (example: React Components) - I Do (30 min), We Do (30 min), You Do (15 min)

Why is the method helpful?

  • Breaks Down Complexity: Coding has many rules and new concepts—seeing it done first, then trying with help, and finally doing it alone makes learning manageable.

  • Teaches Problem-Solving: Students learn how to approach coding problems by watching, then practicing with guidance, before solving independently.

  • Builds Confidence: This step-by-step method reduces frustration with coding errors and builds confidence gradually through supported practice.

  • Reflects Real Coding Practice: Matches how actual programmers learn—by studying examples, working with others, and then coding independently.

Implementation Tips

  • Start with smaller coding problems that can be completed in one session

  • Think about examples and exercises in advance

  • Connect coding concepts to everyday experiences using analogies

  • Show both correct solutions and common mistakes with fixes

  • Use color-coding to highlight syntax patterns

  • Incorporate visual aids and flowcharts

  • Celebrate debugging as learning rather than failure

  • Share stories of professional programmers overcoming challenges

Articles about the method:

Other Best Practices

  • Context before content - We experienced that explaining why a concept is important helps a lot in understanding what the concept is about. Why should you learn this concept? Try to give the context. Maybe explain where you use it in your daily work life. Or explain how this concept can help to solve a bigger problem

  • Engage with Students: Ask questions to check understanding. Use their names and keep the tone friendly and encouraging.

  • Be Prepared but Flexible: Have a plan but adapt based on student needs.

  • Feedback is Key: Provide constructive feedback to help students improve. Celebrate small wins to keep motivation high.

Ice Breakers:

Watch on how to run the Regular Class.

Ice Breakers and Energizers - Do you want to start the session with an energizer? Have a look at

this video
Class Engagement
https://classwork.com/i-do-we-do-you-do-strategy-gradual-release-strategy/
https://explaineverything.com/blog/inspiring-educators/how-to-master-the-i-do-we-do-you-do-model-approach-to-teaching/
https://thirdspacelearning.com/blog/i-do-we-do-you-do/

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

Weekly Sessions

Timeline

Preparation Phase

Teachers Onboarding & Planning Sessions

⏰ Feb 12th - 20th, 2 meetings per course

A ReDI volunteer journey starts with a welcome to the ReDI community! During teachers onboarding & planning sessions, we:

  • Welcome new & returning volunteer teachers to the community

  • Share semester mission, goals & timeline

  • Plan / review the outline of the coursw

  • Align on teaching roles & processes

  • Prepare for students selection process and course kick off

Students Screening / Interviews

⏰ Feb 24th - 28th, 1 session, 2 hours, optional briefing 30 min before event

The interview is the last step to become a ReDI students, after completing a prework and submitting an official application. We interview in order to:

  • Get to know the students

  • Ensure their time availability

  • Check their understanding of course content

  • Understand their motivation to join

We interview every candidate who is not a returning students who passed with achievement in the past semester. *For Circles & Bootcamps we will interview both new & returning students.

We recommend the candidate a course if motivation, understanding of the content and time commitment fit. Based on your decision, we recommend your course, a lower or more advanced one.

Interview Preparation

  • You will receive the information on this page, as well as the interview form for your course along with your calendar invite for the interviews. Please accept or decline the invitation by February 19th to confirm your attendance so we can plan accordingly.

  • A non mandatory 30-minute briefing will also be held on interview day to review the process and address any questions before we start.

On Interview day

  1. Join the Zoom call from your calendar invite.

  2. The ReDI Team will welcome you and assign you to a breakout room.

  3. A max of 6 students will be sent to you one at a time for 1:1 interviews (20 minutes total):

    • 15 minutes conversation

    • 5 minutes for notes and recommendation

  4. A dedicated Slack channel will be set up for real-time communication throughout the interviews and breakout sessions. Once you complete an interview, notify the team on Slack, and the next student will be sent your way.

Teachers Training

⏰ March 3rd-12th, non mandatory We'll offer trainings to our wonderful volunteer teachers to make sure they feel confident sharing their knowledge in the classroom. Training plan and additional information will be presented during onboarding & planning meetings.

Kick Off Preparation

⏰ Courses kick off on March 17th or 18th

During our teachers / students kick-off day, you welcome the students to the class. The session is facilitated by each teaching team as a collaborative effort. You find the materials for the kick off session in your course sheet. You need to sign up for a role by adding your name to the meeting agenda. You prepare for the event by finalising the materials needed for your role. The main goals of the meetings are:

  • Getting to know each other, create a welcoming class atmosphere

  • Introducing the teaching team to the students

  • Presenting the course & class tools

Teaching Phase

Mid-Semester Students Feedback Session - ReDI Led

⏰ May 5th - 7th, 1 session per class, 2 hours Exact date available in your course sheet LINK

The ReDI team will meet with the students to collect feedback on the course as well as suggestions from the students. The session is moderate entirely by the ReDI team and results are brought to the teaching team at the teachers touch point one week later.

Teachers Touch Points

⏰ May 12th - 14th, 1 session per team, 2 hours Exact date available in your course sheet LINK We meet at mid semester with the teaching team to:

  • hear feedback from the students and ideate solutions,

  • celebrate our achievements and

  • plan the rest of the semester.

Teachers touch points happen while students are attending ReDI's career week.

Career Week

The Career Week at ReDI School is a week of training webinars designed to help students connect with industry professionals, improve job-related skills, explore career opportunities and boost their job readiness. More LINK CAREER SERVICES ✅ Students need to attend 2 career events during the semester (within or outside the career week) in order to graduate. Students choose topics most interesting to them. ✅ Other career events during the semester might include: company visits, networking opportunities, mentoring matching events.

During career week, classes are on hold. We use this time to organize teaching team touch points.

Project Phase

⏰ Last 2 or 3 weeks of classes are dedicated to project Exact dates available in your course sheet LINK The Project Phase at ReDI School is the part of the course where learners apply what they've learned by working on a real-world projects. It is also a way to boost students confidence and improve job readiness. It usually happens towards the end of the program and is designed to help building practical experience and a strong portfolio. For learners, this is a chance to foster:

🔹 Team Collaboration – Work in teams with other students, just like in a real job. 🔹 Hands-on Learning – Apply coding, design, or data skills to solve real problems. 🔹 Mentor Support – Get guidance from teachers on real case scenarios. 🔹 Final Presentation – Showcase their project to classmates, mentors, and sometimes even company representatives.

Community Events

Local Community Events at ReDI School are gatherings where students, alumni, mentors, and industry professionals come together to network informally and share some quality time. These events help you connect with the tech community in your city (Berlin, Hamburg, or NRW). We'll organize 2 community events per each location this semester.

Let's go to the next section and dive into the tools:

Essential Tools

Practice Session Owner

Overview

Session Preparation

  • Review concepts from the previous class

  • Prepare practice exercise

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 ❤️

As Practice Session Owner, you lead a 2-hour weekly session. The goal of the on Monday is to practice the content covered in the last session. We suggest using the README.md and teacher_guide.md of the previous session as guidance. The focus is on hands-on exercises and clarifying questions

Practice Session

Regular Class

Purpose

Weekly class where students learn new concepts.

Session Details

  • When: Tuesdays and Thursdays, 19:00 - 21:00

  • Where: Zoom (link in Slack)

  • Team: Session Owner leads the session and Session Assist supports

Class Structure

  1. Review previous content

  2. Introduce weekly milestone

  3. Present new concepts

  4. Guided practice ("We Do")

  5. Group practice in breakout rooms ("You Do")

More Resources

  • Course Content

  • Session Owner

  • Session Assist

Practice Session with Q&A

Purpose

Students practice concepts from the previous class and get answers to their questions about projects and course content.

Session Details

  • When: Mondays, 19:00 - 21:00

  • Where: Zoom (link in Slack)

  • Format: Guided practice and Q&A

  • Team: Practice Session Owner leads session, Session Assist supports.

Session Structure

  1. Practice exercises on recent concepts

  2. Address questions

  3. Project support as needed

Roles

  • Practice Session Owner: Leads exercises and answers questions

  • Students: Participate in practice and ask questions

Resources:

  • Course Content

This explains the Session Formats.

VIDEO

Tools & Platforms

Course Sheet
Zoom
Attendance Tracker
Google Classroom

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 the slides and exercises (Course Content)

  3. Test coding exercises

  4. Prepare Homework (for Thursday Sessions)

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


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.

Add material to Google Classroom (24h before) (")

how to use Google Classroom
Teaching Guidelines
Session instruction slides
Class Engagement Resources

Course Sheet

Course Sheet

  • Link: The link to your Course Sheet is pinned in Slack.

  • Course Management: We use the Course Sheet to organize the course.

  • Availability & Ownership: Volunteers assign themselves to the session. They show when they are available to teach.

  • Feedback: The coursesheet has a feedback tab where we collect feedback about the session.

Not available anymore?

  • Mark it in the Course Sheet so that others can see it!

Timeline

Preparation Phase

Teachers Onboarding & Planning Sessions

⏰ Feb 12th - 20th, 2 meetings per course

A ReDI volunteer journey starts with a welcome to the ReDI community! During teachers onboarding & planning sessions, we:

  • Welcome new & returning volunteer teachers to the community

  • Share semester mission, goals & timeline

  • Plan / review the outline of the coursw

  • Align on teaching roles & processes

  • Prepare for students selection process and course kick off

Students Screening / Interviews

⏰ Feb 24th - 28th, 1 session, 2 hours, optional briefing 30 min before event

The interview is the last step to become a ReDI students, after completing a prework and submitting an official application. We interview in order to:

  • Get to know the students

  • Ensure their time availability

  • Check their understanding of course content

  • Understand their motivation to join

We interview every candidate who is not a returning students who passed with achievement in the past semester. *For Circles & Bootcamps we will interview both new & returning students.

We recommend the candidate a course if motivation, understanding of the content and time commitment fit. Based on your decision, we recommend your course, a lower or more advanced one.

Interview Preparation

  • You will receive the information on this page, as well as the interview form for your course along with your calendar invite for the interviews. Please accept or decline the invitation by February 19th to confirm your attendance so we can plan accordingly.

  • A non mandatory 30-minute briefing will also be held on interview day to review the process and address any questions before we start.

On Interview day

  1. Join the Zoom call from your calendar invite.

  2. The ReDI Team will welcome you and assign you to a breakout room.

  3. A max of 6 students will be sent to you one at a time for 1:1 interviews (20 minutes total):

    • 15 minutes conversation

    • 5 minutes for notes and recommendation

  4. A dedicated Slack channel will be set up for real-time communication throughout the interviews and breakout sessions. Once you complete an interview, notify the team on Slack, and the next student will be sent your way.

Teachers Training

⏰ March 3rd-12th, non mandatory We'll offer trainings to our wonderful volunteer teachers to make sure they feel confident sharing their knowledge in the classroom. Training plan and additional information will be presented during onboarding & planning meetings.

Kick Off Preparation

⏰ Courses kick off on March 17th or 18th

During our teachers / students kick-off day, you welcome the students to the class. The session is facilitated by each teaching team as a collaborative effort. You find the materials for the kick off session in your course sheet. You need to sign up for a role by adding your name to the meeting agenda. You prepare for the event by finalising the materials needed for your role. The main goals of the meetings are:

  • Getting to know each other, create a welcoming class atmosphere

  • Introducing the teaching team to the students

  • Presenting the course & class tools

Teaching Phase

Mid-Semester Students Feedback Session - ReDI Led

⏰ May 5th - 7th, 1 session per class, 2 hours Exact date available in your course sheet LINK

The ReDI team will meet with the students to collect feedback on the course as well as suggestions from the students. The session is moderate entirely by the ReDI team and results are brought to the teaching team at the teachers touch point one week later.

Teachers Touch Points

⏰ May 12th - 14th, 1 session per team, 2 hours Exact date available in your course sheet LINK We meet at mid semester with the teaching team to:

  • hear feedback from the students and ideate solutions,

  • celebrate our achievements and

  • plan the rest of the semester.

Teachers touch points happen while students are attending ReDI's career week.

Career Week

The Career Week at ReDI School is a week of training webinars designed to help students connect with industry professionals, improve job-related skills, explore career opportunities and boost their job readiness. More LINK CAREER SERVICES ✅ Students need to attend 2 career events during the semester (within or outside the career week) in order to graduate. Students choose topics most interesting to them. ✅ Other career events during the semester might include: company visits, networking opportunities, mentoring matching events.

During career week, classes are on hold. We use this time to organize teaching team touch points.

Project Phase

⏰ Last 2 or 3 weeks of classes are dedicated to project Exact dates available in your course sheet LINK The Project Phase at ReDI School is the part of the course where learners apply what they've learned by working on a real-world projects. It is also a way to boost students confidence and improve job readiness. It usually happens towards the end of the program and is designed to help building practical experience and a strong portfolio. For learners, this is a chance to foster:

🔹 Team Collaboration – Work in teams with other students, just like in a real job. 🔹 Hands-on Learning – Apply coding, design, or data skills to solve real problems. 🔹 Mentor Support – Get guidance from teachers on real case scenarios. 🔹 Final Presentation – Showcase their project to classmates, mentors, and sometimes even company representatives.

Community Events

Local Community Events at ReDI School are gatherings where students, alumni, mentors, and industry professionals come together to network informally and share some quality time. These events help you connect with the tech community in your city (Berlin, Hamburg, or NRW). We'll organize 2 community events per each location this semester.

Let's go to the next section and dive into the tools:

Essential Tools

Homework

Overview

  • Homework is given every Thursday session via Google Classroom

  • The Session Owner of the Thursday session prepares the homework

  • Students have until the following Tuesday session to complete the homework

  • The Homework Reviewer reviews their homework from Tuesday until Thursday

  • Homework is not graded. The goal is for students to learn by working on their homework. If it is not complete or perfect, it’s okay. We ask students to complete at least 80% of the homework.

Why homework?

  • Learning by Doing - Through homework, students practice and code more. The more they practice, the better the students get!

  • Students try out the concepts in homework. The review helps students to know if they are on track.

  • By reviewing the homework, we might better understand which concepts need further elaboration.

Homework Process

1. Create Homework

Session Owner creates homework.

2. Add to Google Classroom

3. Present Homework in Class

Session Owner presents the homework assignment on Thursday

4. Students hand in homework

Students hand in the homework until the start of the next session (Tuesday)

5. Show solution

Session Owner shows the solution of the homework in the Tuesday session

6. Teachers review homework

Homework Reviewer reviews submissions until Thursday

How much homework?

Focus the homework on one achievable, practical problem. That means:

  • Give only one problem, not multiple, it would overwhelm and lower chances of completion.

  • Achievable - make it equally hard or slightly harder than the last practice exercise in class. Make it feasible in terms of the time required. If you need 5 minutes to solve it, it will probably take the students 30 minutes or longer. Don’t go over 5min for yourself.

  • Optional - to accommodate the more advanced students in the class, you can add optional extra questions.

How to add Homework to Google Classroom?

Homework Guidelines

Session Owner creates a homework assignment in Google Classroom at least 1 day before class. .

Go to , Go to Create, and select Assignment.

Give title, instructions and set the due date to the next session on Tuesday ().

Support: .

Google Classroom
template
Video for Google Classroom
Template

Homework Reviewer

Overview

  • The homework reviewer reviews the homework submissions of the students.

  • More about Homework

Review Tool

Homework 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.

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 needs improvement.

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.

Homework Guidelines

Attendance Tracker

Attendance Tracker

  • Who: The teaching assistant tracks attendance

  • When: Every regular class (usually 20 minutes into the session)

  • Access: Credentials are pinned in your teaching teams' Slack channel


Why track attendance?

We ask learners to join at least 80% of the sessions to obtain a certificate. We believe students can only learn if they attend. That's why attendance tracking is essential. ReDI follows up regularly with students with low attendance to offer support.

Attendance Status per Session

100% – Present: Arrive on time, actively participate, and keep the camera on.

50% – Excused: Notify in advance if unable to attend

50% – Late: Arrival more than 15 minutes late. Please mark as "Excused". If no excuse is known, select "Other." No explanation from students is required.

50% – Early Leave: Leaving before the break. Please mark as "Excused". If no excuse is known, select "Other." No explanation from students is required.

0% – Absent: No prior communication of absence

Camera on Policy

Students will only be marked as "present", if they join the class with their camera on.

If a student should experience internet connection problems during the class, they should either write it in the chat or unmute themselves to inform teachers and fellow students. If this is not possible, students should inform the class through a message in their students slack channel.


How to track Attendance?

Attendance Tracking App Demo
Attendance Tracking Steps Visualised

Link:

Attendance Tracker

Content Introduction

Projects

Our Full Stack Bootcamp is project-based - students learn by working on hands-on projects. Each project is broken into weekly milestones.

Weekly Schedule

  • Thursday: Introduce new concepts and the next milestone

  • Thursday - Wednesday: Students work on their milestone

  • Monday: Practice session with Q&A

  • Wednesday: Students present their milestones in the Coaching Session

Teaching Materials

Our core teaching materials are hosted in our GitHub repository:

Resource Type
Platform
Description

Projects

Contains all course projects. Includes weekly milestones.

Lessons

In the GitHub repo, you find in every milestone folder a lesson.md for each week. The file contains an explanation of how to approach the session, what topics to cover, and how you can introduce the concept with an example. You find the lesson.md files in the respective milestone folders in GitHub.

Teacher Guide

In the GitHub repo, you find in every milestone folder a teacher_guide.md for each week. It contains guidelines on how to run the Practice Session on Mondays.

Student Hub

Student-facing documentation, tutorials, and concept explanations. Students use this as their main reference.

Further Material

Slide decks from previous semesters.

Overview by Session

Session
Material & Descriptions

Regular Class

  • lesson.md -It contains a suggested plan to structure the session. It explains which concepts to cover and how we could introduce them.

  • At the end of each Regular Class, we introduce the students to the next milestone (what students work on until next Wednesday). Milestone README.md outlines the next project milestone.

  • Additional Resources - Previous semester materials, including slide decks and exercises

  • Student Hub - Further explanations and resources shared directly with students

Practice Session with Q&A

  • teacher_guide.md - Guidance for practice activities and handling student questions

Coaching Session

  • No teaching is needed. Focused on reviewing student work and providing feedback.

  • Reviewing the milestoneREADME.mdt helps to understand what the milestone contains students are working on.

Let's have a look at the Material

  • Additional Material: Check out prior slide decks and exercises here Course Content

  • Student Hub: The student hub is the "knowledge base" for the students where they find extra resources about the concepts being covered in the course. It is currently under construction. We will share it with you soon!

How to work with the material?

You are free to change the material as you like! If you believe slides are needed to explain a concept, do it! If you would explain a concept differently, go for it.

We know the material is not perfect! For sure, parts are not so clear and can be improved. Please help us to improve it further! If something is unclear or missing - feel free to add it! Thanks to your contribution, we can improve the material in the future!

How to teach? Best Practices!

We share several best practices in the Course Content section. For example, the concept of "How little is enough?" or the "I Do, We Do, You Do" methodology. In the end, it is your decision how you want to teach it. We recommend to browse through the concepts before teaching a session: Course Content.


That was a lot of content! Thanks for staying with us. Let's complete the self-onboarding in the next page: Complete your Self-Onboarding.

GitHub: You can find all files in our . Do you see the lessons and teacher guides?

GitHub Repo
GitHub
GitHub
GitHub
Gitbook
Google Drive

Essential Tools

Here's an overview of the key tools we use for teaching and communication. Please set up these tools now to ensure effective collaboration with your team and students.

Slack

This is our main communication tool, both with teachers and with the students. You'll have access by default to your teaching team channel and the students' channel. Additionally, you can join our community channels in Berlin, NRW, and Hamburg to learn about local events. Please check Slack regularly during the semester and communicate with your teaching team via Slack if you cannot make it to class.

Action


Google Calendar

We use Google Calendar to send semester meeting appointments to teachers and students.

Actions


Zoom

Our online sessions are running on Zoom. We highly recommend installing and updating the Zoom app on your device, as the online version doesn't cover all functionalities. Please note: The class Zoom link is the same for the entire semester.

Actions


Google Classroom

We use Google Classroom to share material with the students and to collect and give feedback to projects and homework.

Actions


Please complete all steps before going to the next section of the self-onboarding. If you face any issues, please reach out to the ReDI team via E-Mail or Slack. Once you are done, let's dive into the Content Introduction.

Open the Email with the Slack invitation from ReDI. .

to your Laptop (and or mobile phone).

Watch the "" video

Done?

Enter ReDI Slack
Download Slack
how to use Google Classroom
✅

Learning Design

Project-Based Learning

The course follows a project-based learning approach. Students learn hands-on through projects the whole semester. We saw that students are more motivated to work on projects than homework and seek to apply their new skills in practical cases. Each project lasts four weeks and includes a recap week, where the previous content is recapped.

Weekly Milestones

Projects are broken into manageable weekly milestones:

  • Students complete one part of the project each week

  • Each milestone applies concepts learned in Thursday's session

  • Progress is presented in Tuesday's coaching session

  • Builds toward a complete project over 4 weeks

Weekly Learning Flow

Each week follows a structured pattern to ensure consistent learning and progress:

Day
Activity
Description

Monday

Practice Session with Q&A

Students practice the concepts with the teachers. They can ask questions regarding the current milestone.

Wednesday

Coaching Session

Students present their weekly milestone progress and receive feedback

Thursday

Input Session

New concepts are introduced for the next milestone

Between Sessions

Project Work

Students work independently on their milestone tasks

How the Bootcamp fits into the Full Stack Track

The Bootcamp is part of the Full Stack Track. In this Vision Board you can see how the courses are connected:

Questions?

If you have any questions regarding the Learning Experience Design of the course, please contact your Course Manager.

Class Engagement

We provide additional tools that you can use to engage students more in your sessions! At ReDI, we like to use the following tools and icebreakers:

Mentimeter (Interactive Polls)

  • Create live polls, word clouds, and Q&A

  • Perfect for:

    • Icebreakers: Ask students about their expectations or background knowledge.

    • Quick polls: Check understanding of a topic in real-time.

    • Exit tickets: Gather feedback at the end of a session.

  • Login credentials in teachers' Slack channel

Kahoot (Learning Games)

  • Quiz-based learning with competitive elements

  • Perfect for Revision & Recaps - You create a quiz, and students participate live in class via browser or cell phone.

  • Login credentials in teachers' Slack channel

Icebreaker Ideas

You can use quick icebreakers at the start of your sessions to energize participants, build connections, and create an engaging and interactive learning environment. Here is a list of icebreakers. They shouldn't take more than 5 minutes to run.

1. Two Truths and a Lie

  • Description: Participants share three statements about themselves—two true and one false. The group has to guess which one is the lie.

  • How to Run: Use breakout rooms for smaller groups or let everyone participate in the main room.

  • Objective: Participants get to know each other in a fun way.

2. Virtual Scavenger Hunt

  • Description: Give participants a list of items to find in their home within 1-2 minutes (e.g., something red, something that makes noise).

  • How to Run: Ask them to bring the items back to the camera and share a quick story about one of them.

  • Objective: The activity is an energizer.

3. Emoji Reactions

  • Description: Pose a question or statement (e.g., "How are you feeling about today’s session?") and ask participants to respond using emojis only.

  • How to Run: Use the chat in Zoom.

  • Objective: It is an easy way for participants to share how they are doing.

More Resources

Mentimeter.com
Kahoot.com
13 online icebreakers
Ice breakers using slido
Ice breakers in Kahoot
Ice breakers in Menti

Session Owner

Overview

Session Preparation

  1. Review previous class feedback in Slack

  2. Review and update material in GitHub (Course Content)

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

  • Content: Course Content

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.

As a session owner, you lead the weekly , introducing key concepts and guiding students through exercises. We have material prepared in GitHub. We suggest using the I Do, We Do, You Do method to introduce the content. However, you can adapt the material and use your teaching style.

Plan how to introduce the concepts with live coding ()

Add slides (if you use some) to Google Classroom (24h before) (")

How to Teach? I Do We Do You Do Method:

How to Engage Students:

Regular Class
I Do, We Do, You Do Method
how to use Google Classroom
Teaching Guidelines
Class Engagement Resources
Full Stack Track - Vision Boardmural.co

Session Assist

Overview

As a session assistant, you provide technical and administrative support during 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

Google Classroom

Google Classroom

  • Link: The link to your classroom is pinned in Slack.

  • Purpose: We use Google Classroom as our learning platform. We use it for two functions: Sharing material with the students and reviewing projects. You can also use it to create material.

  • Google Drive: Your Google Classroom is connected to a Google Drive where material is stored.

  • Calendar: Students are invited to the sessions through the calendar from the classroom

How to Upload Materials on Google Classroom

Go to Classwork. Go to Create. Select material to upload material, which is shared with the students. Select Topic to create a new section that can hold multiple materials.

Draft function: drafts are only visible to teachers - not to the students (yet). You can already work on material before sharing it with students. In order to share it, you publish the material.

Review Projects

  • Go to the Grades section. You find all the students; you can see who turned in the homework. Once you click on it, you can review their work, write a comment, and return it.

Are you not in Google Classroom?

You should have received an email invitation from ReDI. Please check your emails and spam folder. Otherwise, please get in touch with the ReDI team via Slack.

Zoom

Zoom

  • Zoom? It is our video conferencing tool for the classes.

  • Zoom Link: You find it pinned in Slack. The Zoom link is the same for the whole semester.

  • Recordings: We record the session. More: Recordings

  • Claim Host: Credentials are pinned in Slack. How to Join Zoom & Claim Host

  • Join early? The Zoom call opens 45 min ahead of time. Feel free to join early.


How to Join Zoom & Claim Host

  1. Find the link to the class meeting either in your calendar invite for the session or pinned in the teachers slack channel. Join with one click

  2. Go to the participants list and “Claim host”. Sign in with the host key to become the host. You can find the host key (a series of 6 numbers) pinned in the teacher Slack channel.

  1. Please make your co-teachers for the sessions co-hosts by right-clicking on their name from the participants list.

  2. Please do not forget to record the class. We record only Input and Q&A Sessions.

Recordings

Recordings automatically save into a drive students have access to as viewers. This Drive is pinned to the students slack channel. Recordings are available for whole semester. Break out rooms cannot be recorded.

Default Zoom Settings

  • When starting the meeting, audio is off, your video is off and recording is off.

  • Hosts are allowed to add co-hosts.

  • Possibility to send files via meeting chat.

Use the App: Install the for all functionality.

Breakout rooms enabled. How to setup breakout rooms: , .

Zoom app
Video
Guide

Course Content

GitHub

The material for the bootcamp is in GitHub. You can find all the material in the project folders. There is a README for every week, with a description of the concepts we introduce and the deliverables for the students.

Material for Regular Class on Thursday

Resource Type
Platform
Description

Material

The README file in every milestone folder is for teachers to introduce the content and for students to review the material. Furthermore, it contains the "Expected Deliverables" that students are asked to complete by next Wednesday.

Teacher Guide

You can find in every milestone folder a teacher_guide.md for each week. It contains further instructions on how to introduce the content.

Slides

If you want to use slides for teaching, you can reuse slide decks from previous semesters. However, the primary teaching resource is the material in GitHub. The slide decks are not adapted to the current content, so they might require some adaptation.

  • Prior Material? If you taught in the past semester at ReDI, you might have existing material you would like to reuse. That is fantastic! Please add the content to GitHub.

Consolidate & Update Material

  • With the teaching team, we discussed to simplify and consolidate the material. That means, we want to have only one relevant file per milestone for the students and teachers - which is the README.

  • If you are the Session Owner, please consolidate the material for your session - or ask the team for support.

  • How we consolidate? We use the lesson.md as a baseline, and we add the learning objectives from the README at the start of the lesson, the required deliverables, and references of the README at the end of the file. If you have any questions, flag it in SLACK.

  • Let's improve the material together - flag mistakes, inconsistencies and improvements with issues in Github

Material for Practice Session on Monday

  • The goal of the Practice Session on Monday is to practice the content covered in the last session. We suggest using the README.md and teacher_guide.md of the previous session as guidance.

Material for Coaching Session on Wednesday

  • No teaching is needed. Focused on reviewing student work and providing feedback.

  • Reviewing the milestoneREADME.mdt helps to understand what the milestone contains students are working on.

How do I teach the material?

How do I create more engagement in class?

The concept behind the course

More material, feedback or ideas?

If you find good material, ReDI could use, and if you have feedback or further ideas, feel free to contact Julian via Slack or email (julian@redi-school.org).

More information about the session: .

If you are looking for more code snippets, have a look at the Berlin React .

Currently, we have a README.md, a lesson.md and reference.md file per milestone. We merge them into one file (example: ).

More information about the session: .

More information about the session: .

Regular Class
GitHub Repo
Milestone 1 - Project 1
Practice Session
Coaching Session
Teaching Guidelines
Class Engagement
Learning Design
GitHub
GitHub
Google Drive

Teaching Team

Role
Topic

Leads small group sessions, providing feedback on student milestone presentations

Leads regular classes, introduces new concepts and project milestones

Manages Zoom logistics and supports students during classes

Provides emergency coverage when regular teachers are unavailable

Leads practice sessions, helping students apply concepts through exercises

Coach
Session Owner
Session Assist
Backup Teacher
Practice Session Owner

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 ❤️

Full Stack Circle

Get Started

Most important Resources

Tools
Description
How to use it

course management

share material & project review

Zoom link for the sessions

Track student attendance

Course Material

Material
Description
How to use it

prior material

knowledge base for students

Weekly Class Schedule

Day
Session
Description
Roles

Monday 19:00 - 21:00

Project Session

We meet for two weekly online sessions to support the students work step-by-step on the project. Agenda: General standups, updates in main room, then breakout rooms

Guides

Wednesday 19:00 - 21:00

Project Session

Agenda: General standups, updates in main room, then breakout rooms

Guides

Teaching Roles Overview

Role
Topic

As a guide, you find ways to support learners at best. You drive students through the project and strategise with the other teammates to diagnose any issues.

About ReDI

Help

  • Reach out to Caro, your Course Manager, for help via Slack.

❤️ Thank you for supporting the ReDI students ❤️

Are you new to this course:

Start your Onboarding:

Find out more about ReDI:

Find out about the career services ReDI offers:

Check out: , , .

Course Overview
Get Started
About ReDI
Career Services
I can't teach tonight
I am dropping out
I feel uncomfortable
Course Sheet
Google Classroom
Zoom
Attendance Tracker
Course Content
Course Content
Course Sheet
Google Classroom
Zoom Link
Attendance Tracker
Google Drive
Guide

Get Started

Welcome to the Full Stack Circle! 👋

Welcome to our teaching team! We're excited to have you join us in supporting ReDI students on their journey in tech. The Full Stack Circle is a 14-week journey where students build realistic projects while learning modern web development skills.

As a teacher, your first step is to complete the self-onboarding process:

This hub contains everything you need to start and support your teaching journey. If you have any questions along the way, don't hesitate to contact our team on Slack.

Explore the to learn more about the course

Check out the

Review and get onboarded in the

Check out the

Complete your onboarding in

Ready to begin? Head over to the section!

Course Overview
Timeline
Essential Tools
Content Introduction
Complete your self-onboarding
Course Overview

Course Overview

Welcome to ReDI School! We really appreciate that you are part of our community. In this page, you'll find an overview of the course. By volunteering, you contribute to our main goal: help our students gain the necessary skills to find a job in tech. ReDI School has now helped over 17.000 people advance their tech skills. This is only possible with the support of our volunteers <3

ReDI Students

Our student community brings together people from over 138 countries. Your course won't be different. Your students will come from a wide range of countries. They also come from diverse professional backgrounds - some are currently unemployed or underemployed, while others are students looking to prepare for their careers. With an average age of 32, many of our students hold a university degree and have several years of work experience. What unites all students is their passion for technology and their aim to build a career in the tech industry.

About the Circle

The Full Stack Circle is a 14-week advanced program designed for students with solid HTML, CSS, JavaScript, and basic React skills who want to gain development experience by working on team-based projects. Each cohort consists of 25 students who collaborate in small teams to build a full-stack application, simulating a professional software development environment.

Course Purpose & Philosophy

  • Primary goal: Employability through hands-on experience

  • Focus on real-world project work rather than traditional lectures

  • Emphasis on production-quality code and team experience

  • Encourages self-learning and independent problem-solving

Course Structure

  • One main project for the entire semester

  • The class operates like a development team

  • Students are divided into feature teams

  • 3-week sprint cycles

  • Gradual transition from teacher-led to student-led project organization

Curriculum Goals

  1. Soft Skills: Teamwork, Task management, Project communication, Self-learning

  2. Technical Skills: React, Frontend/Backend development, Testing, Git, Clean code practices, Debugging, Documentation

Projects

The students choose at the beginning of the semester a platform they like to clone. The previous project was an AirBnb Clone.

Semester Outline

  • Weeks 1 - 3: Tools configuration, development environment setup, project management process overview

  • Remaining weeks: Split into 3-week sprints. Each sprint contains a focus topic according to the project type that needs to be completed. Milestones will break down the project into smaller deliverables. Expect weekly homework (project work) during this period.

  • Demo Day: At the end of the semester, each team will present their projects to the audience of ReDI course community members.

Sprint Outline

Sprint Phase
Duration
Key Activities

Sprint Kickoff

Day 1

Sprint Planning, Refinement, Work Time

Sprint

Weeks 1-3

Standups, Work Time, Optional Lessons

Sprint Conclusion

Week 3 Day 2

Demo, Retrospective, Next Sprint Brainstorming

Activities Description

Work Time
  • This is where the students are working on their projects in class and the teachers are available to help.

  • We can encourage them to be investigating their tickets so that they can already start finding any unknowns that we can instruct them on, or to inform us what the next lesson should be about.

  • Pair with students, answer their questions

  • We do code reviews, look at their work, and see how we can be helping them improve as mentors.

  • Prepare the upcoming tickets for the next classes.

Standup

The PM of each team walks them through standup:

  • Check the status of the tasks on the board: Any updates, anything blocked or anyone need help?

  • Keep it brief - standups are about exchanging important information and connecting with people who can solve your problems, not about solving them there or showing off.

Refinement
  • The teachers will already have prepared the relevant tickets for the rest of the week.

  • In refinement, you take your team through them and ask the questions: “Is the User Story + Acceptance Criteria clear? Is the task too large to accomplish? Is the task blocked / do you need more info before you could start on it?”. Refine the tasks to the point where the team feels comfortable taking them and working on them.

Planning
  • Roughly figuring out who will work on what for the rest of the week. Mainly looking for:

  • Does every student have meaningful work available to them?

  • Will anyone be blocked by others, and can we avoid that?

Demo

Give the students a chance in front of everyone to showcase what they’ve been working on and made, what they’re proud of.

Retro

At the end of every sprint, we’ll have a retrospective where we address two main points:

  • Likes: What did we like (about anything - the tasks, the project, the code, the course, other people?)

  • Wishes: What do we wish for, how could we make things better (about the tasks, or the project, the code, or the course).

Sprint Brainstorming
  • A large gathering of the entire class where everyone is participating in coming up with ideas for what the next sprint projects could be, and finding out who is interested in them (to form which teams).

Lesson

When we see students needing help on a specific topic (or they request a specific one), then the Instructor prepares a short (20m-1h) lesson on the topic. This should be a bit of a lecture with some slides or other visual materials, and ideally some examples and practice code/session for the students. We will record these lessons.

Sessions

Day
Session
Description
Roles

Tuesday 19:00 - 21:00

We meet for two weekly online sessions to support the students work step-by-step on the project. Agenda: General stand ups, updates in main room, then breakout rooms

Thursday 19:00 - 21:00

Agenda: General stand ups, updates in main room, then breakout rooms

Guides

The volunteers (guides) take on the head of basically two roles:

  1. Product Manager: Runs meetings (standups, planning, refinement), Prepares and prioritizes tasks

  2. Mentor: Performs code reviews, Provides one-on-one guidance, Answers student questions

As a guide, you are both a PM and a Mentor within the sessions :)

On-Site Activities

We are organizing on-site activities in our three main locations. Find out more below.

We invite you to four on-site community events throughout the semester if you are located in Berlin and the surrounding. The Onboarding will also take place in person in Berlin. You are more than welcome to join!

We invite you to four on-site community events throughout the semester if you are located in Berlin and surrounding. The Onboarding and Demo Day will also take place in person in Düsseldorf. You are more than welcome to join!

Four in-person sessions are taking place in Hamburg: Onboarding, two regular course sessions, and Demo Day. If you are based in Hamburg, it would be fantastic if you could support the course in one or more of these sessions.

Conclusion

❤️ Thank you for supporting our students as they take another step in their journey! To learn more about ReDI students and our community, visit .

The course has two online sessions per week. For on-site events, check out . The session format differs from what you might have seen before.

We hope that by reading this, you have a better idea of the course and what it means to volunteer at ReDI. Let's explore the now 📅.

About ReDI School
Timeline
On-site Activities
Project Session
Guides
Project Session
Guides

Essential Tools

Here's an overview of the key tools we use for teaching and communication. Please set up these tools now to ensure effective collaboration with your team and students.

Slack

This is our main communication tool, both with teachers and with the students. You'll have access by default to your teaching team channel and the students' channel. Additionally, you can join our community channels in Berlin, NRW, and Hamburg to learn about local events. Please check Slack regularly during the semester and communicate with your teaching team via Slack if you cannot make it to class.

Action


Google Calendar

We use Google Calendar to send semester meeting appointments to teachers and students.

Actions


Zoom

Our online sessions are running on Zoom. We highly recommend installing and updating the Zoom app on your device, as the online version doesn't cover all functionalities. Please note: The class Zoom link is the same for the entire semester.

Actions


Google Classroom

We use Google Classroom to share material with the students and to collect and give feedback to projects and homework.

Actions


Regular Class

Purpose

Weekly class where students learn new concepts and get introduced to their next project milestone.

Session Details

  • When: Thursdays, 19:00 - 21:00

  • Where: Zoom (link in Slack)

Class Structure

  1. Review previous content

  2. Introduce weekly milestone

  3. Present new concepts

  4. Guided practice ("We Do")

  5. Group practice in breakout rooms ("You Do")

More Resources

Open the Email with the Slack invitation from ReDI. .

to your Laptop (and or mobile phone).

Watch the "" video

Done?

Please complete all steps before going to the next section of the self-onboarding. If you face any issues, please reach out to the ReDI team via E-Mail or Slack. Once you are done, let's dive into the .

Team: leads the session and supports

This explains the Session Formats.

Enter ReDI Slack
Download Slack
how to use Google Classroom
✅
Content Introduction
Session Owner
Session Assist
Course Content
Session Owner
Session Assist
VIDEO

Weekly Sessions

Coaching Session
Regular Class
Practice Session with Q&A

Coaching Session

Purpose

Students present their weekly milestone solutions in small groups (4-5 students), receiving feedback and support from coaches.

Session Details

  • When: Wednesdays, 19:00 - 21:00

  • Where: Zoom (link in Slack)

  • Format: Breakout rooms with one coach per group

  • Who: The Coaches run the Coaching Sessions. Read the instructions for the Coach.

Session Flow

  1. Welcome and breakout room setup

  2. Student presentations (15 minutes each)

  3. Break halfway through

  4. Remaining presentations

  5. Extra time for additional support if needed

Per Student

  • 5 minutes: Project presentation

  • 10 minutes: Feedback and support

Final Project Session

For the last session of each project, students present their complete project instead of weekly milestones.

Resources:

This explains the Session Formats.

VIDEO

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. 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.

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

Google Classroom
Slide deck
Student Hub - Gitbook
Student Hub
Student Hub - Gitbook
Student Hub
Logo