2017 FIRST STEAMWorks Resources

2017 FIRST  “STEAMWorks” Resources

2017 STEAMWorks Game Manual

Rules Quiz

Demand Prefer Wish Example and Template

STEAMWorks Reveal Video

Key Info

Field Diagram

Air Ship

STEAMworks Kickoff Agenda

Breakfast 6:30 – 7:30

  • Food is available for Team 3309 in the Priory Dining Room
  • Members, get your food and head over to the classroom to eat.
  • Make sure you’re in the theater by 7:30

7:30 Kickoff Live Stream in the Theater

Explore Field and Mingle

  • Explore the field in Robodome
  • Mingle with the 30+ teams here for kickoff

9:30 Initial Reading, Quizzes

  • Begin reading rules
    • First Solo silent read (Library)
  • First Solo Quiz
    • Take Quizzes at your own pace (online quiz)
      • When the quiz is ready, we will make an announcement
      • First time no manual
      • Feedback and multiple attempts (can use manual on other attempts)
      • Students and mentors have to correct the ones they got wrong
      • Take notes to help
  • Second Reading/Second Pair Quiz Attempt
    • May discuss in pairs
      • Focus on highlighting rules
      • No off-topic discussions
      • Library environment
  • If you have extra time, write up quiz questions of your own for a refresh quiz we’ll send to the team later

12:00 to 12:30 Lunch on the Patio

12:30 Team Discussion and Q&A

  • Full team rules discussion
  • For people that have questions
  • Time to clarify (emphasize any critical or tricky) rules with team
  • Make sure we are all on the same page
  • Clarify most missed questions on quiz
  • Note possible questions for FIRST Q&A

2:30 Field Time

  • Time to get hands on with the field knowing the rules
  • Record times for humans enacting game actions
  • Game objects

3:00 Small group time

    • 3-5 students
    • Each group has one mentor, one VP level member of leadership, and other team members.
    • Strategy Oriented Discussion
      • What are your initial reactions?
      • How do robots score the most?
      • What should robots on an alliance do?
      • What is a perfect robot capable of?
      • Is a defensive robot effective?
      • What key actions would cause a robot to rank high in qualifications?
      • Are there key strategy differences between quals and elims?
      • Are there any “game changing” strategies?
    • DO NOT Discuss: Mechanisms, Software, Design
    • When you present, make sure to explain your reasoning

4:30 Full Team presentations

  • Small Groups present to team
    • Skip or summarize ideas that are identical to groups that already presented
  • Note taker takes notes + combines small group Google Docs into one team Google Doc
  • Several minutes for questions after each group presents

6:00 Dinner on the Patio

6:45 Small Group Design Requirements 45 minutes

  • Make a Demand Preffered Wish list:
    • Demand: Our robot will have it
    • Preferred: Possible, achievable goal for our team
    • Wish: A reach for our team, not as important, but would be nice
  • Small groups work on their own matrix
    • What should our robot do? (WHAT not HOW)
    • Fill in your own spreadsheet following the example given.
    • Why do certain tasks have more value?
    • Consider: Defense, Autonomous, Endgame

7:45 Presentation and Discussion

  • Small Groups present to team
    • Skip or summarize ideas that are identical to groups that already presented
  • Team discussion to develop a “master” matrix
  • Decide as a team like last year
    • Which capabilities will we require
    • Which capabilities are priorities

8:45 End of Day

Field Diagrams

(Not yet available)