Hi, I'm the "lead engineer" on team 1317 this year. Although it is a rookie team, I have been on many other FIRST teams over the past six years. From that experience, I have drafted a "Team 1317 Standard Operating Procedures" document. It includes our team organization, as well as bunch of other useful stuff. You might want to take a look at it:
http://www.osufirst.org/twiki/pub/OS...dureManual.doc
Two points that I want to highlight: about the comment about not having any team structure, that's a bad idea. You need team structure, the key is to sure that is an effective structure, not an ineffective structure. A committee of six people rarely gets anything accomplished. Democracy sounds great in principle, but it is very inefficient. A dictatorship or oligarchy approach is usually best for FIRST as it is more efficient. Put one or two people in charge and let them have final say over everything. Then, have a nice hierarchy under them.
Second point: although this depends upon the style of frame (or "chassis") and drivetrain that your team uses, I have found that making separate frame and drivetrain groups is usually not the best idea. Combining them into one group works much better for us.