This document describes the 971 team’s rules and expectations. It starts out with a description of the FIRST program and its mission, then covers our team’s goals and the team member contract, and finishes with specific rules and expectations. By having and following these, we believe that the team will be able to be more successful at reaching and positively impacting the lives of more students.
FRC Team 971 is a high school robotics team for current MVHS students. Students who will be attending MVHS in the fall may begin attending meetings starting in the summer.
FIRST stands for “For Inspiration and Recognition of Science and Technology” and was founded in 1989 by Dean Kamen to inspire young people's interest and participation in science and technology. FIRST designs accessible, innovative programs that motivate young people to pursue education and career opportunities in science, technology, engineering, and math, while building self-confidence, knowledge, and life skills.
Being part of FIRST is a life-changing, career molding experience and a lot of fun! FIRST’s mission is “to inspire young people to be science and technology leaders, by engaging them in exciting mentor-based programs that build science, engineering, and technology skills, that inspire innovation, and that foster well-rounded life capabilities including self-confidence, communication, and leadership.”
Dr. Woodie Flowers, FIRST National Advisor and Pappalardo Professor Emeritus of Mechanical Engineering, Massachusetts Institute of Technology, coined the term “Gracious Professionalism®”. Gracious Professionalism is part of the ethos of FIRST. It's a way of doing things that encourages high-quality work, emphasizes the value of others, and respects individuals and the community. With Gracious Professionalism, fierce competition and mutual gain are not separate notions. Gracious professionals learn and compete like crazy, but treat one another with respect and kindness in the process. They avoid treating anyone like losers. No chest thumping tough talk, but no sticky-sweet platitudes either. Knowledge, competition, and empathy are comfortably blended. In the long run, Gracious Professionalism is part of pursuing a meaningful life. One can add to society and enjoy the satisfaction of knowing one has acted with integrity and sensitivity.
FIRST Team 971 is formed of a partnership between students and adult mentors. The team is structured so that students can learn real-life engineering, business, and life skills by working side-by-side with adult mentors. Students are encouraged and expected to take on responsible tasks. Our goal is to build a sustainable team that provides an enriching experience for students and mentors, grows to be a world class team, and has a lot of fun doing so!
We have found that in order to be a full contributing member of the robotics team, a member needs to commit to a minimum level of attendance. While there is no specific attendance requirement for participating in team meetings and helping on the team, students who do not meet the minimum time commitment will find it difficult to be involved on more than the most basic level. This is a team just like a sports team and commitment and practice is necessary for success.
Off Season participation: The off season is the time during the school year after the competitions are over in April until before the first weekend in January, including the summer. New members should attend at least one meeting a week during the off season so that they can learn how the team works and how to use the many tools that the team owns - hand tools, power tools, and computer aided design (CAD) software. Some students take the summer off, which is fine, and others learn a lot from their time invested during the summer. Spending more time learning in the off season will make members, both new and returning, more prepared for the season. Once the season starts in January, there is much less time for training.
Competition season participation: The competition season runs from January through April and we meet five days a week with a leadership meeting on a sixth day. During this season a minimum of two meetings a week, with at least one of those being on a weekend, is required to be a full participating member of the team. We also meet and work on the robots during school breaks - especially during the winter break before the stop build date. Returning members often schedule family trips around these dates because a lot of fun and exciting work is done during that time.
The team does a lot of work and designing on the weekends when there is more time and there are more mentor resources available. Because of the short design and build timeline, time critical projects will be worked on throughout the week and weekend. A project started on a Wednesday evening during the competition season may have completely changed or be finished by the next Wednesday evening. Members who want to see their projects through to completion need to show up to several meetings a week. Some students and mentors work late into the evenings on weekends as we get closer to our deadlines, and the more students who are committed to help, when they can, on the weekends will allow us to get more done on the robot and increase our odds of performing well. Students who spend a lot of time on robotics also find that their time spent is more fun and rewarding.
Leadership: Students who commit to being leaders on the team find it to be very rewarding. Team leadership often spends time outside team meetings working on their leadership tasks, and this extra commitment should be understood and taken into account when stepping into leadership roles. The leadership council works to make sure that students can be successful as leaders and still do well in school.
Because a high level of commitment from team members is required to learn how to contribute and perform well as a team, students who do not make a minimum commitment (two meetings per week, including a weekend meeting during the competition season) will not be excused from school to attend competitions. All students may attend competitions during the hours after school and are encouraged to do so. All students are welcome to help during the competition.
All team members and mentors must agree to and sign the Team Member Contract. It is repeated here.
As part of my commitment to FIRST Team 971 I agree to the following:
I understand that the Leadership Council has final authority over all matters related to the team. I understand that leadership meetings are open, and that if I have an opinion I should bring it to the attention of the leadership for consideration.
I agree to practice Gracious Professionalism in all my interactions with other team members, mentors, parents, and other teams.
I agree to take an active part in the team. I agree to work hard, show up at meetings, be willing to learn, and be open to new ideas.
I commit to good attendance and punctuality. Absences and tardiness may result in loss of team privileges. I agree to notify the team leadership in advance if unforeseen circumstances prevent me from meeting this commitment.
I understand that the team expects me to contribute at the highest level of my ability, and that in order to be an involved member of the team I understand that I need to make a commitment to spend a minimum amount of time at meetings. If at any time I have a problem meeting team expectations, I agree to discuss with the team leadership in order to resolve the situation and ensure that both the team and I are benefiting from the relationship.
I agree to discuss my expectations for my involvement in the team with the team leadership. If at any time during the season I am having a problem with another team member or with the team, I agree to bring this to the attention of the leadership.
I understand that there are many skills required for a successful robotics team. I agree to work with the team leadership and the mentors to find a position that I find fulfilling and fun.
I agree to comply with all safety rules posted by the team leadership without exception. Safety is everyone’s first priority, and everyone needs to be looking out for potentially unsafe situations. Unsafe situations must be reported to adult leaders. Repeated unsafe behavior will result in dismissal from the team.
All team members (students and mentors) are expected to follow the rules listed below. For the benefit of the team, violations can result in loss of privileges and removal from the team.
The drive team is the subteam that includes the driver, manipulator, coach (typically a seasoned mentor), and human player. Being on the drive team is the icing on the cake rather than the main meal. Students that significantly contribute to the team in terms of management, design, building, programming, and such will be given preference for being on the drive team. Students in any grade are encouraged to be active contributors to the team in all areas, including being on the drive team. Students interested in being on the drive team are encouraged to talk to the mentors and students organizing the drive team if they have questions or need more information. The 971 team fields high performing robots and works hard to field high performing drive teams to drive the robots to victory.
Drive team selection is a process that happens every year. If you are interested in being on the drive team, first start by reading and understanding the Drive Team section of the team expectations web page.
The competition drive team is selected at the end of the build season. Selection is based on more than just driving skill, and includes consideration of students’ involvement and interactions on the team throughout the year. Students need to demonstrate involvement on the team outside of drive practices if they would like to be considered seriously for drive team selection. The selected drive team is responsible for preparing for and competing in all in season and off season competitions for that season year. This selection is nominally re-done on an annual basis.
Our expectation is that the drive team is consistent throughout this duration, but there are exceptions where this may not be the case. The drive team is expected to operate according to the drive team expectations, and members will be removed if they are not following these expectations. Also, being on the drive team is not for everyone. Sometimes it becomes clear to the mentors that someone else will serve the team better, and in these cases drive team members will be replaced.
We do not hold tryouts during the build season. Instead, we base driving skill assessments off of off-season competition and practice performance. The team takes three robots to the Madtown Throwdown in November, which allows us to select two additional drive teams for this event. Also, the drive team for the competition robot sometimes has students graduate. When this happens, we hold an additional selection process to backfill those positions before our first off-season. We hold multiple open drive practices leading up to the selection of these drive teams in order to give everyone a chance to gain experience driving the robots.
Our general process for off season drive team member selection is as follows. We start with open drive practices to give everyone a chance to learn. We then have an open tryout where everyone trying out performs some task. We may or may not have multiple phases of narrowing, where extra consideration is given to a subset of candidates. The amount of time spent in each phase depends on how much time is available, and how much time is judged by the mentors to be appropriate. This selection process for the additional Madtown Throwdown drive teams usually starts with open practices in the summer and finishes in October.
For Madtown, members of the competition robot drive team may be interested in trying other roles within the drive team. They are welcomed to try out for these roles. If they are selected for a different role, their position with the competition robot will be backfilled through the same selection process.
Selection for the 3rd robot drive team is more heavily weighted towards involvement during the design, manufacturing, programming, and assembly of the 3rd robot, over involvement throughout the rest of the year. The 3rd robot drive team is not selected until after the 3rd robot is ready for drive practice, and the selection process may be compacted based on how much time is available.
Version 1.4 - Travis, Michael, and Kevin 8/13/18 - Added drive team selection process.
Version 1.3 - Wyn and Finbarr 10/15/13 - Updated the text and removed Draft.
Version 1.2 - Draft by MJS 3/9/13 - Added Drive Team section.