FIRST ® LEGO® League Coach/Mentor Workshop Snoqualmie Robotics FIRST ® LEGO® League Coach/Mentor Workshop June 17, 2017

Agenda Introductions FIRST ® LEGO® League Forming your team Equipping your team Managing your team Progressing with your team Competing at the tournament Final Tips

The FIRST ® LEGO® League Team Experience Sport for the minds for youngsters (<14 years old) Miniature engineering project team stressing Creativity and teamwork Engineering principles: requirements, alternatives, rapid prototyping, testing, … Hands-on problem solving Context is a real-world situation Illustrates multiple roles: Designers, Builders, Programmers, Sales and Marketing Insights into possible careers

FIRST ® LEGO® League Team Costs Start-up Costs FIRST ® LEGO® League EV3 Robot Set: $500 Materials for table: Around $100 Yearly Costs FIRST ® LEGO® League Team Registration Fee: $225 Washington Tournament Fee: $325 Challenge Set: $75 Misc. including batteries, shipping: $50-$100 First-year total: ~$1400 Subsequent years total: ~$850

Possible Sources of Team Funding Team Member Dues Having some portion of costs picked up by team members gives a sense of commitment Fundraising Activities Team Sponsors OSPI/FIRSTWA.Org Financial Support 5 5

The Team Timeline April – Sept.: Teams form Registration with FIRST ® is open now – registration materials found on FIRST ® website Mid May: Robot kits begin to ship Mid May: Applications for FIRSTWa Team Financial Support are available July – Aug.: Challenge Sets begin to ship Aug. 29: The Hydro Dynamics Challenge is released Teams develop their solutions for ~3 mo. Culminating event is the Tournament Qualifying tournaments in early December Championship tournaments in January

Plans for 2017 Theme: Hydro Dynamics ~500 teams with more than 4000 youngsters Around 24-26 Qualifying Tournaments Held first two weekends in December 40-50 teams per tournament Expect same locations as last year 2 Championship Tournaments of about 60 teams each in January, 2017

Forming Your Team More retails

Not a Drop-In Program This is a project oriented program Parents and team members need to understand the commitment required Team members need to be available on a consistent basis to move their parts of the project forward from the first meetings through the season-end tournaments Ask kids for their level of comittment

Team size High initial interest may fade Sub-teams of 2-3 can work in parallel Experiment with prototypes Learn programming techniques Work on the project Maximum team size allowed is 10 5 to 7 team members is probably ideal

Where to Meet Large enough space to handle the number of youngsters on the team Space for challenge field setup – 4’x8’ Access to a computer Storage space between meetings Challenge table Partially built robot LEGO parts

You Need Adults, Too! Coach – The person in charge Organizes the team Does not need to be a techie Mentor – The technical guru Provides technical advice Provides the technical basics One person can play both roles But, don’t go it alone Recruit other adults to supervise sub-teams

Coach – The Person in Charge Single point of contact for team Understands the FIRST ® LEGO® League and FIRST Washington programs Management expertise more important than technical expertise Point of contact for FIRST® and FIRSTWA info Recruits the team Registers the team Arranges for equipment Schedules meetings Sets the philosophy and instills team spirit Is a good role model Use web sites ortop and fll

Coach – Need to know Responsible for ensuring the Team knows the rules and requirements for the current year’s Challenge Details on FIRST® website: http://firstlegoleague.org/challenge/thechallenge Be sure you access the following key elements: “Robot Game” Includes Field Setup, Missions, and Rules “Robot Game Updates” Provides detailed interpretations and rule changes for missions and game rules. Updated frequently throughout the season, until Friday of Tournament weekend. Project Generate and share an innovative solution to the Challenge theme Core Values Judging rubrics

Coach: Set Team Goals Scale to experience level of team Samples Learn to program (...learn to use subroutines) Learn about (topic of year) Participate in tournament Complete at least 1 mission (more for experienced teams) Everyone participates HAVE FUN! Not to many missions

Mentor – The Technical Advisor Technical Advisor to assist the coach Facilitates both robot design and programming skill sets Helps set achievable goals Encourages structured problem solving Follow typical engineering project models Experiment with one variable at a time Graduates of FIRST ® LEGO® League can work as mentors

General Advice to All Adults This is the kids’ project, not yours Be a good role model Keep a positive attitude Encourage teamwork and insist on mutual respect Don’t over emphasize “winning” – demonstrating a solution at a tournament is success Have fun Emphasis star

