View Single Post
  #4   Spotlight this post!  
Unread 10-11-2005, 12:08
GaryVoshol's Avatar
GaryVoshol GaryVoshol is offline
Cogito ergo arbitro
no team
 
Join Date: Aug 2005
Rookie Year: 2000
Location: Royal Oak, MI
Posts: 5,757
GaryVoshol has a reputation beyond reputeGaryVoshol has a reputation beyond reputeGaryVoshol has a reputation beyond reputeGaryVoshol has a reputation beyond reputeGaryVoshol has a reputation beyond reputeGaryVoshol has a reputation beyond reputeGaryVoshol has a reputation beyond reputeGaryVoshol has a reputation beyond reputeGaryVoshol has a reputation beyond reputeGaryVoshol has a reputation beyond reputeGaryVoshol has a reputation beyond repute
Re: Getting every member to know everything possible.

Every team member should know something about everything. Obviously, you know the most about what you did the most.

On the technical side, some don't know programming at all, and that's OK. But you should know the key features about your robot - what kind of drive train, gearing, where are the sensors and what do they do, etc. When judges come to the pits for a second look at your team (after the formal interviews), you never know who they will find to talk with.

For project presentation, everyone should be able to answer general questions. Specific questions about a fact in your presentation could be answered by the person who researched it. Judges like to see several people raising their hands or otherwise indicating they know something about the question. No one person should dominate the conversation.