Go to Post I personally think that everybody on the team is important. No matter what, every single student, mentor, teacher put their effort all year long to get the team going. So in my opinion, Credit goes to everyone. - Arefin Bari [more]
Home
Go Back   Chief Delphi > Other > Chit-Chat
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
 
 
Thread Tools Rate Thread Display Modes
Prev Previous Post   Next Post Next
  #1   Spotlight this post!  
Unread 25-07-2015, 00:10
GeeTwo's Avatar
GeeTwo GeeTwo is online now
Technical Director
AKA: Gus Michel II
FRC #3946 (Tiger Robotics)
Team Role: Mentor
 
Join Date: Jan 2014
Rookie Year: 2013
Location: Slidell, LA
Posts: 3,508
GeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond repute
FIRST world problems

Sometimes, a team is so successful at some aspect of its operations that it runs into "problems" that most teams would love to have. Even more than with most problems, "FIRST world problems" are best viewed as an opportunity. What "FIRST world problems" have you turned to an advantage, and how?

Here's our story: Team 3946 did a bit of a PR blitz prior to Bayou 2014 (Aerial Assist). As a result, several teachers had the webcast of Bayou on during class on Friday. During the fall of 2014, we brought our t-shirt and mini-football launching air cannon onto the running track during several football games; we flew the robotics banner (which is intentionally aligned with the other school teams' colors and names; even our Navy JROTC has "Tiger Navy" on their PT uniforms). In late 2014, we realized that we had more people interested in joining robotics than our facilities could possibly handle (80 vs 40-50). We decided to hold "tryouts" to whittle the numbers down to about 50. We set up tryouts that looked like aptitude tests in programming, numerical drawing, cutting pieces, writing directions, and a number of other tasks. We graded students both on aptitude/ability and on attitude. We selected members based on attitude and asigned them to departments based on aptitude (with expressed preferences considered). OH WHAT A DIFFERENCE! The 2015 team was about the same size as the 2014 team, but the attitude was incredibly different. I originally approached "tryouts" as a way to prevent overcrowding, but one week after tryouts were over, I hope we never have to go back to a "take everyone" condition again.
__________________

If you can't find time to do it right, how are you going to find time to do it over?
If you don't pass it on, it never happened.
Robots are great, but inspiration is the reason we're here.
Friends don't let friends use master links.

Last edited by GeeTwo : 25-07-2015 at 00:12.
Reply With Quote
 


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 11:56.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi