Rss

  • youtube
  • google

2016 Working Agreement

2016 Working Agreement
This working agreement is for the team of students selected for the 6 week competition robot build season in January and February to build the FRC competition robot. This working agreement was drafted by the student leadership team from last year, and is indicative of the commitment that is necessary by all team members through this intense build season.

Meeting Times:
All those on the January/February competition build team can commit to the following
meeting times.:
Monday, Tuesday, & Thursday evenings:
Check in at 5:45 with work going from 6:00PM -8:00PM
Saturdays: 9:00AM- 3:00PM
There will be some build sessions on weekdays days that we do not have school in session.
For the full calendar, see the “Team Calendar” tab at the top of the MarsWars.org website.

Attendance:
We know that conflicts may arise and thus ask that team members attend at least 80% of
the weekday evening build sessions and at least 5.5 of the 7 Saturday build sessions.

Definition of On Time:
Team members are also asked to commit to being on time and staying for the duration of
build sessions or as otherwise decided by individuation sub teams. Arriving late or leaving early will constitute as an absence.

Notification of Absences:
Absences must be posted prior to the meeting time (the sooner the better). This is important so that team leaders can plan daily build sessions accordingly.
Absences should be posted to the “2016 Build Season Report Absence” link that is found under the “Quick Links” section of the team forum.

Expectations while in working sessions:
Responsible phone usage
Knowing what you’re going to be working on before coming to the build session
Not being on Youtube or other computer games

What do I do if my main role on the team is not currently active or I do not have anything to do?
There is always something that can be done to help the team, and we expect everyone to step up and stretch yourselves. Part of committing to this varsity level competition team is being able to be self directive. We expect team members that are active in this varsity level group to see projects through completion and find additional projects to work on. Also, as a member of this varsity level group, if a mentor asks you to complete a task, we expect it to be completed regardless of how enjoyable it is. Often times, past team members have found fun ways to approach even the menial tasks. Loitering in hallways or classrooms, “hanging out”, or not being productive is not an option. If this becomes a pattern with team members we will ask them to not return to the competition build season as there is time during the rest of the year to be involved in other robotics activities.

Competition Attendance:
Team members need to keep their commitments to be eligible to attend competitions with
the team. This means that it is possible for a robotics team member to decide not to try out for the January/ February varsity level competition group, but still attend the local competition with the team.

Other Extracurricular Activities:
Students who compete in the varsity level January/ February competition build season are
asked to consider their other extracurricular commitments prior to the season starting. Please do not take the place of another student if you cannot commit to this working agreement.

2015 Mars/Wars Team Structure

Mars/Wars 4143 FRC Robotics Team
Clay Barlow
Andrew Barth
Willie Barth
Jeanine Beaver
Kadin Bertsche
Carston Boast
Josh Clasen
Matthew Croutteau
Garrett Dominy
Daniel Ernenputsch
Cassy Fitzgibbons
Jenna Gardner
Blake Glueck
Ben Hahn
Becca Harris
Kaleb Johnson
Clay Jones
Jarrett Khattar
Alonzo Kiefner
Baillie Larson
Cory McHugh
Ryan Meyer
Nick Meyer
Sam Nauman
Paul Nauman
Cade Neumann
Victoria Northrop
Payton Piercy
Ben Poling
Jordan Reese
Jan Rollings
Skai Salmon
Christian Sauder
Lee Schmidt
Seth Tealbey
Brody Webster
Austin Wernsman
Anthony Wessel
Matt Wipfler
Mars/Wars Varsity Build Team
Andy Barth
Willie Barth
Jeanine Beaver
Carston Boast
Josh Clasen
Garrett Dominy
Cassy Fitzgibbons
Jenna Gardner
Becca Harris
Kaleb Johnson
Jarrett Khattar
Alonzo Kiefner
Baillie Larson
Ryan Meyer
Nick Meyer
Paul Nauman
Sam Nauman
Cade Neumann
Jordan Reese
Jan Rollings
Skai Salmon
Seth Tealbey
Austin Wernsman
Anthony Wessel
Matt Wipfler
Mars/Wars Varsity Build Team Mentors
Joe Bachman
Keith Barth
Charlie Brown
Jim Datillo
John Gardner
Amy Gardner
Keith Gargiulo
Julie Johnson
John Johnson
Evan Johnson
Kevin Meyer
Ryan Noe
Jon Salmon
Ryan Shoff
Dick Steele
Brian Stoecker
Ray Tealbey