FIRST ® LEGO® League Core Values We are a team. We do the work to find solutions with guidance from our coaches and mentors. We know our coaches and mentors don’t have all the answers; we learn together. We honor the spirit of friendly competition. What we discover is more important than what we win. We share our experiences with others. We display Gracious Professionalism™ and Coopertition™ in everything we do. We have fun. Kids will learn + poster

Equipping Your Team

Minimum Resources to Start A robotics kit Reasonably equipped computer A place to meet and practice Classroom Family room Garage Community Room Win 8 and mac No tablets though

Allowed Robot Parts EV3 controller (1) EV3 motors (4) As many sensors as you like but only from this set – touch, light, color, rotation, ultrasonic, and gyro They must all be LEGO-manufactured MINDSTORMS sensors Note: The HiTechnic color sensor is not allowed  Be sure to check the rules for this year for any changes   21 21

Team Uniforms?? Many teams do something for the tournaments Team shirts, hats, etc Theme clothing Team sponsor advertising on a T-shirt, etc. is OK Helps adults keep track of team

Managing Your Team

You Have A Team, Now What? Divide the season Build A Foundation Address the Challenge Get It Done Practice like the Tournament Participate in Tournament (Judging and Field Challenge)

(Approx) Field Challenge Timeline Assume 12 week season (24 meetings) 4 weeks: Build Foundation 6 weeks: Complete Challenge 2 weeks: Practice / Minor changes You may need to adjust these suggestions based on the time you have available to meet with your team

(Approx) Research Project Timeline 1 wk: Basic Research 2 wks: Narrow and Select Project Topic 1 wk: Focused Research 6 wks: Conduct Project / Prepare Presentation 2 wks: Practice and Present to Others These tasks run concurrently with the Field Challenge Timeline on the previous slide Use the DVD from registration or look online at usfirst.org

Meeting Organization How often and how long to meet Most teams meet 1-3 times per week After school, evenings, weekends as team desires Some add extras as get closer to end > 1 hr (set up and take down) < 3 hrs (attention span) At least 2 adults present during meetings – can use parents who take turns Set ground rules -- E.g. don’t turn kids loose to walk home by themselves after dark Refreshments / snacks ??

Team Kick-off Meeting Welcome parents/guardians Set expectations with kids and adults Send kids off to build with LEGO parts Get assistant to help Use EV3 assembly booklet to build something Something they can all do at once Explain the real situation to the parents

Parent Involvement Explain program/FIRST ® LEGO® League philosophy Success = Participation Explain team rules (attendance, respect, ...) Discuss participation commitment for kids Review costs and funding sources Communicate about tournaments Solicit help

Progressing With Your Team More retails

Multi Dimension Developing the goals/strategy for the season Building the Robots and the attachments Programming and testing Fine tuning the approach Defining and handling the science project Field visits and outreach are critical parts of the program and experience Instilling Core Values

Address the Challenge Team decides how to divide responsibilities A) Builders / Programmers B) Mission based (build/program by mission) C) ?? Need duplicate coverage for illness/absences Probably want area specialists (build, program, research, etc.) BUT Recommended ground rule: Everyone contributes to all aspects of team’s work

Foundation: Engineering Design Process Want consistency 9 out of 10 runs work…. Fewer missions and better success

Build a Foundation Introduce techniques and concepts Build or bring demos Discuss advantages and disadvantages Let kids figure out how to apply concept to Challenge One approach: use 5-10 minutes at start of each meeting to introduce concepts Pick 1-2 subjects per session Can be more for first meetings / new teams May stop about ½ way thru season – A bit late to incorporate new concepts unless they are stuck

Foundation: Sample Concepts Pick one or two new subjects per session Structural strength: bracing vs. snapped pieces Gear ratios: torque vs. speed Traction: tracks vs. wheels Friction: tires vs. skids Programming techniques: linear vs. loops vs. subroutines (MyBlocks)

Foundation: Mechanics Robot basics: have team evaluate 2-3 different robots with instructions Discuss the engineering criteria and constraints based on the challenges (space constraints, navigation challenges) Discuss trade-offs (+/-) of each robot model Team decides/combines for challenge robot Gives team design tradeoff experience Build Field Kit Dedicate 1 meeting, divide up elements Ad hoc extra meeting for leftovers

