Presenter bio »

PDI-5: STEM Programming 101: Creating Integrated STEM Programs

Wednesday, April 10, 2013
9:00 a.m.–4:00 p.m.
Conference Room 3 and 4, Marriott Rivercenter Hotel
Cost: $150
Limit: 80
Grades: K–12

Recommended Pathway Sessions

Provider: International Technology Engineering and Education Association (ITEEA), Gaithersburg, Maryland

Framing Questions / Outcomes

1. What is the difference between STEM, STEM education, and integrative STEM education?
2. What is STEM literacy and why is it important for all students?
3. Why should STEM education be included at all grade levels, and what should it look like?
4. How do I use the Grand Challenges for Engineering to provide a meaningful context for learning?
5. Why should I and how do I integrate inquiry, design, problem-solving, and literacy strategies in one unit?
6. With so many definitions of STEM, how do I create an action plan for my school or district?

PDI Summary

What does it take to create a STEM Program? Using the Common Core State Standards, the Standards for Technological Literacy, and the Grand Challenges for Engineering, participants will understand the integrative nature of K–12 STEM and how Engineering by Design can be the basis for developing the practices of engineering and concepts outlined the NGSS framework. This PDI will focus primarily on helping educators, schools, districts, and states to understand that all four components of STEM build a framework for students to understand how the natural world and the designed world coexist and how human wants and needs drive invention, innovation, and thus engineering. Examples of successful programs will be used as jumping off points that point to the integrative nature of STEM rather than the "SILO" approach to STEM. Participants will be experience interactive activities that draw upon their prior experience and stretch their STEM thinking. Ultimately, participants will leave with new knowledge and skills to plan a true STEM program in their classroom, school, or district.

Register Now!

Joey Rider-Bertrand describes this session:

The player will show in this paragraph