Mars/Wars Galactic Council
Jeanine Beaver
Jenna Gardner
Jarrett Khattar
Nick Meyer
Jordan Reese
Seth Tealbey
Matt Wipfler

Mars/Wars Leadership Team
Joe Bachman
John Gardner
Julie Johnson
Ryan Shoff
Brian Stoecker

2015 Build Season Mentor Working Agreement

This working agreement is for the mentors of students working on the 6 week build season to build the FRC competition robot

Working session days/hours
Monday, Tuesday, Thursday 6-8pm
Saturday 9am-3pm

Commitment to students
1. Start each session with review of goals, milestones and activities with your student working group

  • What did you work on last time
  • What are you working on next
  • What is getting in your way of completing it
  • Fully defining what is to be done before starting activities

2. Defining what ‘Done’ means for project student is working on – definition of done (DoD)
3. Having students documenting what has been be done on their activities in Trello
4. Coordinate any unscheduled meetings with student working group as needed

Attendance
Manage personal attendance in Mentor availability spreadsheet
mentor.marswars.org

  • Attend any meetings you are scheduled (S) to attend
  • Update your scheduled  sessions as changes occur in your availability in Mentor spreadsheet
  • (A – Available, M- Will Miss Scheduled, L – Will be late for scheduled)
  • Last minute scheduling issues text to Mars/Wars
  • Arrive on time

Trello – Team Activity Management Tool
1. At any time – students and mentors are only working on items that are defined in Trello and are listed under a sub-group
2. Team Support mentors and Galactic Council focused on continuous grooming of Trello backlog

  • Further refining detail in activity
  • Continuous re-prioritization

3. Trello items are not moved to a sub group until they are Ready.

  • Definition of Ready – (can move to Ready column)
    • Description of what needs to be done
    • Sub-group assigned
    • Due date assigned
    • Definition of Done (DoD) noted in description or checklist
      • Clear and concise list of requirements that the activity must meet for the Sub-group to call it complete
  • Before Trello items are moved to a sub-team to be worked on
    • Students and a mentor assigned
    • Student responsible for updating the status noted in description

Purchases
List purchase requests or items purchased in the google doc located at purchase.marswars.org

2015 Galactic Council Responsibilities

Galactic Council Responsibilities :
(Responsible for, but not the only one working on these items)

Planning, managing sub-team assignments – Jenna

Conduct status review sessions, maintain ready task list in Trello and ensure status updates are kept up

Open House – Jenna

Coordinate open house assignments, visitor flow and presentation material

Awards – Nick

Develop timeline, milestones for:

  • Chairman’s
  • Dean’s List
  • Judges Book

Social Media – Nick

  • Web site articles
  • Collect, compile and distribute video
  • Tweets for special events
  • Manage team Facebook page
  • Thank you responses for sponsors and volunteers

Software – Seth

Install software on new laptops, apply updates when new software available.
Timeline, milestones for documenting a process to create an account and install software for:
Documentation completed by year end 2014

  • Windchill
  • MeshCAM
  • Creo
  • AutoCAD
  • Eclipse
  • Github

Pit Master – Jarrett
Pit layout, setup dry run and banner structure complete by year end 2014

  • Design
  • Prototype setup with banners and structure
  • Electrical layout
  • Carts/storage needs
  • Tower contents
  • Organize transport and setup/tear down of pit at competitions
  • Rules around what gets stored in pit area, people in pit, pit crew and cleaning assignments for competitions
  • 10 minute pit

Safety – Jeanine
Safety test given by Kickoff

  • Safety test
  • Shop tour
  • Document procedure if someone has an accident, review with team
  • xxx Days since last accident poster, update
  • Policy for who can use what tools
  • Competition safety kit, documentation

Captain Cleanup – Jordan

  • Bell for cleanup 10 min before build session ends
  • In charge of keeping cabinets and tools organized
  • All tools and material put away by end of session, anyone wanting to continue work can get their material out again after all clean up

Fundraiser – Jordan
Run 2 IGA fundraisers by Kickoff and collect bulb sales due by Kickoff

  • Organize students for light bulb sales 10 per student or attend sales event
    Required : sell 10 light bulbs or work light bulb sales event or pay $70
    fundraiser covers team attire
  • Organize any additional fundraiser such as batteries

Driver Selection Process – Matt
Driver test criteria documented and put on Mars/Wars storage google drive by year end 2014
 

FUN – All

  • Cow Bell (or other equivalent) for cleanup notice
  • Once a week surprise visit by mascot for team member interviews (having fun with this, be sure to record)
  • Sub-Team challenges (details to be determined)

 

