Go to Post I really think we need to keep our pitchforks sheathed and torches unlit until we here more news and get more details. - IndySam [more]
Home
Go Back   Chief Delphi > FIRST > General Forum
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
  #16   Spotlight this post!  
Unread 04-11-2015, 16:57
Monochron's Avatar
Monochron Monochron is offline
Engineering Mentor
AKA: Brian O'Sullivan
FRC #4561 (TerrorBytes)
Team Role: Engineer
 
Join Date: Feb 2007
Rookie Year: 2002
Location: Research Triangle Park, NC
Posts: 898
Monochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond repute
Re: Pros/Cons for making our Robotics Team selective?

We do not have a selective team, but have discussed it with other teams. If we were to implement requirements they would probably go something like this
  1. After 1st or 2nd meeting give out simple "homework" for all students after each meeting. Something as simple as "you will receive an email from me this week. Respond to that email." You might be surprised how many students won't manage to reply.
    • Each homework should be something basic like that, but should require effort. Something like, research any type of fastener and talk about 3 uses for it to the whole team.
    • Homeworks completed (but not quality) should factor into who you accept. As long as they participate, they are welcome to come and be educated.
  2. Off season attendance higher than 50% of meetings. (It's great to have other extra-curriculars, but students who regularly miss meetings can end up so far behind that they are a detriment to the other students)
  3. Keep track of student participation and work ethic during meetings.
  4. At the start of the season (Aug / Sept.) announce a specific number of students that will be added to the team. This can be flexible in the end, but a hard and fast number makes it clear early.

That probably needs some tweaking but it's a good start. The key for us would be that we aren't barring people based on aptitude or "ability", we are barring them based on attitude and willingness to work as a team. Those are the qualities that can make or break a team. And students without them often negatively effect the whole team.
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 01:31.

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