[Ryan Caldwell]

last year our drive team was:
Driver: Junior Designer
Co-Driver: Senior Electrical Lead
HP: Sophomore Strategy/Scouting Lead
Coach: Junior Programmer
Driver alt: Sophomore Programmer
Co-driver alt: Freshman Build Team

We base who drives primarily on a written rules test that is timed and observed. We want drive team that knows the rules not a drive team that needs to think about the rules. We also test drivers with the robot and hp with their tasks. The coach is more or less subjected to a psych evaluation to see how they will interact with other coach's and how well they can orate commands and make snap decisions. The coach must also be able to complete a task without getting tunnel vision to the task.

Our drive team are typically the "die hard" students whom have the most hours in at the build site as well.

Evaluation and testing have given us good/unbiased results for picking a drive team over the past 5 years. Once together its important to practice, practice, practice. we also make the drive team sit/eat/ride together at team functions so that they get familiar with each other.