Kick off presentation

1,096
-1

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,096
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Kick off presentation

  1. 1. FRC 2789<br />STAYING SANE<br />2011 Austin FRC Kickoff<br />2/16/11<br />1. Define Problem<br />State a well constrained problem, one that you can solve and document on this page. Clearly state what the problem is, explain why it is important to solve, and describe the benefit to finding a solution.<br />2. Specify Requirements<br />List and describe the requirements that a potential solution to the problem must have. This may include performance numbers, the method of use, accessibility, or size constraints.<br />6. Refine<br />First, state a brief conclusion of what you present. Then, state next steps for the result solution. This may be a need to monitor, maintain, or re-evaluate in the future. Capture the how this work fits into the “big picture.”<br />3. Identify Solutions<br />Describe solutions that solve the problem and meet the requirements. This may be a physical description, a code outline, a page layout, a numbering system, etc. This section should describe IMPLEMENTATIONS in detail.<br />5. Test<br />Describe the methods you used to validate your solution against the requirements during and after development. Explain how you measured success, and what those measures were. This is not necessarily a numeric measure.<br />How to Stay Sane as a<br />FIRST Team<br />4. Develop<br />Explain what evolved out of the solutions you identified, the unforeseen problems you encountered, and how you reached your solution. This section is descriptive, and should include images or diagrams.<br />RELEASE| PROPRIETARY | TEAM CONFIDENTIAL | DO NOT DISTRIBUTE<br />FRC 2789 - Standard A3 Report<br />
  2. 2. FRC 2789<br />2/16/11<br />2011 Austin FRC Kickoff<br />STAYING SANE<br />The Problem:<br />  <br />FIRST is a demanding, multifaceted competition.  <br />Building a team that can build robots & that is about “more than the robot” is very hard!<br />FIRST attracts talented, overcommitted people.<br />Step 1: Define Problem<br />State a well constrained problem, one that you can solve and document on this page. Clearly state what the problem is, explain why it is important to solve, and describe the benefit to finding a solution.<br />RELEASE| PROPRIETARY | TEAM CONFIDENTIAL | DO NOT DISTRIBUTE<br />FRC 2789 - Standard A3 Report<br />
  3. 3. 2/16/11<br />STAYING SANE<br />FRC 2789<br />2011 Austin FRC Kickoff<br /> SHARED CHALLENGES & <br />REQUREMENTS<br /><ul><li>CULTURE: Strong mentor-student relationships; Positive team culture; Engages wide variety of students
  4. 4. PRODUCTS: Competitive robots & awards submissions
  5. 5. MONEY: Financial stability</li></ul> REQUIREMENTS UNIQUE TO OUR PROGRAM<br /><ul><li>Only varsity sport on campus -> high academic & behavior expectations inside & outside Robotics
  6. 6. No on-site machine shop
  7. 7. PBL instruction school-wide means that Robotics is not the only hands-on gig in town</li></ul>2. Specify Requirements<br />List and describe the requirements that a potential solution to the problem must have. This may include performance numbers, the method of use, accessibility, or size constraints.<br />RELEASE| PROPRIETARY | TEAM CONFIDENTIAL | DO NOT DISTRIBUTE<br />FRC 2789 - Standard A3 Report<br />
  8. 8. 2/16/11<br />STAYING SANE<br />FRC 2789<br />2011 Austin FRC Kickoff<br />Potential Solutions:<br />1 – Quit FIRST; opt for something cheaper and easier<br />2 - Focus only on the robot at the expense of team culture<br />3 - Focus only on team building at the expense of the robot<br />4 – Delegate, communicate, and solve problems <br />3. Identify Solutions<br />Describe solutions that solve the problem and meet the requirements. This may be a physical description, a code outline, a page layout, a numbering system, etc. This section should describe IMPLEMENTATIONS in detail.<br />RELEASE| PROPRIETARY | TEAM CONFIDENTIAL | DO NOT DISTRIBUTE<br />FRC 2789 - Standard A3 Report<br />
  9. 9. FRC 2789<br />2/16/11<br />2011 Austin FRC Kickoff<br />STAYING SANE<br />STANDARDIZE <br />4. Develop<br />Explain what evolved out of the solutions you identified, the unforeseen problems you encountered, and how you reached your solution. This section is descriptive, and should include images or diagrams.<br />RELEASE| PROPRIETARY | TEAM CONFIDENTIAL | DO NOT DISTRIBUTE<br />FRC 2789 - Standard A3 Report<br />
  10. 10. FRC 2789<br />2/16/11<br />2011 Austin FRC Kickoff<br />STAYING SANE<br />COLLECT & SHARE DATA!<br />4. Develop<br />Explain what evolved out of the solutions you identified, the unforeseen problems you encountered, and how you reached your solution. This section is descriptive, and should include images or diagrams.<br />RELEASE| PROPRIETARY | TEAM CONFIDENTIAL | DO NOT DISTRIBUTE<br />FRC 2789 - Standard A3 Report<br />
  11. 11. FRC 2789<br />2/16/11<br />2011 Austin FRC Kickoff<br />STAYING SANE<br />DELEGATE & COMMUNICATE<br />4. Develop<br />Explain what evolved out of the solutions you identified, the unforeseen problems you encountered, and how you reached your solution. This section is descriptive, and should include images or diagrams.<br />RELEASE| PROPRIETARY | TEAM CONFIDENTIAL | DO NOT DISTRIBUTE<br />FRC 2789 - Standard A3 Report<br />
  12. 12. FRC 2789<br />2/16/11<br />2011 Austin FRC Kickoff<br />STAYING SANE<br />COMPETING AT REGIONALS IS AN EARNED PRIVILEGE, NOT A RIGHT<br />4. Develop<br />Explain what evolved out of the solutions you identified, the unforeseen problems you encountered, and how you reached your solution. This section is descriptive, and should include images or diagrams.<br />Advancement Requirements Deadline:<br />12/4/10<br />RELEASE| PROPRIETARY | TEAM CONFIDENTIAL | DO NOT DISTRIBUTE<br />FRC 2789 - Standard A3 Report<br />
  13. 13. FRC 2789<br />2/16/11<br />AUSTIN FRC KICKOFF<br />2011 Austin FRC Kickoff<br />TIME MANAGEMENT (OUT BY 7 PM)<br />4. Develop<br />Explain what evolved out of the solutions you identified, the unforeseen problems you encountered, and how you reached your solution. This section is descriptive, and should include images or diagrams.<br />RELEASE| PROPRIETARY | TEAM CONFIDENTIAL | DO NOT DISTRIBUTE<br />FRC 2789 - Standard A3 Report<br />
  14. 14. FRC 2789<br />2/16/11<br />AUSTIN FRC KICKOFF<br />2011 Austin FRC Kickoff<br />EVERYONE READS THE MANUAL !<br />4. Develop<br />Explain what evolved out of the solutions you identified, the unforeseen problems you encountered, and how you reached your solution. This section is descriptive, and should include images or diagrams.<br />RELEASE| PROPRIETARY | TEAM CONFIDENTIAL | DO NOT DISTRIBUTE<br />FRC 2789 - Standard A3 Report<br />
  15. 15. FRC 2789<br />2/16/11<br />AUSTIN FRC KICKOFF<br />2011 Austin FRC Kickoff<br />Determining Success:<br /><ul><li>Did we meet the competition deadlines?
  16. 16. Did we pass inspection?
  17. 17. Did we represent our school well at regional competitions?
  18. 18. Did we minimize the risk of penalties & injuries?
  19. 19. Did we adequately prepare to interact with judges & compete for awards?
  20. 20. Did we collaborate graciously and professionally with other teams?</li></ul>5. Test<br />Describe the methods you used to validate your solution against the requirements during and after development. Explain how you measured success, and what those measures were. This is not necessarily a numeric measure.<br />RELEASE| PROPRIETARY | TEAM CONFIDENTIAL | DO NOT DISTRIBUTE<br />FRC 2789 - Standard A3 Report<br />
  21. 21. FRC 2789<br />Team:<br />FRC 2789 - Standard A3 Report<br />2/16/11<br />2011 Austin FRC Kickoff<br />Determining Success:<br /><ul><li>Did we meet our financial goals?
  22. 22. How many students & mentors did we retain?
  23. 23. What did our students learn?
  24. 24. Did we hold our students accountable to high technical, non-technical & academic standards
  25. 25. Did we have fun?</li></ul>5. Test<br />Describe the methods you used to validate your solution against the requirements during and after development. Explain how you measured success, and what those measures were. This is not necessarily a numeric measure.<br />RELEASE| PROPRIETARY | TEAM CONFIDENTIAL | DO NOT DISTRIBUTE<br />
  26. 26. 2/16/11<br />STAYING SANE<br />FRC 2789<br />2011 Austin FRC Kickoff<br />Ask us at Kick-off 2012!<br />6. Refine<br />First, state a brief conclusion of what you present. Then, state next steps for the result solution. This may be a need to monitor, maintain, or re-evaluate in the future. Capture the how this work fits into the “big picture.”<br />RELEASE| PROPRIETARY | TEAM CONFIDENTIAL | DO NOT DISTRIBUTE<br />FRC 2789 - Standard A3 Report<br />
  27. 27. FRC 2789<br />Team:<br />FRC 2789 - Standard A3 Report<br />2/16/11<br />2011 Austin FRC Kickoff<br />Contact Info:<br /><ul><li>Janice Trinidad
  28. 28. janicetrinidad@manornewtech.org
  29. 29. Bobby Garcia
  30. 30. bobbygarcia@manornewtech.org
  31. 31. www.team2789.com</li></ul>5. Test<br />Describe the methods you used to validate your solution against the requirements during and after development. Explain how you measured success, and what those measures were. This is not necessarily a numeric measure.<br />RELEASE| PROPRIETARY | TEAM CONFIDENTIAL | DO NOT DISTRIBUTE<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×