# ReDI Session: Tips & Guidelines ## How to work with the material? You are free to adapt the materials to your teaching style. If you think slides would help explain a concept, feel free to adapt them. If you prefer to explain something differently, go for it. We know the materials are not perfect, and we truly appreciate your input. If something is unclear or could be improved, please help us enhance it. If anything is missing, feel free to add it. Thanks to your contributions, we can continue improving the materials for future courses. [Where can I find the material?](https://redi-school-1.gitbook.io/teacher-hub/platform-tools#slack-bookmarks) *** ## Teaching Sessions & Roles ### Regular Class Live online lectures focused on introducing concepts and guiding students through practical exercises.\ \&#xNAN;*Used across all courses (except Circles). Bootcamps use README.md for milestones.* ### 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") *** #### **Session Owner** Leads the session, introduces concepts, and guides students through exercises. **Before the Session** * Review previous class feedback (Slack Handover Bot) * Review materials and test exercises * Coordinate with the Session Assistant * Share materials with students (ideally 24h in advance) **During the Session** * Join Zoom (Slack/Calendar link) * Claim host - You can find the credentials on top of your channel * Assign co-host to your co-teachers (5 min early) * Recap previous content * Introduce weekly milestone * Present new concepts * Guide practice (*We Do / You Do*) * Lead and record the session **After the Session** * Share feedback in Slack Handover Bot * Highlight follow-ups or challenges * Share After Class Message *** #### **Session Assistant** Supports the session through technical and administrative tasks. **Before the Session** * Coordinate with the Session Owner * Review session content **During the Session** * Join Zoom (Slack/Calendar link) * Claim host - You can find the credentials on top of your channel * Assign co-host to your co-teachers (5 min early) * Monitor questions * Support breakout rooms * Track attendance **After the Session** * Share feedback in Slack Handover Bot *** ### Practice Session / Q\&A Support-focused session for practicing concepts and answering questions. *This session structure is managed for the UXUI Bootcamp course. Other courses can also adopt this structure if applicable* *** #### **Session Owner** Leads the session and supports students with exercises and questions. **Before the Session** * Review recent concepts * Prepare exercises/support material **During the Session** * Join Zoom (Slack/Calendar link) * Claim host - You can find the credentials on top of your channel * Assign co-host to your co-teachers (5 min early) * Facilitate practice * Answer questions * Support project work **After the Session** * Highlight common challenges * Share feedback with the team *** #### **Session Assistant** Supports the session through technical and administrative tasks. **Before the Session** * Coordinate with the Session Owner * Review session content **During the Session** * Join Zoom (Slack/Calendar link) * Claim host * Assign co-host to Session Owner * Start/monitor recording * Monitor questions * Support breakout rooms * Track attendance **After the Session** * Share feedback in Slack Handover Bot *** ### Coaching Session Students present milestone progress. Focus is on feedback, not teaching.\ \&#xNAN;*This session structure is managed for the Bootcamps.* *** #### **Coach** Supports a small group of students by reviewing milestones and guiding progress. Tracker: One of the coaches will be assign to track attendance and stay in the main room. **Before the Session** * Review milestone README.md * Check student progress (Course Sheet) **During the Session (2h)** * Join Zoom (Slack/Calendar link) * Claim host - You can find the credentials on top of your channel * Assign co-host to your co-teachers (5 min early) * Create breakout rooms * For each student/group: * 5 min presentation * 10 min feedback/support * Guide and unblock students * Track progress **After the Session** * Complete handover (Course Sheet) *** #### **Feedback Guidelines** * **Stay positive** * **Be hands-on** * **Guide, don’t solve** ### 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.
*** ### Project Session Team-based session focused on building projects collaboratively. *This session structure is managed for the Circle courses. Other courses can also adopt a similar structure if applicable* #### Class Structure 1. Standup meetings (15 minutes) 2. Work time with active mentoring 3. Optional micro-lectures as needed 4. Team-based project work #### Sprint Cycles (3 weeks) * Sprint planning and kickoff * Regular refinement sessions * Demo presentations * Retrospectives *** #### **Guide** Acts as Product Manager and Mentor. Tracker: One of the guide will be assign to track attendance and stay in the main room if there are break-out rooms. **Before the Session** * Review team progress and priorities **During the Session** * Join Zoom (Slack/Calendar link) * Claim host - You can find the credentials on top of your channel * Assign co-host to your co-teachers (5 min early) **Product Manager:** * Runs team meetings (standups, planning, refinement) * Prepares and prioritizes tasks for sprints **Mentor** * Conducts code reviews * Provides one-on-one support during work sessions * Helps students discover solutions independently * Identifies areas where students may need additional support **After the Session** * Align on next steps * Share updates if needed
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.
*** ### Peer Feedback Session *This session structure is used in Bootcamps when there is a low number of coaches.* Other courses can also adopt this structure if applicable*.* #### Class Structure *** #### Facilitator **Before the Session** * Review milestone expectations * Prepare feedback prompts * (Optional) Set up a Mural board for collaborative feedback **During the Session** * Join Zoom (Slack/Calendar link) * Claim host - You can find the credentials on top of your channel * Assign co-host to your co-teachers (5 min early) * Organize participants into groups * Guide the feedback process * Ensure discussions are constructive and balanced * Encourage participation from all students * Remind students that: * Feedback is meant to support improvement * The project owner decides which changes to implement and prioritize * Use tools like Mural for collaborative input (if applicable) **After the Session** * Highlight key learnings and common insights * Share feedback with the team if needed * Ensure feedback is accessible (e.g., via Mural or shared notes) *** #### **Feedback Guidelines** * **Stay positive**: Balance suggestions with recognition * **Be hands-on**: Provide actionable input * **Guide, don’t solve**: Encourage independent thinking * **Respect ownership**: The project owner makes final decisions and prioritizes changes *** ### Homework / Project Review At ReDI, homework is not mandatory but encouraged. #### Homework/Project Reviewer If you have been assigned homework to review, please provide constructive feedback to support students’ learning and improvement. **Before Reviewing** * Familiarize yourself with the assignment requirements * Understand the expected outcomes and criteria **During Reviewing** * **Be positive**: Highlight what was done well to build confidence and reinforce learning * **Be specific**: Clearly point out which parts of the code need improvement * **Provide suggestions**: Offer guidance on how to improve, without giving away full solutions **After Reviewing** * Ensure your feedback is clear and balanced * Encourage further learning and self-study * Submit feedback on time *** ### Backup Teacher Covers sessions if a teacher is unavailable. *** #### **Backup Teacher** **Before the Session** * Stay informed (Slack #teachers) * Be familiar with content * Ask questions regarding previous sessions if needed **During the Session** * Step in if requested * Take assigned role **After the Session** * Share feedback if involved *** #### **Substitution Process** * Teacher posts in Slack and tags backup * Backup confirms * Assignment: * Assistant absent → Backup = Assistant * Owner absent → Assistant = Owner, Backup = Assistant *** ### Mini Project Demo Some courses present a Mini Project. This is the first small project the students work on. The students present their Mini Project in front of the course. Students present the Mini Project in a dedicated session. You can find the session in your Course Sheet and ideas in your course section if applies. ### Expectations? This is a small project only. Let's focus on what is achievable in this short time frame. #### Class Structure * **Presentations:** Every student or team presents their work * **Format:** Students can present it in a form of their choice. They can use Google Slides, show the code directly or any other format. * **Time:** Each team has 5 minutes to present. * **Q\&A:** After the Presentation, there is 2 min for questions from other students and from the teachers. * **Break:** Let’s take a short break after half the teams went :) **Finish Early?** Depending how fast your presentations are you might finish slightly early - that is okay! #### Session Owner The Owner is guiding the session, has an eye on the watch to not go too much overtime and coordinates who shares when. #### Session Assistants We support the students, share feedback after the presentations. Let’s cheer for the students 🥳 *** ## Tips: Handling Session & Last-Minute Changes #### ⏱️ **If you need to end the session early** * Frame it as a win: *“Great progress today, we’re wrapping up early”* * Leave a clear next step or small task * Open space for final questions *** #### 👥 **If students are disengaged or quiet** * Use breakout rooms to activate participation * Ask them to explain concepts in their own words * Rotate who speaks (avoid always the same voices) *** #### 🧠 **If students don’t understand a concept** * Ask: *“How would you explain this?”* * Let students try first, then correct or clarify * Use simpler examples or real-life analogies *** #### 🗣️ **If you’re talking too much** * Switch to *“You Do”* faster * Let students explore and struggle a bit * Guide instead of explaining everything *** #### ⚡ **If the energy is low** * Add a quick break (2–5 min) * Use interactive questions or quick challenges * Change format (discussion → activity) *** #### 🧑‍💻 **If there are technical issues** * Have a backup plan (slides, examples, discussion) * Ask students to help each other in breakout rooms * Don’t block the whole class — keep momentum *** #### 🧩 **If students are at very different levels** * Use breakout rooms to group by pace * Give optional “extra challenges” for advanced students * Focus on minimum understanding for everyone *** #### ❓ **If no one asks questions** * Ask specific questions instead of open ones\ (*“What was confusing about X?”*) * Use chat instead of voice * Normalize confusion: *“It’s okay if this is not clear yet”* *** #### 📉 **If students fall behind** * Focus on key concepts, not everything * Share resources for later review * Encourage peer support *** #### 🤝 **If collaboration is weak** * Assign roles in breakout rooms (driver, reviewer, speaker) * Ask groups to present back * Encourage explaining, not just solving *** #### 🎯 **General Tip** * **Less teaching, more learning** * Students learn more when they **do, explain, and struggle a bit** *** ### Best Practices #### Supporting Students * Encourage self-learning * Guide rather than provide direct solutions * Foster team collaboration * Maintain consistent communication #### Project Management * Help break down tasks into manageable pieces * Ensure clear acceptance criteria * Monitor progress and address blockers * Facilitate effective team discussions ### 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 teachers/coaches *** #### Read More: * [How to use Zoom?](https://redi-school-1.gitbook.io/teacher-hub/platform-tools#zoom) * [How to Track Attendance?](https://redi-school-1.gitbook.io/teacher-hub/platform-tools#attendance-tracker) * [How to get access to the tools? (Credentials)](https://redi-school-1.gitbook.io/teacher-hub/platform-tools#slack-bookmarks) * [How to get access to the material?](https://redi-school-1.gitbook.io/teacher-hub/platform-tools#slack-bookmarks)