|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Re: Getting every member to know everything possible.
Quote:
By the way, big thanks for the input. 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 Last edited by JoeXIII'007 : 17-10-2005 at 21:46. |
|
#2
|
|||||
|
|||||
|
Re: Getting every member to know everything possible.
This is my first year mentoring a brand spankin' new FLL team and we have been using the method of letting everyone build during meetings and do independent research at home with a quick wrap-up meeting at the end to see what everyone has come up with so far on their research project. We aren't too sure yet how well this will work out in the long run, but for now, it gives the students the chance to work with the kit and brainstorm competition solutions together.
|
|
#3
|
||||
|
||||
|
Re: Getting every member to know everything possible.
Quote:
|
|
#4
|
|||||
|
|||||
|
Re: Getting every member to know everything possible.
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. |
|
#5
|
|||||
|
|||||
|
Re: Getting every member to know everything possible.
Quote:
) 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. |
|
#6
|
|||||
|
|||||
|
Re: Getting every member to know everything possible.
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.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Who's a Returning Rookie Member? | cavegirl47 | General Forum | 5 | 11-12-2004 00:58 |
| Fantasy FIRST suggestions for next year | Joe Ross | Fantasy FIRST | 39 | 14-04-2004 01:13 |
| Valued CD members | GregTheGreat | Thanks and/or Congrats | 16 | 07-07-2003 12:58 |
| Junior member wishes to be senior member.. | randomperson | Chit-Chat | 5 | 07-04-2003 18:50 |
| Junior Member/ Senior Member / Frequent Contributor / <<WHATEVER YOU WANT HERE>> | yangotang | CD Forum Support | 5 | 13-02-2003 12:41 |