The main test we have is a game test. For example for toss up, we asked questions regarding point systems, dimensions of the field, robot limitations (what can you use on the robot/ what your robot can do/ etc.). This test just covers everything you need to know to design. Since designing is naturally a competitive field where information is covered, we don’t add a minimum score required to pass. The test itself should take around 30 minutes to administer and 10 minutes to review. Each person grades themselves to speed up the process and they keep their own form for review.
Another test we have us the drivers test. This test covers game rules, ways to score, and pressure questions. The scores are then tiered. Whoever gets the highest score has first pick on what he/she wants to control and when he/she gets to drive when the opportunity is available. The next highest score gets the remaining slot and third and fourth and so on gets to drive if someone is missing. However, there is a restraint. Team captains, presidents, and vice presidents are not allowed to be drivers because it would sap their attention in overseeing the group
Another test we have is a cleaning test. It’s just free response questions, usually with a photo asking where certain items belong. if you dont get higher than an 80%, you’re forced to clean the shop for a week and you’re not allowed to build until you pass the test.
Since we also use power tools, we also take safety tests. In order to build, you must have a 100% on this test. It’s free response, and questions are usually intuitive (what does this button do on a tool, whenever you do ____ you must____). If the member is missing a critical step, they will not be allowed to use tools until they pass the test
Each test can be administered whenever. They’re all electronic so they’ll always be available.
in this case, either the president, vice president, or mentor has to talk to the student. It’ll be obvious that work is falling behind, so i would approach them saying that they should offer the task they’re working on to another student. Another way to avoid this is to have the group as a whole discuss what’s going to happen on the robot. With this, each person has a general idea of how things are going to work. Also, if you could get cad files of the design, you can give a picture of a manipulator to get members working fast, especially those who are savvy with legos.
Now if it’s a personality issue, such as that one person believes everyone else is incompetent, your going to have a battle ahead of you. Truly, i don’t know how to solve this issue. But the way i’ve treated this issue is by exploiting weaknesses in their mindset: prove that the team is being slowed down by only one person working, prove that everyone’s word is useful, prove that it’s possible to teach others, et cetera.
Another thing you need to be careful of is splintering. Don’t make parties form, after all, you all have one goal as a team. Usually this occurs when an individual tries to impress others for future benefit. This is especially noticeable in our system so we’re cautious to target this fast.