Radioactive Roaches Team Guide

Welcome to the Radioactive Roaches, a high school robotics team dedicated to fostering creativity, technical skills, and leadership through hands-on robotics projects. This guide outlines how our team operates, how students grow through our Experience Ladder, and how we welcome and support new members. It serves as a roadmap for students, mentors, and parents to ensure a rewarding and organized experience.

Mission and Values

• Mission: Empower students to learn, innovate, and lead in robotics through collaboration and hands-on experience.
• Values: Growth, inclusivity, teamwork, and resilience.
• Team Charter: All members commit to respect, effort, and supporting each other’s growth.

Experience Ladder: Progression and Badges

Every student progresses through the Experience Ladder, a structured path that builds skills and responsibilities: Observer, Learner, Doer, Responsible. Progression is tracked for each student, and achievements are recognized with Dosimeter Badges, styled like dosimeters with increasing "dose counts" to reflect growth.

Levels and Behaviors

Each level has distinct behaviors, mentor engagement strategies, and expectations to encourage growth.

Level	Description	Typical Behaviors	Mentor Engagement
Observer	New to the team, watching and absorbing.	Asks basic questions, follows instructions, observes processes.	Ask: “Does that make sense?” Provide clear explanations, encourage curiosity.
Learner	Actively learning skills, starting to contribute.	Tries tasks with guidance, asks “why” and “how,” begins to suggest ideas.	Ask: “What do you think is next?” Guide through tasks, encourage problem-solving.
Doer	Independently performs tasks, teaches others.	Executes tasks confidently, helps peers, takes initiative on projects.	Ask: “Who are you going to teach that to?” Encourage leadership and peer mentoring.
Responsible	Leads projects, drives team success.	Plans tasks, delegates, ensures project quality, mentors lower levels.	Ask: “What does this project need to really succeed?” Support strategic thinking.

Tracking and Badges

• Tracking: Mentors maintain a shared spreadsheet to log each student’s current level, skills mastered, and contributions. Regular check-ins (monthly or per project milestone) assess progress.
• Dosimeter Badges:
  • Observer: Single bar (low dose, ~10 mSv, green).
  • Learner: Two bars (~50 mSv, yellow).
  • Doer: Three bars (~100 mSv, orange).
  • Responsible: Four bars (~200 mSv, red).
• Badges are awarded at team ceremonies (e.g., Induction Ceremony, end-of-season celebration) to celebrate growth.
• Students may be at different levels across sub-teams (e.g., Learner in Mechanical, Observer in Programming).

Mentor Guidance

• Assess Progress: Use behaviors as a rubric. Discuss with students to set goals for the next level.
• Encourage Growth: Tailor tasks to stretch students just beyond their current level (e.g., pair Observers with Doers for shadowing).
• Celebrate Milestones: Recognize badge awards publicly to motivate the team.

New Member Program

The New Member Program welcomes students and parents, sets expectations, and integrates new members into the team. It aligns with the school year and emphasizes inclusivity, focusing on fit with the team charter rather than aptitude.

Timeline and Key Events

1. Tryouts/Interviews (Early September):

   • Purpose: Introduce the team, assess interest, and determine primary/secondary sub-team placements (e.g., Mechanical, Programming, Strategy, Outreach).
   • Process:
     • Brief interviews with students and parents to discuss goals and commitment.
     • Focus on alignment with team charter (e.g., willingness to learn, teamwork).
     • Not aptitude-based; all interested students are welcome.
     • Collect preferences for sub-teams to guide initial placements.
   • Outcome: Draft sub-team assignments, shared with families.

2. Introduction Faire and Parent Meeting (Mid-September):

   • Purpose: Set expectations, finalize sub-team placements, and build community.
   • Activities:
     • Showcase sub-teams through demos and student presentations.
     • Discuss team rules, schedule, and commitment (e.g., build season intensity).
     • Parents and students sign the Team Rules and Contract (covering behavior, safety, and participation).
     • Allow students to refine sub-team preferences based on Faire exposure.
   • Outcome: Finalized sub-team placements, signed contracts, and engaged families.

3. Orientation Week (Late September):

   • Purpose: Deepen understanding of sub-teams and team culture.
   • Activities:
     • Detailed sub-team demos and hands-on mini-projects (e.g., assemble a simple mechanism, write basic code).
     • Team-building activities to foster bonds.
     • Assign each new member a Buddy/Journeyman (a Doer or Responsible student) for ongoing support.
   • Outcome: New members feel connected and ready to engage as Observers.

4. Monthly Crash Courses (October–December):

   • Purpose: Build skills and confidence through student-led learning.
   • Format: 1-hour sessions on topics like CAD, soldering, scouting, or outreach, developed and taught by Doers/Responsible students.
   • Outcome: Observers gain exposure to diverse skills, preparing them for Learner status.

5. Induction Ceremony (December, Pre-Build Season):

   • Purpose: Celebrate new members’ integration and progression.
   • Activities:
     • Assess Observers for Learner status based on engagement and crash course participation.
     • Award Dosimeter Badges (most new members receive Learner badge).
     • Share team vision for the upcoming build season.
   • Outcome: New members officially join; team ready for build season.

