Quote:
Originally Posted by BenGuy
This is something that I think all teams face. Unless you have a core group of a few people, there are bound to be those who get bored and are not as engaged and care about the subject as others. We make sure everyone has the 'opportunity to succeed' by letting them be in the discussion. However, it's like the saying goes, 'you can lead a horse to water but you can't make it drink.' Those who are leaders and are engaged excel and stay focused, those who aren't focused are setting themselves up to be behind the rest of the year.
|
It's similar on our team. We try to have every member engaged in the beginning when going over the game, rules, ideas, etc, but only a few remain engaged in the discussions for the whole day. Usually halfway through when game/idea discussions start to become more detailed, large parts of the team break off either to get started on prototypes, KOP inventory, making critical parts of the field needed for prototyping and other stuff along that nature.
Usually the drivetrain is decided very quickly(Typically a 6WD Kit) and many students will begin working on getting that up and running. Programming team also starts getting new software and firmware set up. Lots of stuff happen on the first day that's for sure.
While it would be cool for every student to be active in design or strategy discussions, not every student wants to do it. Typically it's the more experienced members or students that naturally have a strategy mindset that are the most involved. Though this is typically only 4-5 students, it's a pretty good number considering the core team consists of only about 18 students.