|
Re: REQUEST - Are you a Multi-School Team?
* Team Name / Number: 710 PAW
* Team Location: Coral Springs/Ft.Lauderdale area
* How many student team members: well,at regionals about 30 or so...i think
* How many schools:4
* Breakdown - how many students from each of the schools (generally): Well from North Broward (my school) we have about 3 or 4, From Coral springs Christian we have 4, and i'm not sure between WA and Pinecrest, but im gonna say about 10 from each.
* How do you organize your team with multiple schools: This year my old team, 267 (NBPS&CSCA), was unable to find the money and resources to stand on its own so we joined up with 710(WA&PC). While the actual build season organization is excellent, the team's communication is not so good, so I will take examples of 267 as it was run in previous years. We created a mailing list so that we could email one address and get it to the entire team. With this mailing list, every piece of information was given through email, and we knew exactly what to do if we had questions. As far as meetings, we lived relatively close to each other and could therefore find a good meeting place somewhere between the two schools. This year the kids from my team live a good 45 minutes away from the other schools, but have to meet there because that's where the machine shop is. It takes a lot of gas money, but we deal with it.
* What are pros / cons you have seen given your arrangement: Pros- two teams/four schools with dwindling resources are able to still participate. There are many people with many different ideas. Cons- Location. Make sure your schools are close together!
* Do you have any advice to other teams who may want to do something similar: For years my old team 267 has had no problem with joining the two schools into one team, as far as school spirit and animosity goes... we always considered ourselves '267' rather than NBPS or CSCA. This year, when we joined teams with 710, it was hard at first to assimilate for several reasons (we were all really good friends in our little group, and 267 mainly made up the software team, and had basically noone not on 267 on software, so there wasnt even any building time to bond with other members) but eventually it all worked out well. Make sure you get everyone involved, assimilate everybody, create some form of quick and easy communication, and be sure you tell everyone when the meetings are!! (slight problem this year, but we get around it)
|