Growing Team

[MrMurf]

For teams that do sub divisions, do you allow students to be in more than one group so they can experience different aspects of engineering and non engineering? What about groups who seem to have specific lifespans? Ex: What does the chassis team do once the chassis is complete?

[Hallry]

Originally Posted by MrMurf

For teams that do sub divisions, do you allow students to be in more than one group so they can experience different aspects of engineering and non engineering?

Most of our engineering groups only do their engineering-related tasks, but recently we've had some non-engineering groups want to learn how to do other things, which they are allowed to do after their own work is done.

Originally Posted by MrMurf

What about groups who seem to have specific lifespans? Ex: What does the chassis team do once the chassis is complete?

If one group doesn't have work, they usually do miscellaneous work such as button-making, or any task that needs to get done. However, there constant seems to be work, and our chassis team is usually always busy either creating the robot's chassis, creating our test/practice bot's chassis, or fixing one of the two. Our idlers never seem to like to stay in one place for long =P

[EricH]

If a group doesn't have work to do, but another group is running into an issue, you can do a "Tiger Team" with the finished group to come up with alternative solutions. I've been on those more than once when either there was an issue or we hadn't done a detail design due to priorities. Or get some of them to do non-engineering stuff like scouting.