| | 1 | = Team Structure 2015-2016 Season = |
| | 2 | |
| | 3 | {{{ |
| | 4 | #!div style="border:dashed;color:blue" |
| | 5 | '''Special Comments''' |
| | 6 | |
| | 7 | }}} |
| | 8 | |
| | 9 | |
| | 10 | == Team Captain == |
| | 11 | - Interact with mentors and faculty advisor daily. Understand mentor direction and translate to the students |
| | 12 | - Overall coordination and communication across all the captains (including business and outreach). You are leading the captains, not their teams |
| | 13 | - Ensures all members of the team are engaged in meaningful roles |
| | 14 | - Make sure an overall SCHEDULE is understood and all milestones are achieved by working with the various teams |
| | 15 | - Main POC for communicating team issues, concerns, ideas to the mentors |
| | 16 | - Lead daily standups during build season |
| | 17 | - Coordinate and resolve issues between Strategy, Integration and Hardware leads |
| | 18 | - Bring inter-‐student or inter-‐mentor disagreements to the attention of the faculty advisor for resolution |
| | 19 | |
| | 20 | |
| | 21 | == Game Captain == |
| | 22 | Beginning of Build Season |
| | 23 | - Coordinate with Captains and Strategy Team to translate rules into design requirements |
| | 24 | - Set team strategy for scoring (and platform attributes) based on game rules and our scoring strategy |
| | 25 | - Know things: (Know these at competitions too) |
| | 26 | - Know the Rules |
| | 27 | - Know the competition: venue, game dynamic, judges and referees |
| | 28 | - Know the Opponents: other teams, other designs |
| | 29 | During Build Season |
| | 30 | - Train the drive team on our likely strategies. Run driving drills designed to simulate game-‐time situations. |
| | 31 | - Work with mentors and faculty advisor to determine the best drive team for executing competition strategy |
| | 32 | - Interact with other captains (constantly) |
| | 33 | - Communicate with adults |
| | 34 | - Coordinate system design goals/issues/details |
| | 35 | - Interact with strategy and outreach teams (daily) |
| | 36 | - Understand needs/goals/status of both teams |
| | 37 | - Coach, inspire, communicate w/ each team daily |
| | 38 | - Make a weekly plan with Strategy and Outreach “groups” |
| | 39 | - Backstop your team leads |
| | 40 | During Competitions |
| | 41 | - At competitions ensure that our entire team understands game strategy, especially when we make adjustments during the regional. This is critically important once we are selected for an alliance as our strategy may change significantly |
| | 42 | - Execute scouting strategy at the game |
| | 43 | - Lead debriefs after each match during the competition |
| | 44 | - Build relationships with other teams at competitions to build potential alliance relationships |
| | 45 | |
| | 46 | |
| | 47 | == Operations Captain == |
| | 48 | - Define, prioritize, and oversee execution of team marketing, business and outreach activities (all non-robot building activities). These include: |
| | 49 | - Team Media presence: Website content, YouTube, Facebook, newsletters |
| | 50 | - Fundraising, sponsor contact (former, existing, new) and relationships |
| | 51 | - Outreach activities- STEM Fairs, other FIRST teams, etc |
| | 52 | - Awards writeups |
| | 53 | - Marketing and Promotional items |
| | 54 | - Team branding standards |
| | 55 | - Ensure that entire team understands these activities, knows who sponsors are, knows teams that we mentor, etc. |
| | 56 | - Work closely with mentors and Tech Boosters to determine student roles and responsibilities and Boosters/parent roles and responsibilities in these areas. Actual activities dependent on this Division of Effort and staffing levels of overall Operations team. Keep the communication going to ensure nothing is dropped. |
| | 57 | - Work with subteam leads to identify each subteam’s tasks, schedules, milestones, deadlines and priorities |
| | 58 | - Create an overall schedule for all activities and ensure milestones and deadlines are met. |
| | 59 | - Support subteam leads as needed to ensure staffing levels are appropriate, all actions are tasked, and deadlines are met |
| | 60 | - Coordinate across subteams to address cross-subteam integration needed |
| | 61 | - Oversee authoring of team submissions for awards (Chairman’s, etc.) |
| | 62 | - Train and staff ambassadors for competitions |
| | 63 | - Coordinate with other captains on overall team staffing, training, planning |
| | 64 | - Manage Team Facebook page to include monitoring content and page membership (inviting members to join, approving requests to join, etc.) in a timely manner. |
| | 65 | - Provide logistical support to team admin/Tech Boosters as requested. |
| | 66 | - Backstop subteam leads |
| | 67 | |
| | 68 | |
| | 69 | == Integration Captain == |
| | 70 | - Implement risk matrix and mitigation strategy for software and electrical |
| | 71 | - Ensure close coordination between electrical and software teams |
| | 72 | - Work with hardware captain to determine required number of sensors, positions, states, etc. |
| | 73 | - Educate hardware captain and mechanism leads on how to produce electrical and software requirements specifications for their respective areas |
| | 74 | - In coordination with the Hardware Captain, run the initial integration and overall platform design meetings. |
| | 75 | - Create pit area checklists for electrical, software and drive station. |
| | 76 | - Interact with other captains (constantly) |
| | 77 | - Coordinate system design goals/issues/detail |
| | 78 | - Interact with electrical and software teams (daily) |
| | 79 | - Understand needs/goals/status of both teams |
| | 80 | - Coach, inspire, communicate w/ each team daily |
| | 81 | - Communicate with adults |
| | 82 | - Know things: |
| | 83 | - where things are, who’s doing what, why they are doing it, what needs to happen next |
| | 84 | - Make a weekly plan for integration “group” that aligns with the master schedule |
| | 85 | - Backstop your team leads |
| | 86 | - Provide realistic estimates of schedule/milestone completion for the electrical and software teams to other teams |
| | 87 | |
| | 88 | |
| | 89 | == Hardware Captain == |
| | 90 | - Implement risk matrix and mitigation strategy for mechanical and drive components |
| | 91 | - In coordination with the Integration Captain, run the initial integration and overall platform design meetings |
| | 92 | - Determine hardware requirements for sensors, software, etc. |
| | 93 | - Create pit area checklists for all mechanical components |
| | 94 | - Interact with other captains (constantly) |
| | 95 | - Coordinate system design goals/issues/details |
| | 96 | - Interact with mechanism teams (daily) |
| | 97 | - Understand needs/goals/status mechanism teams |
| | 98 | - Coach, inspire, communicate w/ mechanism teams daily |
| | 99 | - Communicate with adults |
| | 100 | - Know things: |
| | 101 | - where things are, who’s doing what, why they are doing it, what needs to happen next |
| | 102 | - Make a weekly plan for hardware “group” that aligns with the master schedule |
| | 103 | - Resolve issues between mechanical groups (e.g., room on the platform, etc) |
| | 104 | - Backstop your team leads |
| | 105 | - Provide realistic estimates of schedule/milestone completion for the mechanical/drive teams to other teams |
| | 106 | - Coordinate the pit area during competitions |
| | 107 | |
| | 108 | |
| | 109 | == Strategy Lead == |
| | 110 | - Prior to build season scout out teams that we will be facing in our respective regional competitions and build a dossier on each team. This dossier should include any past wins, strategies, history of teaming with RAID, etc. Update these dossiers during the build season based on open source information found on team sites, youtube, etc. |
| | 111 | - Shred game rules and devise compliance matrix |
| | 112 | - Devise our intended “scoring” strategy |
| | 113 | - Validate all designs (software, hardware) against game strategy |
| | 114 | |
| | 115 | |
| | 116 | == Mechanism Lead (several), Electrical Lead, Control Systems Lead, Drivetrain Lead, !Field/Pit Lead == |
| | 117 | - For your respective area, create a design that is compliant with our game strategy and overall platform design |
| | 118 | - Ensure your team understands their assignments and have meaningful work to perform AT ALL TIMES |
| | 119 | - Devise a strategy for mentoring newer team members |
| | 120 | - Meet & beat schedules |
| | 121 | - Interact with other team leads to better understand progress, strategy and design |
| | 122 | - Keep track of team members participation |
| | 123 | |
| | 124 | |
| | 125 | Outreach Lead |
| | 126 | |
| | 127 | Identify elementary and middle school teams that we can mentor. |
| | 128 | Coordinate team mentoring of elementary and middle school teams. |
| | 129 | Work with mentors to coordinate team participation in community outreach events (e.g.STEM Fairs, Girl Power, Homecoming Parade, etc.) |
| | 130 | Plan and organize student and robot participation in external activities as needed |
| | 131 | Expand the FIRST culture across AHS- link with other student clubs, etc to bring special expertise (video, photography, graphics, business) expertise into the team. |
| | 132 | Draft Chairman’s award input - work with other Operations subteam leads to produce video |
| | 133 | Define and track schedules, milestones, deadlines of all activities and ensure these are met. |
| | 134 | |
| | 135 | Marketing Lead |
| | 136 | |
| | 137 | Define content for team website and work with software team to keep website updated |
| | 138 | Work with Tech Boosters and parent volunteers to plan graphics, buttons, shirts, promotional materials etc. |
| | 139 | Oversee the creation of team marketing materials- newsletters, videos, etc. Define content, task out articles, help write scripts,, put together finished product |
| | 140 | Define and track schedules, milestones, deadlines of all activities and ensure these are met. |
| | 141 | |
| | 142 | Business Lead |
| | 143 | |
| | 144 | Work with the mentors and Tech Boosters to help plan and execute a strategy for team fundraising. |
| | 145 | Categorize team budget for grants and award purposes |
| | 146 | Represent funding needs to potential sponsors |
| | 147 | Identify potential grant opportunities, support drafting of grants |
| | 148 | Reach out to former, current and potential new sponsors for additional team support |
| | 149 | Communicate with sponsors regularly to keep them informed of team activities |
| | 150 | Draft/Update Business Plan and Entreprenuership Award Writeup |
| | 151 | Define and track schedules, milestones, deadlines of all activities and ensure these are met. |
| | 152 | |
| | 153 | CAD Lead |
| | 154 | |
| | 155 | Provide CAD designs that assist the mechanical leads in designing their components |
| | 156 | Manufacture “rapid prototyping parts” as required |
| | 157 | Develop drawings of key features to explain the robot to judges at competition |
| | 158 | |
| | 159 | Senior Mechanical Lead |
| | 160 | |
| | 161 | Interface with Hardware Captain, sub-‐team leads, and mentors |
| | 162 | Support all mechanical teams as required or directed |
| | 163 | Provide guidance and mentorship to less experienced sub-‐team leads |
| | 164 | Be responsible for: |
| | 165 | Special projects |
| | 166 | Critical parts |
| | 167 | Rapid prototypes |
| | 168 | Be able to work independently while meeting deadlines |
| | 169 | Significant time requirement for this position |
