|
|
|
| You've stolen the 128-bit encryption key to my heart. |
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools |
Rating:
|
Display Modes |
|
#16
|
||||
|
||||
|
Re: Hours worked
Our team has 27 scheduled hours of work each week during the build season. That doesn't include work that CAD students are doing at home, or supply runs, or Google Hangout strategy sessions on Sunday. If we average 15 students (though often its more like 25), that is around 1200 person-hours of work done on the robot so far this build season.
|
|
#17
|
||||
|
||||
|
Re: Hours worked
We've tracked time for a number of years, not meeting the minimum cutoff means the team won't pay for you to attend competitions.
With respect to tracking mentor hours, we do ask our mentors, alums (both student and parent) and parents to login when they are working too. This allows us to demonstrate in real numbers the amount of support the team has beyond the students to our school board, community, sponsors. Two of our former team members built a custom time clock for us right before kickoff. We had been using a COTS app meant for employees. The new lets users check their own hours from the clock console - so no excuse for "not knowing where they stood" the day before we leave for competition. It also has a text feature that lets mentors send a "shop open" or "shop closing early" message. My favorite part is when mentors are logged in "shop is open" message is added to the team website and when they clock out it says "shop is closed" so kids and parents can just check the website to see if someone is there before they stop by. |
|
#18
|
|||
|
|||
|
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. ![]() |
|
#19
|
||||
|
||||
|
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? |
|
#20
|
||||
|
||||
|
Re: Hours worked
So far this year, Team 900 Students/Mentors have logged 3949 hours. Since build season started we've had 2040 hours logged. Those numbers only count logged hours. At least one mentor never remembers to sign in, and if a student forgets to sign out they get credited for only 1 minute of time.
I also built us a time logging system for our team (and some pretty graphs). Constantly modifying/updating it. If anyone is interested it's open source and can be found here: https://github.com/FRC900/timesheet Last edited by meg : 23-01-2015 at 13:09. |
|
#21
|
||||
|
||||
|
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.
|
|
#22
|
|||
|
|||
|
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. |
|
#23
|
||||
|
||||
|
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. |
|
#24
|
||||
|
||||
|
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.
|
|
#25
|
|||
|
|||
|
Re: Hours worked
Last year we went to signing in and out, but never did much with the data. This year we are tracking it as part of eligibility for positions at competitions.
We have 13 students, and they have clocked 545 hours (since the Monday after Kickoff) before we started our long Saturday today. Individual students range from 8 to 30 hours per week. |
|
#26
|
|||
|
|||
|
Re: Hours worked
We don't have any logging system, but I know we have logged a lot of hours because our team has been running as a class for the first 3 weeks of the build season. Between first and second semester, our school has J-term, which allows us to make robotics a day-long class. It has given us tons of time and a great headstart in this first 3 weeks. Sadly now we are back to regular classes and meeting after school going into build week 4.
|
|
#27
|
|||
|
|||
|
We had a team of 75 last year and after winning our regional and attending worlds we received 140 applications for the team. We cut the team size to 50 members, and our team is at 90 hours per person since January 3rd. Probably a little more because sometimes we forget to sign in.
|
|
#28
|
|||
|
|||
|
Re: Hours worked
To the best of my knowledge, I'm the only one on the team who has consistently logged time.
53 hours from October 20th through January 3rd 102 hours from January 3rd through 17th 155 total hours (9,300 minutes) No wonder I don't have a life. Disclaimer: I am a team captain and help with graphic design and marketing, really obsess over FRC, and am homeschooled so I can put in extra time on top of meetings. So this is more than the average Wired Wizard. But it's still a lot! And I can not believe it's actually stop build day today. My last year as a student on an FRC team. ;( |
|
#29
|
||||
|
||||
|
Re: Hours worked
We started logging hours last year and kept better track of it. This year we have not been so consistent with keeping everything up to date. Last year at least, I had around 350 hours by the end of build season and I assume around the same amount if not more this year.
Do any teams use the hours to motivate students to show up more such as posting "rankings" for everyone to see? |
|
#30
|
||||
|
||||
|
Re: Hours worked
This year we installed a clock in/clock out system to track how much time we spend because we've never even had a great estimate in the past. Once we are done with the season, I'll try to remember to post some analysis in here.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|