Battle Rhythm

The Battle Rhythm outlines recurring team activities, ensuring structure and progress throughout the year, with heightened intensity during build season (January–March).

Year-Round Activities

• Weekly All-Team Meeting (1–2 hours):
  • Review progress, share sub-team updates, and align on goals.
  • Include design reviews or report-outs to keep everyone informed.
  • Open Q&A for Observers to build understanding.
• Monthly Crash Courses: Continue as described in the New Member Program.
• Sub-Team Meetings: Scheduled by sub-team leads (Responsible students or mentors) for focused work.

Build Season (January–March)

• Kickoff (Early January):
  • Game rules released. All members participate in brainstorming and design review to ideate solutions.
  • Form cross-sub-team groups to analyze rules and propose strategies.
• Prototyping (Weeks 1–2):
  • Entire team contributes to prototyping (e.g., testing mechanisms, coding basic functions).
  • Observers shadow, Learners assist, Doers/Responsible lead.
• Intensified Schedule:
  • First 2 Weeks: All-team meetings/design reviews every other day to iterate designs rapidly.
  • Weeks 3–6: Revert to weekly all-team meetings, with daily sub-team work.
• Project Assignments:
  • Observers: Support prototyping, observe competition robot work.
  • Learners: Work on alternative projects (e.g., practice robots, outreach displays) and document protocols.
  • Doers/Responsible: Build and refine the competition robot.
• Design Reviews: Weekly (or more frequent early on) to critique prototypes, finalize designs, and assign tasks.

Competition Season (March–April)

• Observers/Learners:
  • Assist with scouting (e.g., observing opponent robots, collecting data).
  • Lead cheering and team spirit activities.
• Doers/Responsible:
  • Operate and maintain the competition robot.
  • Mentor Observers/Learners in scouting roles.
• All Members: Participate in pit setup, strategy discussions, and representing the team to judges and visitors.

Team Structure and Sub-Teams

The Radioactive Roaches are organized into sub-teams with clear leadership roles to ensure effective collaboration and project management. The structure includes a Team Captain, Project Owners, sub-team leads, and the buddy system to support all members.

• Team Captain:

  • Role: Serves as the overall student leader, representing the team to mentors, sponsors, and competition officials. The Team Captain coordinates across sub-teams, ensures alignment with the team’s mission, and motivates members.
  • Responsibilities:
    • Chair weekly all-team meetings and report on team progress.
    • Mediate conflicts and foster team unity.
    • Work with mentors to set season goals and track milestones.
    • Deliver team presentations at competitions or outreach events.
  • Selection: Nominated by peers and mentors in October, elected by team vote. Must be a Responsible-level student with cross-sub-team experience.
  • Term: One school year, with option to reapply.

• Project Owners:

  • Role: Lead specific projects or subsystems (e.g., swerve drivetrain, game piece manipulator, scouting app) to ensure timely completion and quality. Each project has one Project Owner who reports to the Team Captain and mentors.
  • Responsibilities:
    • Define project goals, timelines, and tasks in collaboration with sub-teams.
    • Delegate tasks to Doers, Learners, and Observers based on skill levels.
    • Conduct regular check-ins with project team members and report progress at design reviews.
    • Ensure documentation (e.g., CAD files, code, scouting protocols) is complete.
  • Selection: Appointed by mentors and Team Captain at the start of build season (January), based on expertise and leadership (typically Responsible or high-level Doer).
  • Term: Duration of the project (e.g., build season for robot projects, semester for outreach campaigns).

• Sub-Teams:

  • Programming:
    • Role: Write and test code for the robot (e.g., swerve drivetrain control, autonomous routines) using RobotPy.
    • Skills: Python, Git, WPILib, simulation (e.g., Pymunk integration).
    • Tasks: Debug code, develop autonomous paths, integrate sensors (e.g., Limelight).
  • Mechanical:
    • Role: Design and build robot components, like swerve modules or manipulators.
    • Skills: CAD (Fusion 360), machining, assembly, 3D printing.
    • Tasks: Prototype mechanisms, maintain shop tools, fabricate parts.
  • Strategy/Scouting:
    • Role: Analyze game rules, scout opponents, and develop match strategies.
    • Skills: Data analysis, communication, strategic thinking.
    • Tasks: Build scouting apps, collect match data, brief drivers.
  • Outreach:
    • Role: Promote the team through events, sponsorships, and media (e.g., designing Dosimeter Badges).
    • Skills: Graphic design, public speaking, event planning.
    • Tasks: Create team swag, manage social media, organize demos.

• Sub-Team Leadership:

  • Student Leads (Responsible level): Each sub-team has a lead who oversees tasks, mentors lower-level members, and reports to the Team Captain and mentors at all-team meetings.
  • Mentors: Guide sub-teams, assess progression, and ensure safety. Mentors work closely with Project Owners and the Team Captain to align projects with team goals.

• Buddy System:

  • Pairs new members (Observers) with experienced students (Doers or Responsible) for mentorship and integration.
  • Buddies assist during Orientation Week, crash courses, and early build season tasks.

