Quote:
Originally Posted by hg273
I was wondering if other teams have statistics about the average and median amount of hours committed by team members over the build season. Anecdotes would work too. What I'm looking for are things that I, and my team, can take to our administration to see if we can amend the policy before it goes into effect for next year's build season. Also, if anyone has any past experience with situations similar to this, anything would be greatly appreciated.
|
This probably isn't what you want to hear, but:
I think it all depends on what you want to do. In 2008 we built a robot that could probably compete with the Space Shuttle for most complicated system ever built.
[video] I spent about 170ish hours at the school... and I was only around for 3 weeks of build! The core students and mentors (12ish) also averaged 40+ hours. Our two lead mentors were somewhere north of that. In short, we built a totally sweet robot, but we totally burned out our team.
In 2009, we only met 3 times a week for 4 hours for the first 3 weeks, 4 times a week for weeks 4-5, and daily during week 6. We put in significantly fewer hours, yet we were *more* competitive than we were in 2008!
Limits are not bad things, after all
"Work expands so as to fill the time available for its completion." 