Go to Post Sustaining an FRC team is really hard! - Jared Russell [more]
Home
Go Back   Chief Delphi > Competition > Team Organization
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
 
 
Thread Tools Rating: Thread Rating: 2 votes, 5.00 average. Display Modes
Prev Previous Post   Next Post Next
  #2   Spotlight this post!  
Unread 16-12-2011, 21:55
RoboMaster's Avatar
RoboMaster RoboMaster is offline
Alum, former programmer&co-captain
FRC #2472 (The Centurions)
Team Role: Mentor
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Minnesota, Twin Cities
Posts: 268
RoboMaster has a brilliant futureRoboMaster has a brilliant futureRoboMaster has a brilliant futureRoboMaster has a brilliant futureRoboMaster has a brilliant futureRoboMaster has a brilliant futureRoboMaster has a brilliant futureRoboMaster has a brilliant futureRoboMaster has a brilliant futureRoboMaster has a brilliant futureRoboMaster has a brilliant future
Re: Team organization issues and Build Season Schedule

I won't personally comment on everything you said, I'll let others help with that, but I'll try to give some advice from my experience.

I very much agree with spending a good long time on clarifying the game plan (you said you wanted more than 3 hours). I have a question and a suggestion for this later on, but here's some other advice first. The rest of your team might not understand the importance of the design process, or they may think it's important but just doesn't need as much time as you think it does. Which is it?
That is helpful to know when you're trying to counter their opinions. In fact, learning more about what they think can help you better understand the topic in general, since you include all viewpoints, allowing you to see what really is the best. It also helps keep you from seeing their views too negatively.

Now, what is your/your team's definition of a "game plan"? I ask because I want to warn you not to finalize such an idea too early on. I've seen that picking the overall strategy for the team/robot is very closely related to the specific robot designs that accomplish that strategy. You need to think about both almost at the same time to be able to judge which strategy is the best. For example, if you lock down a strategy in the beginning, but then later realize that it is simply to impractical to build robots to match that strategy, you need to change your overall focus. And that's hard to come back, start over, or do on the fly. I would suggest being open to all ideas and strategies for a day or two, and then when you understand the possibilities of the different strategies, you can better finalize one.


Also, it's great that you're going to discuss things with your leader to improve things, but expect that things still might not end up the way you want it. In big groups like this people will always disagree with you, and if it's a majority or a person of leadership above you, it might be best to just let it go. Your team still might not crash and burn and you can still have a good time. Furthermore, if you disagree and fight too much, it can make the issue worse and waste time. So be careful how you approach this, and for what personal reasons you may be doing it for.
__________________
My engineering blog: noeticbrainwaves.blogspot.com

I'm not slacking, my code's compiling
...and I'm using LabVIEW
Reply With Quote
 


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 06:09.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi