Quote:
|
Originally Posted by 1987
Here's something you could try next year. The way our team works out who can go to Nationals is everybody gets a "hours" card and it is there respsonsiblity to keep track of it and have one of our mentors sign off that they were there for X number of hours. We set the mimumum to go to Nationals at 35 hours can go to Nationals but we also have it so if space becomes an issue the team members with the most hours can go. It seems to work for our team. It also gives our team members that little extra incentive.
I know this won't help you this year but maybe it might next year.
GOOD LUCK
Joe
|
my view on this is that hours and producivity are two different things. someone can be at a meeting for 6 hours on a Saturday where you just sit there and going to a meeting for 3 hours on a weeknight where you do a lot. I think that the card idea is an awesome idea, and at the same time you should right down what you did for those hours. even if all you did was sit at the computer, programming, and didnt make much progress in the code because you had to delete some stuff and then rewrite (so to a mechanical person .. it seems like you did nothing) or you were correcting simple things that might slow the robot down .. i think that should be written too ...