Foundation: Divide and conquer Three basic robot functions: Locomotion: how the robot moves Concepts: motors, gears/pulleys, wheels/tracks, friction, steering Navigation: how it knows where to go Concepts: time, sensors (rotation, touch, light, ultrasonic, gyro) Robotic Action: function it performs Concepts: pushing, grabbing, lifting , dumping

Foundation: Programming Introduce basic programming Can use Workshop handouts Introduce sensors If meetings start before Challenge is announced, can use mini-challenges to introduce concepts Use EV3 tutorial developed by Dale Yocum, Engineering Program Director at Catlin Gabel School www.stemcentric.com

Address the Challenge Pick up all information about the challenge from FIRST® website when details announced on August 29th Missions Rules Field setup Game Updates (grows during the season) Project – details on research project Core Values Very important to get all the pieces!! Both field challenge and project/research challenge

Address the Challenge Team must learn missions and rules: Send home copy and learn missions and rules Discuss and test understanding at later team meetings Can overlap with ‘build foundation’ meetings You might want to find a “rules expert” among your team members

Address the Challenge Have your team group the missions Members brainstorm/generate prioritized list: Can prioritize group by ease, location, or points Can group by program or trips out of base Individuals present and team selects which to start with Refer to team goals for how many to try Can add more if finish 1st set and still have time

Get It Done Considerations: Introduce “design rule” concept Shared, agreed upon design constants e.g. Motors B/C drive and motor C is on right Which end is ‘forward’ Light sensor is always in port ‘3’ Programs need to share inputs/outputs Attachments need to go together Base robot with quickly interchangeable attachments, or Attachments can’t interfere with those for other missions Target being done early (time for debug/rebuild)

Practice Like the Tournament Field Competition Runs (Follow Tournament Rules) Start with individual missions/groups, then all together 2 ½ min, 2 members at the table at once Practice working under time pressure Switching between missions, programs Try to limit big last minute changes to missions/robot

Practice Like the Tournament Judging Panels (Robot Design, Project, Core Values) Use Coach Handbook rubrics Parents as judges Work on smooth, clear delivery Ask a variety of questions Practice teamwork exercises

Competing @ the Tournament

Project Judging Similar yet different to school science fair event(s) - great learning opportunity Research skills and presentation skills Good engineering requires research and communication Must be a live presentation Format – includes setup time 5 minute presentation, 5 minute interview Posterboards, skits, models, Powerpoint (not the best format, can waste time with setup), . . .

Robot Design Judging Panel of “experts” interviews teams Mechanical: Durability, Efficiency, Mechanization Programming: Quality, Efficiency, Navigation Strategy & Innovation: Process, Strategy, Innovation Prepare the team to: Give a 1 minute overview of their robot design noting “sources of inspiration” Answer questions about the design of the robot and its program Demonstrate at least one mission on the challenge field Bring a printout of the program 47 47

Core Values Judging A separate 10 minute judging session Teams will do a surprise teamwork activity At Championship tournament the teams bring a Core Values “tri-fold” or poster with them and give a short, less than 2 minutes, presentation on the contents Judges interact with teams to evaluate how the teams meet the FLL Core Values

FIRST ® LEGO® League Core Values Best Practices Youngsters design, build, and program their robots Youngsters are responsible for project work During tournament, no adult may touch the computer keyboard, mouse, robot, robot attachments, or project materials. No adult may give specific verbal directives on programming and building or during table competition at a tournament. Tournament guidelines should be in effect at team meetings.

Final Tips

Final Tips: Budgeting Resources Physical resource effectiveness limits: No more than 2 (3 max) at one keyboard No more than 2-3 building one item Can’t research presentation and program robot on same computer at same time Consider time sharing 2 computers, one robot kit; divide team 1/3 building, 1/3 programming, 1/3 researching Rotate during meeting

Final Tips: Set Expectations For a Positive Tone Encourage risk taking It’s OK to fail – they are learning opportunities Key is to manage the risk Encourage experimentation Expect failure – focus on what is learned as a result Problem solving takes time – Edison’s experience with light bulb filament

Final Tips Keep Meetings Fun Be flexible Watch for teaching moments Usually means hands on LEGO building every meeting Be flexible Help keep them on task, but ultimately it is their project The journey is as important as the result (Another way to phrase Core Value #4) Watch for teaching moments Engineers need ‘hard skills’ Mechanical Design, Programming, Analysis, Problem Solving, Experimentation, and Documentation AND ‘soft skills’ Timeliness, Teamwork, Tact and Compromise, Confidence, Courtesy, Perseverance, and Planning