Team Management!

[DanL]

Our team this year split up into different groups - programming, electrical, cad, construction, etc. Needless to say, that method doesn't work. The problem is that some people don't do things during all the stages of the robot. For example, during the first few weeks, us programmers did nothing. Only once we got everything organized did we start going - before, we had nothing to work with.

What I want to do next year is to begin the season analyzing the game and deciding what kind of robot we want to build. Once we do that, I'd like to try to organize the groups based on different robot components rather than on skills. Seems kinda like what AmyBeth is talking about. The main advantage as I see it: everyone is working on something that has a definate goal all the time instead of just doing their 'job' when they're needed.

Any teams have expierience on the the skill vs. component group organization? I'd like to hear how it's worked for others.