Draft – 2015 Build Season Team Working Agreement

We have a Mars Wars team which has opportunity throughout approximately 46 weeks during the year in Robotics to participate, go to off-season competitions, etc.

This working agreement is for the team of students selected for the 6 week build season to build the FRC competition robot also known as the Varsity Build Team
This working agreement is owned by that team and will be agreed upon by the entire build season team, if a new team member comes onto the that team, will need to revisit

Working session days/hours
Monday, Tuesday, Thursday 6-8pm

      5:45-6:00pm students are expected to be signing in and in their working areas or meeting rooms
      6-8pm working with full mentor involvement

Saturday 9am-3pm

Team Meetings
Startup/Cooldown Meetings – sub-team share efforts

      Saturdays after lunch
      Monday 5:45-6pm

Quick Standup Meeting

    Tuesday and Thursday 6-6:05pm

Meals
Asking for parents to signup to provide meals on Saturdays

Expectation while in working session
Responsible phone usage
Knowing what you’re going to work on before you come in
Not on youtube or playing games

Communication about changes in meeting times / snow days / locations
Remind Text
Forum Announcements
Web site parent section

Attendance requirements
Attend 80% of scheduled meetings (attend entire meeting)

Definition of on time
In the meeting room or with your sub-team by stated start time

Track attendance
Sign in Sheet
Sign in before scheduled start time

Forecast absence
Text any know absences to team Voice number with: Absent – Full Name and Date
or
Enter absence on the team forum under the “Report Meeting Absences [Team Only Access]” forum (must be logged into the forum to see that option under the Administration category)

Sub-Teams

      Mechanical
      Modeling
      Electrical
      Programming

Track and manage team activities
Manage all team activity in Trello, display on TV in team area

Drivers
Selected by week 3
Signups by week 2

Fund Raising
Attend a fund raiser event (IGA, etc) or sell 10 bulbs
Participation highly recommended for team members
Participation entitles member to team jacket

Travel to competitions and participate with build team
Meet the 80% attendance requirement (must attend entire session)

Interviews
Format – student and mentor or board of mentors
Questions: Availability, interests, why do you want to be there

MarsWars Social Media Policy

MS Word Version – MarsWars Social Media Policy

MarsWars Social Media Policy

MarsWars.org
• Information posted online is to be written by students, but approved by a mentor. This is maintained by restricted access to the account password. . Recognition of sponsors, promoting MarsWars and FIRST, and information sharing are the primary purpose of the team account. The web site will provide an online history of the team and it’s activities. It will also be used to communicate with parents and sponsors. Public Comments will not be allowed on the website.
• Each season, there will be a student designated to ensure MarsWars.org is kept up to date.

Twitter
• Tweets to be written by students, but approved by a mentor. This is maintained by restricted access to the account password. Recognition of sponsors, promoting MarsWars and FIRST, and information sharing are the primary purpose of the team account.
• The goal is to tweet weekly during the school year with more frequent tweets during build season and competitions. Tweets may be suggested by any students or mentors. If there is no suggestions in a given week, a designated student will write a tweet for posting. Video links will either be from MarsWars.org or the team YouTube channel.
• MarsWars will not follow any students and will only follow individuals if there is a business case for it. For example, following Woody Flowers would be acceptable. The primary accounts to be followed are other FIRST Teams, sponsors and potential sponsors and educational institutions.

Facebook
• The MarsWars facebook page will be a public page. Posts to be written by students, but approved by a mentor. This is maintained by restricted access to the account password. The goal is to post weekly updates of what the team has been working on. This can be done by writing a summary or providing links to MarsWars.org or the teams YouTube Channel. Video links will either be from MarsWars.org or the team YouTube channel.
• The goal is to post weekly during the school year with more frequent posts during build season and competitions. Posts may be suggested by any students or mentors. If there is no suggestions in a given week, a designated student will write a posting.

• Recognition of sponsors, promoting MarsWars and FIRST, and information sharing are the primary purpose of the team account.

YouTube Channel
• The MarsWars YouTube channel will be open to the public and will have all posts approved by a mentor. This is maintained by restricted access to the account password. Recognition of sponsors, promoting MarsWars and FIRST, and information sharing are the primary purpose of the team account.

Texting
• Texting between mentors and students will be limited to official MarsWars communications that cannot reasonably be done during build sessions
• Remind.com may be used for reminders of build sessions and as a way to mass communicate with the team.

Other Social Media
• At this time, the team will not have snapchat, Instagram, or any other social media accounts.