View Single Post
  #4   Spotlight this post!  
Unread 28-03-2005, 18:33
Jeffmudhs's Avatar
Jeffmudhs Jeffmudhs is offline
Registered User
FRC #0357 (Royal Assault)
 
Join Date: Feb 2005
Rookie Year: 2002
Location: Upper Darby
Posts: 17
Jeffmudhs has a spectacular aura aboutJeffmudhs has a spectacular aura about
Re: Chronic Problems

Quote:
Originally Posted by Ewilliams2006
1. Fund Raising - Every year my team seems to be scrambling for the bare minimum to enter our regional competition (forget about the nationals). This takes away valuable time from team organization and "pre kit-arrival" planning. Are we in the same boat as everyone else? If not, how does your team avoid this problem?
My best answer to this would be to start fundraising in the middle of the summer, don't stop fundraising. Go around to local bussiness with a pamphlet of what first is, what your team does in the community, and speak to managers and owners of local bussiness. Get your school involved, hold candy sales, present to the school board and get them involved. Find major bussiness with offices in your area, and request to present to them. goto local shopping malls and present there asking for donations or even mentors you'd be surprised who you could attract. Car washes are always a fun summer event and raise awareness about your team.

Parents, Reletives, and family friends can be a great assest to financial support.

Quote:
Originally Posted by Ewilliams2006
2. Team Members - Many times I feel the size of a team has an inverse relationship on the productivity of the group. I realize this is a learning experience, and really the competition is meaningless, but it seems some people come down to the meetings and do nothing but detract from the other's ability to work effectively. I feel that there is a core group of people that are very knowledgeable and work well together to finalize a goal. Then there are some people that aren't that knowledgeable that somehow find ways to inhibit the smooth flow of work put into the project. I am in no position to tell people not to come, nor do I feel that it would be justified if I could. However, are there any tips on getting these "lazy" people to work? I've tried assigning tasks that are semi-crucial to the team, such as tool organizing, PR work, and the like - but it seems like these projects, though important, are degrading and no-one will stay on task. (Granted, if I was put on one of those assignments I probably wouldn't stay on task either). Basically, I'm looking for a way to keep people mainly working in areas they can produce good work in. I don't feel one person should be isolated to a single job without any input on anything else, but it always seems to waste so much time (our single most important resource), arguing with someone who doesn't know a piston from a Victor about how to wire the robot (note, this is a complaint I hear from most of the "core" group of the team, not just myself).
The best way to get "Lazy" people to work, is to ask them what they want to do. If they are unsure allow them to float around the team and find what they are best at. Perhaps give them a job where they are in charge, but still participating in the aspects of what they are in charge of. Try not to pick on them, as that will most likely cause for a hostile situation. Speak to mentors about problem students, they may not always be aware of that as some students seem to only do work when the 'teacher is looking'. If they feel they do not feel welcomed by the team, give them a nickname.

Coffeeism said it nicely hold workshops in the preseason, educate students on safety in the workshop, what each component does, how the code works. Make these workshops optional (except for safety), and you can easier tell where students are more intrested in.

As teams get larger, students can feel unnessecary or over looked as returning members who know how first works tend to do a majority of the work without explaining what thier doing and why. We try to emphasize peer mentoring. its a great way to increase student involvement

Hopefully I helped, Jeff McCarrin
Reply With Quote