Quote:
Originally Posted by Andrew Schreiber
Let's talk about the hierarchy of needs for teams.
1. Build Robot
2. Build functional Robot
3. Build reliable Robot
4. Build elimination caliber Robot
5. Do other stuff a team should do
|
That hierarchy is great for you. Glad you shared your experience.
Please don't assume that what works for your team works for all teams (seems like I've seen that on these message boards before...?).
Our current team hierarchy
1. Develop student skill sets
2. Create awareness of opportunities beyond high school
3. Build a Team
4. Create community awareness of team & program
5. Post snarky responses on Chief Delphi
The robot, and any successes from it, are byproducts of these Needs.
Edit: Why is "STEM is too hard" a bad thing?