|
Re: Team Member Expectations
During the preseason, prospective team members participate in workshops run by older and more experienced members in each of our divisions (Design and Manufacturing, Energy Systems, Progamming, Strategy, Marketing&PR and Administration). This is usually a Wednesday afternoon commitment from 2:00-3:30.
During the Build Season, team members on average commit to about 22 hours of time per week, which is the average taken from a google form when they applied for the team. We very rarely look at how long they spent physically in the lab, but more what they're doing while in the lab. A team member that contributes and works hard for 2 hours on a machine is clearly more committed than the team member that is in the lab for 8 hours, but spends most of it sitting around and using his phone.
When applying, we stress that we're a robotics TEAM, and as such all the usual commitments apply, like showing up for meetings, being on time and showing earnest effort in the lab. This also means that if people are misbehaving, or not putting any effort into what they do, we can remind them that they were selected to join the team, and that their performance this year affects whether or not they're invited back to the team next year.
After Build Season ends, most people are told to take it easy and catch up on schoolwork, while a small group of people stay to work on Withholding Allowance stuff. These members keep the build season mentality and time commitment even after build season ends, and they usually end up being the people who put in the most work during Build Season as well. As for the rest of the team, we have a weekly Wednesday meeting to talk about competition preparation, but the time commitment drops significantly.
__________________
2013 FRC World Champions (1477, 1241, 610)
Queens University Computing Class of 2020
2013-2016: Team 610
2017-????: Team 4476
|