|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: Commitment
The CyberCards meet six days a week (we take Sundays off or my wife would shoot me). School gets out at 2:30; we usually leave between 6-7. On Saturdays, we're here from 10:30-5ish.
We expect the veteran members to be here at least 80% of the time; JV members at least 60%. We realize there are other taxing issues for high school students (academics, sports, jobs, other clubs & organizations). |
|
#2
|
|||||
|
|||||
|
Re: Commitment
4 or 5 hours a day, 6 days a week, is about right for the first few weeks, then when you see how far behind you are it might go up to 7 hours a day.....or more.....
|
|
#3
|
|||||
|
|||||
|
Re: Commitment
Usually about one-two hours per night for the first several weeks, with 8AM-5PM on Saturdays and then Sunday afternoons. Let's see now: 5 hours + 9 hours (with lunch) + 5 hours or so= minimum 19 hours per week. Not everyone shows up every night though; the only required meetings are Friday night and Saturday.
The later we get, the longer we go. I'd say as many as 25 hours or more per week during the last two weeks. Then again, crunch time practically starts during Week 1. I'd say that every team has their own time requirement/constraint. If you can only meet as a team twice a week, great. Use those times to update the entire team on what is happening. Smaller groups can meet more often and work on their portion of the robot. |
|
#4
|
|||||
|
|||||
|
Re: Commitment
Quote:
After the first 3 weeks, people start showing up quite a bit more. Integration between teams starts to happen, and people are there as much as they can be. All team members are required to be there every Saturday during the entire build season. Personally, I am there every day/night that we open the shop. So thats: 3-8 (5 hours) weekdays 9-5 (8 hours) weekends 5*5*6 (weekdays) + 8*6 (saturdays) + 8*3 (sundays) = 222 hours. I am also there for the 72 hours before and during the UTC scrimmage, take 6 hours sleep, and then work on the bot for 48 hours. This adds an additional 120 hours, for a total of 342 hours. So I guess for our team, the maximum number of hours that can be put in are 342 hours. For the past 3 years I haven't missed a day (perfect attendance!!) We typically expect students to be there 2 nights a week plus saturdays, totaling 18 hours a week * 6 weeks = 108 hours. 108/222 regular build hours is 48% of the time. Thats approximately the expectation. Keep in mind that we have a large team with 30+ students and this time does not include fundraising time. While 48% of the time doesn't sound like much, we are open an awful lot. Jacob |
|
#5
|
|||
|
|||
|
Re: Commitment
Lets see... 973 does this:
Weekdays: Shop opens at about 4pm, closes at about 10pm. Might go later on some days later in the season... All-nighters are nothing new. Weekends: Saturday: 10am to 5pm. Can go much later. We don't often work Sunday, thats when we get our schoolwork done. However, those last few weeks... |
|
#6
|
||||
|
||||
|
Re: Commitment
We do Saturday-Thursday with the amount of time/night varying depending on what is getting done and how much needs to be done. I don't think we actually have a hard minimum attendance, but if you never show up and never do any work, you don't get to go to the competition.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| [FTC]: Rockwell Collins to Announce Significant K-12 STEM Education Commitment | KathieK | FIRST Tech Challenge | 3 | 17-08-2007 11:16 |