Getting every member to know everything possible.

[Ian Curtis]

Originally Posted by JoeXIII'007

Got a few more questions. When your team has two things due: the technical and the reasearch project, is it necessary to split the team up with half on the robot and half on the research, and then have like a quick meeting to review it all for the entire team? The team has tried this and it worked fairly well last year, but the advisor seems like she doesn't want to do that this year. It's either all on robot or all on research.

-Joe

YES! If you can get everything done with everyone working on everything, your kids are more mature than anyone I was ever on a team with/ ever was. If everyone does everything you WILL run out of time and you WON'T get things done.

[GaryVoshol]

Every team member should know something about everything. Obviously, you know the most about what you did the most.

On the technical side, some don't know programming at all, and that's OK. But you should know the key features about your robot - what kind of drive train, gearing, where are the sensors and what do they do, etc. When judges come to the pits for a second look at your team (after the formal interviews), you never know who they will find to talk with.

For project presentation, everyone should be able to answer general questions. Specific questions about a fact in your presentation could be answered by the person who researched it. Judges like to see several people raising their hands or otherwise indicating they know something about the question. No one person should dominate the conversation.

[EricH]

Originally Posted by GaryV1188

On the technical side, some don't know programming at all, and that's OK. But you should know the key features about your robot - what kind of drive train, gearing, where are the sensors and what do they do, etc.
For project presentation, everyone should be able to answer general questions. Specific questions about a fact in your presentation could be answered by the person who researched it. Judges like to see several people raising their hands or otherwise indicating they know something about the question.

I agree 1000%. (yeah, I know that's a bit much ) We have 1 builder, four programmers (including the builder) and three who worked on the project a lot. We also made sure to give them all several runs through the project presentation, including one where two mentors (myself included) acted as judges. We identified areas that needed improvement. We also made sure that everyone knew the correct answer to each question asked.

[KTorak]

When I was on an FLL team, we had a "brain storm session" where each group would explain to everyone else what they did, why they did it, how, etc. After we had the presentations, the mentors would sit down and ask each kid a set of questions about anything they wanted to make sure they knew about everything.