Thread: Commitment
View Single Post
  #20   Spotlight this post!  
Unread 12-11-2007, 17:00
ay2b's Avatar
ay2b ay2b is offline
Registered User
AKA: Andy
FRC #2928
Team Role: Mentor
 
Join Date: Mar 2004
Rookie Year: 1994
Location: Seattle, WA
Posts: 211
ay2b has a brilliant futureay2b has a brilliant futureay2b has a brilliant futureay2b has a brilliant futureay2b has a brilliant futureay2b has a brilliant futureay2b has a brilliant futureay2b has a brilliant futureay2b has a brilliant futureay2b has a brilliant futureay2b has a brilliant future
Re: Commitment

Quote:
Originally Posted by neoshaakti View Post
Many of the members on our team are really concerned about the commitment required during the 6-week build season, and don't think that they would be able to meet more than twice a week.
Part of my job as "leadership" is to give the rest of the team a clear idea of what the build season is going to look like commitment-wise.
Therefore,
How much individual commitment is required to be on your FRC team?

I know commitment is really relative, so if you'd rather say how many hours are spent each week during build season, that works too

thanks a whole bunch!
It is a big commitment. But it's worth it. Hopefully as the build progresses, the rest of the team will see that and want to come more often. Perhaps you could start with something like having 1/2 the team meet on Mon & Wed, and the other 1/2 on Tue & Thu, and everyone on Sat. That's only three times per week, which is not much more than the twice per week that people wanted, but allows for people who want to put in more time to easily start showing up more often.

There's been times I've put in an average of over 40 hours per week. Other years I've done less.

As "leadership" try to figure out early on how much time you will actually have people putting in (not what they say they'll put in, but what they'll actually do). Make sure you plan your design accordingly. Say you have 10 people meeting twice a week for 4 hours per session over 6 weeks. That's 480 man-hours of work. Say you have 10 people meeting for 40 hours per week over 6 weeks; that's 2400 man-hours of work. 480 man-hours spent on a simple design which requires only 450 man-hours to complete is going to perform much better than 2400 man-hours spent on a design which requires 3000 man-hours to complete.
__________________

2011 - SD Quarterfinalists (980), LA Quarterfinalists (980)
2010 - LA (2404) Finalists (980), AZ Motorola Quality (980)
2009 - LA Semifinalists (980); Las Vegas Quarterfinalists (980); SD (2404); IRI #1 Seed, Finalist (980)
2008 - SD Quarterfinalists (980), LA Champions (980), LA Rookie Inspiration Award (2404); CalGames Finalists
2007 - So.Cal Finalists (980), SD Quarterfinalists (980); CalGames Finalists
2006 - So.Cal Regional Champion (4), Toronto Judge's Award Day 1 (4)
2005 - SVR Champions, Delphi "Driving Tomorrow's Technology" (980); AZ Xerox Creativity (980); So.Cal Finalists, RadioShack Innovation in Control (980); Championship Archimedes Division Semifinalists; IRI Finalists (980)
2004 - So.Cal Regional Champions, Leadership in Controls (980); AZ GM Industrial Design (980); Championship Galileo Division #2 Seed; IRI Champions
2003 - PNW Semi-finalists (488)
2002 - PNW Finalists (488)
2000 - X-bot / 488 - Mentor / Founder
1994 - Sunny Delight - Driver - champion
Reply With Quote