Quote:
Originally Posted by Rangel(kf7fdb)
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.
|
Traditionally, 610 has done a Saturday post-release + short afternoon casual talk in small groups, then we meet as an entire team after thinking our ideas over a night, then we have a large group discussion on Sunday. This year, we'll be making small groups of 4-5 (we have a team of 49 I think), which each includes at least 2 experienced or senior members who have a firm grasp on strategy, and it's their job to explain the concepts to new members, who sometimes come up with extremely innovative solutions.
Personally, I'm really against the idea of people not having input on the robot, even if they don't want to, because if they're dissatisfied with the end product, they may end up blaming themselves for not being more engaged at the beginning with the Strategic breakdown.