sub-team tension???

[Marcel]

Usually we put our ideas together and come up with what we want before we start building, programming or anything. So we've never had aqny problems, of course this year we had a small problem, when some of us wanted to shoot to the top, others to the bottom, and some hybrid. We ended up working from the bottom to the top. So now we have a great shooter and a pretty sweet design for the chassis. But after that no real problems.

[Freak999]

We dont have much tension with our teams our progamming team uses past robot to program the drive-train. One problem that we've had in the past is that the drive team does not get enough time to practice with the robot because the robot does not get compleated in time to practice before the ship date.

[paulcd2000]

OOOOOOOOOHHHH yes. we on the prog team have waited a whole week for the electrical team to finish the bot, and now they have, and we had it for 1 hour, and now their taking it back!!!!!! we spent a whole twiddling our thumbs waiting for them to plug in a few wires. We have every reason to be ticked

[pwilczynski]

I think that as others have mentioned, tension is a part of FIRST that is not only necessary, but also adds another challenge. The best teams are not necessarily those that have little or no tension, but it definitely makes everyone happier when that happens. For our team, there are really only two sub-teams: building and programming/electrical. We have a kind of awards team as well but they don't really need to change what they do based on different design changes. There is a lot of tension this year between the two teams because it is taking a very long time to build the robot because so much prototyping was being done early. Now there may not be enough time to finish calibrating all of the encoders and sensors with the real robot.