Quote:
Originally Posted by EricH
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.
|
Our team works similarly to Eric's. We meet 6 days a week for the first 3 weeks, and 7 days a week for the remaining 3 weeks. Different sub-teams meet on different sets of nights (ex: electrical meets T-TH, manipulator M-W, etc.) This works in the beginning while concepts and prototypes are being built.
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