Writing in a STEM Classroom

http://www.flickr.com/photos/us-pacific-command/

Yesterday my students took final exams in two Project Lead the Way classes:  Introduction to Engineering Design (IED) and Digital Electronics (DE).  Their exams consisted of a writing prompt with the requirement that they write at least one page, they use introductory and concluding paragraphs, and that they use proper spelling and grammar.

For the IED exam they were told to underline the steps in the 12-step design process, underline key terms in the process of Reverse Engineering, and underline the words Planned Obsolescence and Perceived Obsolescence when they were used.

I could have easily had them do a multiple choice test on processes in CAD programming, steps in the design process, and the difference between Planned and Perceived Obsolescence.  But what would that have told be about their real understanding of these terms?

Too often, as STEM teachers, we get to hide behind solving problems and we let the writing and reading part of education be allocated to the English teachers.  We forget that we have college degrees and we had to write papers and we had to read A LOT in college.  Our students need writing and reading preparation so they can go to the best science and engineering schools and do well.

(Insert Sea Story here: )  I remember being a Main Propulsion Assistant, in the Navy, and having the Chief Engineer always (not once or twice but always) ask me what the tech manual said about the problem we were having with the pumps, turbines, or other mechanical equipment in our engine room. I would have to bring the tech manual and I was expected to have read the manual, understood what was being said, and be able to explain it in layman's terms to the Captain. This was true even though I wasn't the person doing the repairs.  It was my people doing the repairs and I was expected to understand the problems.  If I weren't a good reader I would have never made it in that job.

And so, whenever possible, I intend to be a better teacher by having my students read and write.  Not having them write in every class is a disservice to their future.  The English teachers can work on making sure they understand the nuances of style or various grammar rules.   We can be the ones who make sure they are practicing their skills.

(Insert first year teacher story from 1994 here: )  At a faculty meeting during my first year of teaching we were discussing having students write more across all of their courses.  The curriculum person stood in front of us and told us "of course, if you aren't an English teacher you can't grade them on grammar and spelling."  My hand went up faster than a SM-2ER missile.  "If some kid gives me a paper that is written poorly it is going to be marked up like a bloody mess!"  (That was before we became a gentler profession and we got rid of red pens for grading.)

We are professionals.  We have accumulated, in most cases, multiple hours of classes that required us to write and to be graded on our writing.  Yes, some teachers are NOT great writers but that doesn't mean they can't demand good writing from their students.  Make your students write.  You owe it to them.

You Need to Teach How to be in a Group

http://www.flickr.com/photos/davidquick/

     Next week is our first week of school and that means, yet again, we need to teach our Freshmen how to work in a PBL environment.  When every class is being taught this way it means that in every class they will be working in groups of 2 to 5 people.  In some classes they may have to be a group leader.    In other classes they may have specific roles to do.  In yet another class they may just be working in a collaborative role.

     When students get to us they don't, usually, understand how to work in a group.   There are assigned roles with individual responsibilities and expectations.  There are also expected behaviors of each member of the group and behaviors by the entire group.

     Last year we came across a Ted Talk by Tom Wujec where he described a challenge (presented by Peter Skillman).  This is now, famously, known as the Spaghetti Challenge.  Here is a great video to show what a typical classroom is like in the last few minutes of this challenge.

     The rules are simple and we like to present the challenge as an engineering design brief (got to get the vocabulary started too).  During the first day of class they are given the challenge.  The next day we introduce roles and the students break up into expert groups based upon their roles.  The roles are Designer, Tester, and Builder.  Therefore the expert groups are the Design Team, the Test Team, and the Build Team.  Before the expert groups get started we reflect on what we observed the previous day.  What went well?  What hurdles needed to be overcome?  What frustrations did they feel?  And other thoughts as they come up.  We then ask how we could make the experience better.

    On the third day the expert groups have a quick meeting and then the students are sent back to their original groups to make the tower.  The groups are reminded that each person in the group has a role and they are not to do anything that isn't specifically related to their role.  Once the challenge is completed we take measurements but instead of a "winner", based upon height,  we recognize groups that worked well together.  We take time to talk, again, about what worked and what frustrations were felt.

     By the end of these three days, the students have learned most of the other students' names and (more importantly) I know many of the students' names.  They have also worked in groups where no one is assigned as the "group leader."  Each of them has had an important role that was needed for all of the group to be successful.  Finally, they have seen what group relationships worked and what relationships were not as effective.