Large amount of team members.

[cadandcookies]

Originally Posted by Or 2230

Hello there FIRST community
Recently, our team, that traditionally had 30-40 members, has faced a new problem: 40 new students signed up to our team, which makes us a team of 70 students.
Our team never had any process of deciding which students can join our team and which can't, because of the fact that we believe that everyone who wants to join FIRST should have the opportunity to do so.
What do you guys do in your teams? Do you sort the students or do you have a team structure which is capable of having this amount of students?

Good luck.

Before the 2011 FRC season, 2220 had almost precisely the same thing happen-- and then continue happening until now. Explosive growth is a marvelous thing.

In my experience, the number one thing that keeps momentum going on growth is keeping everybody busy. Offseason projects, a second robot, lots of different prototypes, focusing on training and CAD, and capitalizing on individual students' interests are all things that feed into that. If you use your excess human resources wisely, you can get more sponsors, start a lot of FLL, FTC, or VRC teams in your area, and raise awareness for FIRST and STEM programs massively.

Brainstorm different activities and projects that your team can do to keep people busy. Think about the size you want your build team to be, think about whether you want to build two robots, split up what might have been a "robot manufacture" group into "drive train," "manipulator," and "electrical" groups, etc. Figure out what all your new people (and current people) are interested in doing, and then reevaluate-- an excess of electrical might mean exploring doing some fancy lights on the competition robot, or focusing on making very neat wiring this year.

Team 2220 ended up iterating through a series of stuctures-- in 2012, we tried having a bunch of internally competitive groups working on our manipulator. This was not particularly effective and resulted in a lot of friction, so we had to emphasize logical prototyping and CAD in order to keep everyone interested and functional. We also started focusing on tight project management-- when you have so many people, there are no excuses for not meeting your deadlines. We also now do a lot of off-season engineering competitions (internally), and funnel new students in 7-10th grade into our FTC program, which has grown from 1 team in 2012 to 16 this season.

If you have any questions about that, feel free to PM me and I'll put you in touch with some of the mentors on the team (they have a bit of a different perspective; I was a student during that time).

Again, good luck. A large program is both a gift and a curse.

[DonRotolo]

Hm. We also had 45 new members sign up this year, but since we already have 60, we're kinda used to it. Lotsa mentors helps.

We have mandatory service hours before build season, I think it's 20 if you want to stay on the team. These include shop cleanup, carwash, parades, community outreach and other activities.

[Edxu]

My team had 20-ish people apply this year, and we're already a team of 30. We try to keep our team size around 40-45, which is a manageable size for traveling and fits our lab size.

As such, we had to cut 5-10 people.

Basically, we try to put almost all of the Grade 9's (Freshmen??) and older members on the team as a tryout to see how they do from the fall-winter pre-season, and then make cuts based on how much dedication they showed during that time.

[Monochron]

Originally Posted by Edxu

My team had 20-ish people apply this year, and we're already a team of 30. We try to keep our team size around 40-45, which is a manageable size for traveling and fits our lab size.

As such, we had to cut 5-10 people.

Basically, we try to put almost all of the Grade 9's (Freshmen??) and older members on the team as a tryout to see how they do from the fall-winter pre-season, and then make cuts based on how much dedication they showed during that time.

I'm interested to know how you execute that. How do you tell the students they have been cut? How do they usually take being cut from a team after putting in work in the pre-season? Do they often return to the team?

[Edxu]

Originally Posted by Monochron

I'm interested to know how you execute that. How do you tell the students they have been cut? How do they usually take being cut from a team after putting in work in the pre-season? Do they often return to the team?

From my experience as a student, there were very few "grey areas" in terms of student participation, with the cut students not participating or showing interest and the ones who made it show a genuine interest in the team. This means that there are very few students who put in the time and work in the pre-season that get cut.

Our school has a technologies program, that includes robotics, that all of the Grade 9 students go through each year, and if students are cut, that is another chance for them to show their interest, and they can apply for consideration again in Grade 10, where they often work harder and make the team roster.

[seg9585]

We ran into this problem last year, we had 85 students start out the year! The school does not permit capping the club, but eventually the training sessions in the Fall starting whittling down the participation to just the students who were serious about joining.
With only a few mentors, it made things initially difficult for sure!

This year, we are implementing a Club + Competitive Team 4276 system, where students interested "casually" in robotics (or have too many conflicting sports or other activities) can join the club and participate in team activities to learn and tinker, or help with non-build activities, but only Team members who have gone through proper safety and technical training/practice in the Fall can participate in the "Competitive Team" builds.

The club meets during lunch and sometimes after school, the Team participates in late afternoon or evening Training followed by the typical build season schedule in Jan-Feb.

[Sohaib]

This year we have nearly 60 members on our team, a huge jump from our 25 in our first season. We're starting three VEX Robotics teams this year in order to keep everyone involved, wherein each VEX team is also to have sub-teams.

For the FRC, were going to look to work in tightly knit teams, and the more people we have on hand, the better - ie for Awards, Programming, Build.

Each VEX Team is going to have separate meetings as well.