Versions Compared

Old Version 1

changes.mady.by.user Austin Tailon Huang

Saved on

compared with

New Version Current

changes.mady.by.user Austin Tailon Huang

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Responsible for scoping out projects specific to their subteam

    • Overall scope, deliverables, deadlines, etc

  • Manage/mentor younger students to successfully complete technical projects

  • Run subteam meetings to get a sense of progression

  • Communicate subteam progress to other subteams

  • Allocate personnel within your subteam to meet and succeed with different projects

  • Ensure tasks completed by subteam members are properly documented

  • Ensure subteam is set up for upcoming term (month in advance, replace yourself and key members who are leaving)

  • Meet with subteam members at end of term to determine their plans following coop

  • No adjacent responsibilities!!

...

Project Based Team Structure

...

Expand
titleComms Subteam

  • ME Subteam Member (1+ Term of Experience):

    • Responsible for design of mechanical base station

    • Responsible for rover comms design

  • EE Subteam Member 1 (0+ Terms of Experience):

    • Assist and learn from EE subteam Member 1

  • EE Subteam Member 2 (2+ Terms of Experience, Grad Student preferred):

    • Comms lead → own the system

    • Responsible for leading comms on the EE side

    • Good understanding of RF

    • Understand how the bands work, why we have 3, how to select bands

    • How to improve them? Weak points in signal

  • SW Subteam Member 1 (1+ Term of Experience):

    • Responsible for ensuring jetson can properly interface with comms; run and verify comms system on ROS side

This group would meet up once a week on top of weekly team meetings (~30 min) to discuss direction of the comms station and make sure everything works

  • List of Subteams:

    • Comms

    • Autonomy/Localization

    • Gimbal/Vision/Localization

    • Simulation Team (Maybe)

    • ROS Integration Team

    • Arm

    • Power Distribution Team (Battery/Ebox/EE work)

    • Drivetrain

    • Science

    • Controller Team

...

Protocol for Retiring Leads

  • This applies to anyone who has been an in-person lead for a term and goes on co-op, OR is going into 4th year, OR wants to step down

  • Please note - the point of this idea is not to trap people, it’s to reinvest in your teammates and pay forward what you have learned through your experience

  • If you are stepping away from a lead role, please stay on as a team advisor for at least 1 term

  • What is a team advisor, how much responsibility do I have?

  • Make yourself available once a week to existing team leads so they can ask for advice or suggestions on how to solve problems they are faced with

  • You are NOT responsible for the outcome, just give people advice based off of your previous experiences!

  • If you are interested doing more, participating in design reviews would also be fantastic, or hosting small tutorials on various topics of interested (i.e. altium tutorials, etc.)