|
|
|
![]() |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#1
|
||||
|
||||
|
[FRC-Designs.com] Where Are You: Week 1
FRC Designs (http://www.frc-designs.com) presents, “Where Are You,” by Matt Starke. Matt has been a member of FIRST since 2003. He has worked with numerous teams in his years as a student, mentor, and engineer. As the founder of FRC Designs, he desires to share his many experiences as the 2012 FRC Build Season begins.
“Where are you,” postings are intended to create a discussion for teams to reflect on where they have gotten so far in the 2012 FRC build season. Feel free to post your own thoughts and opinions. I look forward to the postings! Where are you? Week 1 FRC Designs: http://www.frc-designs.com Twitter: @FRCDesigns Analyze the Game Challenge Completely One key that teams seem to miss is analyzing the game challenge completely and accurately. It is important that the entire team understands the extent game challenge and rules that are associated with it. It is an extreme pressure to start prototyping ideas and solutions. Don’t do it quite yet! There have been many times where if I just read the rules thoroughly, I would have not took the time to do/try something. There are two methods that I have seen in my FRC career. The first method I have seen successfully is an entire team playing a “mock match.” This requires enough room for at least a half field to a full field of size. You can use trash cans, balls, and rolling chairs with students as robots. Rotating students through the field as the challenge and rules are discussed allows everyone to better understand what is happening. Also, I have seen “sit and read” time after the kickoff has been completed. I know that it is hard to believe, but I have seen teams require a silent read time to better grasp the rules. After sufficient time has been given, the team discusses together important aspects of scoring to the game. Brainstorming After completely analyzing the game challenge, brainstorming is the next most important step. I have seen good brainstorming sessions and bad ones. The key to brainstorming is to get as many ideas on the table as possible. Never judge what anyone says. This includes what you say in the brainstorming session as well as what is said back to you. Overall, I have found that group of 4 to 6 to work well. After six members, it is hard to allow everyone to have enough time to speak. I have seen two different variations of brainstorming groups that have been successful. I have seen mechanical/electrical/programming groups sent to different areas as well as one member from each sub-team represented in each group. I have also seen “freshman/rookies” left to brainstorm by them because they tend to be the most creative. Decide what works best for your team and try it. You can always modify as time goes on. A good brainstorming session is one that ideas work off of each other. Lots of paper and pencil sketches are made, people encourage one another, all comments are allowed, and brains hurt after a while. A bad brainstorming session is one where opinions override others, comments are ignored, creative thoughts are prohibited, and brains hurt with frustration. Follow Key Groups It is important to establish a good foundation of groups to follow during build season. I have made a quick list below and a short reason why (In no particular order):
Last edited by Starke : 13-01-2012 at 20:38. |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|