|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools |
Rating:
|
Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: Hours worked
Oh that is a good idea. Right now we use a messaging system for the students but I could make a simple toggle for it on the admin side of the team site.
See coming to CD just makes more work. ![]() |
|
#2
|
||||
|
||||
|
Re: Hours worked
Our Team has 30 scheduled hours per week, but I know that I go home and CAD so I don't waste time on a computer at a meeting, and I know that the lead mentor goes home and continuously thinks about solutions to problems and our drive coach goes home and thinks about strategy... So I think it's quite a few.
Though, 180 hours to build a robot doesn't seem like a whole lot... Even if I multiply it by the number of people working during the meetings (around 10) that's 1,800 hours... Yikes. Oh well. I'm sure we're not the worst of it.. right? |
|
#3
|
||||
|
||||
|
Re: Hours worked
We do a similar system. I'm not sure of the total hours put in by our team as a whole, but I have put in about 15-20 hours a week starting from kickoff. Our team does other competitions throughout the year and as of now I have a total of around 150 after school hours put in.
|
|
#4
|
|||
|
|||
|
Re: Hours worked
To count the time spent just since January 3rd, 2015, for myself personally, it will be 120 hours by the end of this weekend. As a team of 36 students and 9 mentors, we have a cumulative total of 2846 people-hours so far. That's an average of 63 hours per person, over the past 20 calendar days. Our top students will exceed 100 hours thus far by the end of today.
We have a total of 260 scheduled hours in the months of January, February, and March, and often stay well in excess of scheduled hours. |
|
#5
|
||||
|
||||
|
Re: Hours worked
Let's see... 5 hours Sat/Sun, 12 during the week, so 22 for somebody who shows up all the time per week. I've spent something like double that or more so far, sround 130 hours or more.
We have students constantly going in and out, and it's too much of a hassle to track them. Generally we know which kids are coming in more than others. |
|
#6
|
||||
|
||||
|
Re: Hours worked
708 started tracking hours the day before kickoff for the 45 students on the team. As of last Saturday, the average amount of hours per week range from 15-30 hours per student, with plenty of students having many more than that. The total man-hours for the team thus far are about 2540 hours excluding mentor hours.
|
|
#7
|
||||
|
||||
|
Re: Hours worked
So as team captain, I've only missed 1 day during the six week build season.
Now mind you we met 6 days a week. School week meetings runs from 3-8pm, Saturdays are 9-6pm. Doing the math, I've put in about 198 Hours minus the day I was not present. Factor in the extra hours this last week and I'm over the 210 mark. Crazy to think how much time is well spent right?! |
|
#8
|
||||
|
||||
|
Re: Hours worked
Looking at all of these posts, I didn't know that clocking in and out was a common thing. I kinda like the idea though. I might talk to a programmer about making a system. Sounds like a good offseason project for them.
I have been doing some rough estimations of hourly contributions with a few other people out of curiosity, and this is what I have come up with. I am CAD subteam captain, and I also worked on Build. Because of college classes, my school, day ends at 1:00. I put in at least 300 hours, possibly up to 320 or 330. There are three other people on my team who put in the same amount of time as me (roughly), a few in the 200-250 range, and around 20 at around 100. Five major mentors, putting in around 180 hours each. A few others putting in around 50-70. So that's between around 4820 and 4400 hours from students, and around a thousand mentor hours. A lot. Of time. Fortunately, my schedule this year features little homework, so I am lucky there. |
|
#9
|
|||||
|
|||||
|
Re: Hours worked
Actually, rather like our scouting, real-time data collection is done on paper for reliability, and entered into a spreadsheet a bit later.
|
|
#10
|
|||
|
|||
|
Re: Hours worked
I got excited last night when my Google spreadsheet that I've been logging robotics hours with told me a beautiful thing: I've spent exactly (to the nearest half hour) 250 hours at robotics during this build season, which averages out to about 41.67 hours per week.
The final weekend was craziest. 15 hours on Saturday, 18.5 on Sunday, and 14 on Monday for a total of 47.5 on those three days alone. |
|
#11
|
||||
|
||||
|
Re: Hours worked
My team of 12 students and 9 mentors logged a total of 1109 hours. 7 of those students qualified to attend regionals by getting 50 hours during build season.
My personal total was 180 hours. I am extremely proud of the result of those hours. |
|
#12
|
|||||
|
|||||
|
Re: Hours worked
Team 1208 usually logs 6500 hours per season. That includes August to April.
|
|
#13
|
||||
|
||||
|
Re: Hours worked
I didn't want to, but I added it up.
Between regular build meetings, and then the time outside that planning, finding and ordering parts, helping on various parts/boards etc in the early mornings and evenings after meetings, I've spent about 400 hours. Since kickoff. Not including my 1.5hrs each day driving there and home. |
|
#14
|
||||
|
||||
|
Re: Hours worked
I have spent about 200 hours in our workshop during build season and about another 50 CADing and doing research. That is not including my 30 min of commuting each day and about 3 hours a week running to the store and getting food for the team.
|
|
#15
|
|||
|
|||
|
Re: Hours worked
Our team uses an online sign in/sign out system. Personally I have about 120 hours this season. I don't know how many total hours our team has though. Probably a lot...
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|