|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: Team officers
I'm not currently in Australia, but I will say that Sydney is the best city in the world
And Melbourne has (I believe) the highest concentration of biomedical firms in the world. So look out for the Down Under teams to really grow FIRST and STEM |
|
#2
|
||||
|
||||
|
Re: Team officers
FRC 422 Officer Structure
Team Leader: ●Main officer during off-season, ●Leads team meetings (not build sessions) ●Facilitating decision making process equitably to completion ●Coordination and planning with parent/faculty sponsors and mentors ●Helping Admin and Outreach with Chairman’s Award Mechanical and Design: ●Building mechanical aspects of the robot ●Technical drawings ●Co-leading build sessions ●Resources and Bill of Materials (work with Admin and Electrical/Programming) Electrical and Programming: ●Designing/building electronics board ●Programming the robot ●Co-leading build sessions ●Resources and Bill of Materials (work with Mechanical and Admin), Administrations and Communications: ●Intra-team communications, ●Safety, ●Attendance, ●Internal school relations, ●Resources and Bill of Materials (work with Mechanical and Electrical/Programming), ●Chairman’s Outreach and Public Relations: ●Maintain written communication with sponsors. ●Facilitate development of sponsorship presentations ●Inter-team communications ●Organizing team community service events ●Chairman’s In this system, the five team captains, elected by the membership, take on a share of the listed responsibilities. Each captain is allowed to appoint any number of subteam leaders in order to accomplish all responsibilities listed in each category, and may commission subteams or focus groups for anything they see fit. It is suggested that returning members participate in a minimum of two subteams, preferably across different disciplines, while new members should participate in a minimum of one. |
|
#3
|
|||||
|
|||||
|
Re: Team officers
This year, we've had the president, vice president, electrical head, mechanical head, IT head, and business head. We do something weird with the president, where we elect someone as vice president, and the next year the vice president becomes president. In theory, this teaches the vice president what has to be done as president.
|
|
#4
|
||||
|
||||
|
Re: Team officers
We have a fairly small team compared to many, and we elected two general captains this year to oversee cooperation between groups and help lead the team meetings. Inside each subgroup (programming, chassis, manipulator, electronics, etc), a group leader was appointed based on experience, and was designated to teach the other members of the group how to perform the tasks assigned to the group. We didn't have a very strict organizational structure, and there was a lot of merging between groups to get things done, but hey, we made it to Championships! While strict organization is good in theory, we've discovered it to be difficult to carry out throughout the season. The best advice I've seen is if something isn't working, don't be afraid to fix it. What works on paper often doesn't in real life.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|