Action for Team:

• Captain Election: Schedule nominations and voting in October, post-Orientation Week, to ensure candidates are familiar with team dynamics.
• Project Owner Assignments: At build season kickoff, mentors and Team Captain assign Project Owners based on game requirements (e.g., one for drivetrain, one for manipulator).
• Communication: Team Captain and Project Owners use a shared platform (e.g., Slack, GitHub, Discord) to coordinate tasks and share updates.

Team Rules and Contract

Team Mission

The Radioactive Roaches empower high school students to learn, innovate, and lead in robotics through collaboration and hands-on experience, inspired by the FIRST Core Values of Discovery, Innovation, Impact, Inclusion, Teamwork, and Fun.

Purpose of this Contract

This contract outlines the expectations for all Radioactive Roaches members—students, parents, and mentors—to ensure a safe, inclusive, and productive season. By signing, you commit to upholding our team’s values and the FIRST ethos, fostering growth through the Experience Ladder, and contributing to our success in FRC competitions.

Team Rules

1. Embrace Discovery and Growth (FIRST Core Value: Discovery):

   • Actively engage in learning, whether as an Observer, Learner, Doer, or Responsible. Ask questions, try new skills (e.g., coding in RobotPy, designing swerve modules), and seek feedback to earn your Dosimeter Badges.
   • Attend crash courses, team meetings, and build season activities to explore robotics and grow your expertise.

2. Contribute with Innovation (FIRST Core Value: Innovation):

   • Bring creative ideas to brainstorming, prototyping, and design reviews. Whether coding an autonomous routine or designing a manipulator, think outside the box to solve challenges.
   • Document your work (e.g., CAD files, code, scouting data) to share knowledge and improve future projects.

3. Make a Positive Impact (FIRST Core Value: Impact):

   • Represent the team with professionalism at competitions, outreach events, and in the community. Your actions reflect the Radioactive Roaches’ commitment to inspiring others through robotics.
   • Support team goals, from building a competition robot to creating outreach displays, to leave a lasting legacy.

4. Foster Inclusion (FIRST Core Value: Inclusion):

   • Treat all teammates, mentors, and competitors with respect, regardless of skill level, background, or role. Everyone’s voice matters, from Observers to the Team Captain.
   • Create a welcoming environment by listening, collaborating, and helping peers (e.g., Buddies mentoring new members).

5. Commit to Teamwork (FIRST Core Value: Teamwork):

   • Work collaboratively within your sub-team (Programming, Mechanical, Strategy/Scouting, Outreach) and across projects led by Project Owners. Communicate clearly and meet deadlines.
   • Support your teammates by sharing skills, cheering at competitions, or assisting with tasks like scouting or pit setup.

6. Prioritize Fun and Safety (FIRST Core Value: Fun):

   • Bring enthusiasm and a positive attitude to all team activities, from crash courses to competition cheering. Robotics is a journey—enjoy it!
   • Follow safety protocols in the shop (e.g., wear safety glasses, handle tools properly) and at competitions to ensure everyone’s well-being.

7. Honor Commitments:

   • Attend scheduled meetings, build season work sessions, and competitions. Communicate absences in advance to the Team Captain or mentors.
   • Fulfill your role’s responsibilities, whether shadowing as an Observer, coding as a Learner, leading as a Doer, or managing projects as a Responsible or Project Owner.

Expectations for Parents

• Support Participation: Ensure your student attends team events and communicates absences. Provide transportation or coordinate with the team as needed.
• Engage with the Team: Attend the Introduction Faire, parent meetings, and build events to stay informed and cheer on the Roaches.
• Reinforce Values: Encourage your student to uphold the FIRST Core Values and team rules, fostering their growth in robotics and leadership.
• Communicate: Reach out to mentors with questions or concerns to support your student’s experience.

Consequences for Non-Compliance

• Minor Infractions (e.g., missing a meeting without notice, minor safety violations):
  • Discussion with mentors and Team Captain to address the issue and set a plan for improvement.
  • Potential pause in progression on the Experience Ladder until resolved.
• Repeated or Serious Infractions (e.g., disrespect, repeated absences, unsafe behavior):
  • Meeting with student, parents, and mentors to review the contract and determine next steps.
  • Possible suspension from team activities or competitions, decided by mentors.
• Focus on Growth: Consequences aim to reinforce the FIRST Core Values and help students realign with team expectations, not to exclude.

Commitment

By signing below, we agree to uphold the Radioactive Roaches Team Rules, embody the FIRST Core Values, and contribute to a successful and fun season.

Student Name: _______________________________
Student Signature: __________________________
Date: ________________

Parent/Guardian Name: _______________________
Parent/Guardian Signature: ___________________
Date: ________________

Mentor Acknowledgment: _______________________
Mentor Signature: ___________________________
Date: ________________

Tracking and Evaluation

• Progression Tracking: Mentors update a shared spreadsheet monthly, noting skills, contributions, and level changes for each student.
• Sample Layout:

| Student Name | Primary Sub-Team | Secondary Sub-Team | Current Level | Skills Mastered | Contributions | Next Goal | Last Check-In | Notes | |