Post by drmike on May 10, 2015 0:38:33 GMT
The team round... this is where 15 people work on 10 problems for 20 minutes...
Piece of cake!
Yup... unfortunately it is sauerkraut cake with brusselsprout frosting.
So... how to handle this...
1) Team Leader/ Recorder
Each team needs a coordinator/leader to help distribute the problems to be sure that each question is looked at and not have 15 people working question 1.
Team members need to listen to the Team Leader and not go rogue... if you are assigned #5 but decide 30 seconds into the question that #10 looks more fun... well, 1) #10 is probably brutally hard and 2) the team is counting on you for #5. When you finish #5, then let the team leader know that you have insight or a desire for #10.
2) 6
6 is a great score on the Team Round... these questions are difficult and become more difficult, typically, as the numbers get higher... let's be sure to get 6 of the first 7 questions answered correctly to maximize our points.
3) Find your strengths
The 20 minutes of the team round is NOT the time to try to develop an interest in combinatorics when you've never done that before!! Find your strong area and concentrate on finding that problem to work. For example, I (Dr. Mike) would only be put on a purely geometrical problem as a last resort... combinatorics... yeah, that is more in my wheel-house!
4) Find like minds
If you can work on the Fab 42 and find out who thinks like you... or in a similar way that complements you well... that should be the person with whom you work in the Team Round!! (Be sure that if you are on Team A, that the person is NOT on Team B!) This can/should be done before the meet starts... (Fab 42, the bus, etc.).
Remember... at the actual meet, you are able to LEAVE YOUR SEAT to work with someone (you will have the whole room!!!)
5) Answers for everything before TIME is called!
When TIME is called... that is it! Have your paper in the air ready to be taken. When TIME is called is NOT when you should start writing down answers.
6) Checking
If a group is unsure of their answer to a question, be sure to have another group on the team check that problem!
Piece of cake!
Yup... unfortunately it is sauerkraut cake with brusselsprout frosting.
So... how to handle this...
1) Team Leader/ Recorder
Each team needs a coordinator/leader to help distribute the problems to be sure that each question is looked at and not have 15 people working question 1.
Team members need to listen to the Team Leader and not go rogue... if you are assigned #5 but decide 30 seconds into the question that #10 looks more fun... well, 1) #10 is probably brutally hard and 2) the team is counting on you for #5. When you finish #5, then let the team leader know that you have insight or a desire for #10.
2) 6
6 is a great score on the Team Round... these questions are difficult and become more difficult, typically, as the numbers get higher... let's be sure to get 6 of the first 7 questions answered correctly to maximize our points.
3) Find your strengths
The 20 minutes of the team round is NOT the time to try to develop an interest in combinatorics when you've never done that before!! Find your strong area and concentrate on finding that problem to work. For example, I (Dr. Mike) would only be put on a purely geometrical problem as a last resort... combinatorics... yeah, that is more in my wheel-house!
4) Find like minds
If you can work on the Fab 42 and find out who thinks like you... or in a similar way that complements you well... that should be the person with whom you work in the Team Round!! (Be sure that if you are on Team A, that the person is NOT on Team B!) This can/should be done before the meet starts... (Fab 42, the bus, etc.).
Remember... at the actual meet, you are able to LEAVE YOUR SEAT to work with someone (you will have the whole room!!!)
5) Answers for everything before TIME is called!
When TIME is called... that is it! Have your paper in the air ready to be taken. When TIME is called is NOT when you should start writing down answers.
6) Checking
If a group is unsure of their answer to a question, be sure to have another group on the team check that problem!