Quote:
Originally Posted by EricVanWyk
I don't know anything about scouting or PDA software.
What I do know is that I never really did any REAL scouting as a student. I was my team's programmer for 2 years, so I was stuck in the pit doing last minute fixes. I thought it was great that I got to skip out on scouting duty. I was forced to do it a few times, which was kinda boring.
As a mentor I had a bit more time, and I did some non-official scouting. This made me realize how much I missed out on as a student. Casual scouting is really fun. It is a series of conversations with really cool people about things that they are really into.
What ever the tool set you come up with does, I hope it encourages long winding conversations about whatever. I therefore propose the following form:
Stand in front of their pit and look confused.
How many seconds until someone on their team initiates a conversation?
Was it a student or a mentor that initiated?
How enthusiastic were they?
How many students join the conversation?
How many students linger behind?
Ask for "the electrical person". Do they redirect you to a specific person, or do they do everything communally?
Stare intently at something weird/unusual on their robot. How many seconds before they begin to tell the story of its creation?
And finally...
You have partnered with them. There are 10 seconds on the clock in the tie-breaking match to win regionals. Your alliance is down by 1 [ringer, ball, tetra, gerbil,...]. Their robot suddenly wigs out, smashes into you, bursts into flame and releases enough magic smoke to fill 30 magic lamps.
Are they cool enough to turn this into a story you will tell your great grand-FIRSTies?
|
We have a PR group whose responsibility is to do what you have just described above.
When you have 50 teams in a regional pit to drivetrain scout (or upwards of 80 at nationals), and no more than a day and a half to see all of them, learning everyone's life story just isn't practical.
The first concern of a scout should be performance.
The scout's job is to gather and evaluate data on a robot's construction and abilities, as well as its performance and that of its drivers on the field. The ability of the team to collaborate with others in a GP manor should of course come into consideration, but only to the extent that affects their ability to work together with alliance partners to win matches.
Our drivetrain scouts (and in fact all members of the team) are allowed and encouraged to walk around the pits, seeing robots and meeting fellow FIRSTers, but only when they're "off the clock". If you have field scouting duty, or if we have a match, or, in this case, you're a drivetrain scout who hasn't yet gathered data on all the teams, you should be doing your duty to the team, not socializing.
I guess what I'm saying is, in scouting, scouts should be scouts first, team ambassadors second.