Friday, August 20, 2010

Feedback: It's a two-way street you know

I've been thinking a lot about feedback and the one-way nature of it in education. Wikipedia defines feedback this way:

Feedback describes the situation when output from (or information about the result of) an event or phenomenon in the past will influence an occurrence or occurrences of the same (i.e. same defined) event / phenomenon (or the continuation / development of the original phenomenon) in the present or future.

In many classes, feedback is a one way process: the instructor provides feedback to the student. Typically the student is only granted the ability to provide feedback on the instructor or the course once (at or near the end of the course). This feedback is then not provided to the instructor until after the course has finished. This implies (based on our definition above) that the feedback can not be used to alter the present state of the course that the students are in. This implies an altruistic impetus to the student to even provide feedback (i.e. I will provide feedback not to improve my own state, but to improve the state of future students). I know in my own experience as a student (anecdotal of course, but illustrative) that I only ever filled in the multiple choice part of a end-of-course evaluation unless I was extremely pleased or displeased with the instructor. In addition, by the time the end of term was rolling around, I had forgotten much of the feedback that I had wanted to share.

Looking at it from the other end, this lack of feedback for teachers tends to reinforce the stereotype that teachers are an irreproachable source of knowledge. Stereotypes tend to be more damaging to the one that is being stereotyped that the one perpetrating them. This lack of constructive, useful, timely feedback encourages teachers to accept and embody this omniscient stereotype, and thus not to attempt to become better. Yes, teachers can self-critique and self-reflect upon their own practice (and they should) and change that way. But the system of not permitting feedback for the teacher does not encourage (and in fact discourages) this self-reflection from taking place; in fact it negates any form of reflection of the teacher upon thier teaching practice. It discourages the teacher from changing; what change could be needed by someone that is perfect? By tacitly neglecting feedback, we tacitly accept the idea that we are beyond change and beyond growth; we tacitly accept the idea that we are not learners as we have nothing to learn.

How do we rectify this disparity in our feedback model. The solution is rather simple: do not wait for the prescribed feedback form to come around; be proactive. The exit card strategy is an excellent means of gaining feedback on the lesson from students:

At the end of each class, students are provided a cue card. Upon the cue card they are asked to record the following: One positive item from the lesson, one piece of constructive criticism, and one thing that is interesting (in essence a form of a PMI). Students should be encouraged to do this every class, and to discuss anything they wish. It should also be anonymous.

In my experience, this must be encouraged every class because as students we are very used to having no voice in how we are taught. This idea is not easily dispelled.

It is vital that constructive criticism is acted upon swiftly. Students will realize very quickly if this is a 'sham' when their ideas are not implemented or discussed. Actively discuss the suggestions in class and your feelings on their efficacy.

As I teach in a computer lab, I have digitized my exit card strategy. I use Google Docs to host a form on my course website. The results from the form are dumped into a spreadsheet (think Excel) for me to process. The link to the form is kept on the website and I provide 5 minutes most classes (as I can be forgetful) for students to submit feedback. Here is a sample form for that purpose.

The speed at which I can adjust the flow of the course is empowering. I benefit as a teacher by knowing that my students are understanding my (and our) ideas for the course. I can also gain valuable insights into how my assumptions on how to teach this class may not match the needs of this class. Perhaps more importantly, it shows my students that I am not perfect; that I am growning and learning alongside them; that I make mistakes. But, most importantly, it illustrates those same points to me.

Sample Forms:
General Feedback Form
Exam Feedback Form

Friday, August 6, 2010

Reflections from Summer Institute for CS Educators

I presented two talks today at the Summer Institute for CS Educators here in Waterloo. The first was on The Effective Use of PowerPoint and the second was about Teaching Programming Through Game Design. I'm just going to jot down a few notes and reflections mainly for myself; if anyone finds them useful that is a bonus.

Effective Use of PowerPoint

I was very pleased with how this went, it could not have gone better. I really slimmed down my presentation from when I gave this talk as a student at Trent. That reductionist approach seemed to be the spark that led to an engaging conversation during the talk. I did not have time to get to the group activity of having the participants 'makeover' some slides I had brought in, but I don't think that was needed. The conversation we had was fascinating. I'm going to attempt to summarize some of the key points that I remember:
  • Too much text leads to us serving PowerPoint during the presentation. We need to ensure that PowerPoint is working for us.
  • Sometimes the best usage of PowerPoint is to not use it at all.
  • Allowing our students to use PowerPoint as a crutch (i.e. by having a text laden presentation that they read) may be great scaffolding to help them get over their fear of public speaking. We just need to remember to remove the scaffolding.
  • Tell your students to 'think graphically' about their presentation.
For next time, I would like to have attendees email me some slides prior to the presentation so I can have time to adjust them and we can discuss the changes during the presentation.

Teaching Programming Through Game Development

I felt a bit hectic in this presentation. It was a difficult arrangement as I was planning on working through a few demos with both Python and XNA, but when I got there I realized that would probably not work due to the differing comfort level with the languages.

Overall I was pleased with this presentation as well. I think for next time I would allow time for brainstorming of ideas of games students can program. Also a focus on how to use gaming to bring in the groups of students not typically represented in CS (i.e. anyone non-white male). I would also go through more of my assignments looking more at the idea of them as opposed to the code. Perhaps a bit more detail on how to develop games in a few other languages (like Java or C++) would be helpful

Feedback

At this moment, I have received approximatly 10 submissions to my feedback form (had roughly 15 in the PPT session and 30-35 in the Game Dev session). The majority of the feedback is for the Game Dev session (I'm assuming that is because we were in the computer lab so they were able to fill the form out right then). Some highlights for changes for future presentations:
  • Show games in Java and C
  • More discussion of simple game ideas (as opposed to the graphical games I'm assuming)
  • Less lecture up front, get to the hands on portion ASAP
  • Time to code in XNA (this one is tricky as XNA has a steeper learning curve)
  • Examples that we can work with that allow us to develop parts of the program or improve it (once again, tricky as it implies a working knowledge of the language. Could have a Python example, Java example, C++ example and have them break off into teams. Would have to brush on my Java ...)
  • Have a break (PPT session) and do some sort of group activity (I agree, I had the idea for the makeover at the end and ran out of time. Perhaps moving that forward)
Overall, I am very pleased that I decided to do both presentations. Next stop .... STAO!

Tuesday, May 4, 2010

Tech Tuesday: Create a Google Doc Form

Ok, I've decided to start a Tech Tuesday portion of the blog. One of my professors at Trent told me about her PD she runs at her school on Tuesdays for 1 hour after school educating teachers on the uses of technology. Since I don't have a school, I figured I would start with the blog.

So, today I want to discuss using Google Docs to create a form/quiz/information gather that also has a chart display for the results. This was definitly the show stealer at my recent OAPT presentation. So, here goes.

1. Get a Google Account. Visit Google and click on Sign In in the upper right corner. On the next page choose Create an Account Now. Your new Google Account gives you access to GMail, Google Docs, Google Reader, and Google Calender to name a few.

2. Click on Google Docs in the upper left (may be under More).

3. In Google Docs, click on Create New and select Spreadsheet. A new window will open. Click Form -> Create a Form. Create the form you are interested in (quiz, introduction form, feedback form). For the purposes of these directions, you will need to create questions that have distinct answers (T/F, MC, likert-style).

4. Back in your spreadsheet (which should now have your questions as column headings), click on New Sheet in the bottom left. This new sheet will be used to tally the results from your form. For this example, I am assuming that you created likert-style questions with a 5 point scale (this works best when all the questions have the same style and scale).

5. The values in row 1 should be the questions from your form (or abbreviated versions of them). The questions should start at B1. In the first column (starting in A2) start the scale for your question.


6. Now, we need to add in some formulas to count the responses. For example, in B2 I add a formula that counts all of the responses to the first question that were 1 (this example assumes you renamed the sheet that stores the data from the form as RawData).

=COUNTIF(RawData!B$2:B$103, $A2)

The COUNTIF function will count the data in the range (the first thing in the brackets) only if the value is equal to the second thing in the brackets. The RawData!B$2:B$103 is the range that the function looks over, cells B2 through B103 (this would allow for 102 responses) in the RawData sheet. The $ in front of the number ensures that the numbers do not change when we fill the equation down. The $A2 refers to the 1 placed in that cell, which is the value we want to count.

7. Fill the equation down by clicking the blue square in the corner of the cell highlight box and dragging down. Repeat for the remainder of your questions (by filling across).

8. Now we need to build a chart for our data. Start by selecting all of the data in the new sheet you have just finished making. Select Insert -> Chart to open the chart wizard. Set the Group Data by option to Columns, and ensure that both Use row 1 as labels and Use column A as labels are checked. Click save chart.



9. The chart will appear in the current sheet. Right-click the chart and select Move to own sheet.

10. Now you just need data to be processed into your beautiful chart. Click the Form option in the tool bar and choose Go to live form. This is the page that you can send to the people who you would like to fill out the form. Just copy the web address (the http://spreadsheets.google.com/... bit at the top of your web browser), and send it to your students. They do not need to log in and they do not need a Google Account to fill out the form. In fact anyone who knows the web address can fill out the form.

And that is that, you are now the proud owner of a GoogleDocs hosted spreadsheet creating form that has a nice chart to boot. I have opened the sample form I used for the screen shots, so you can access it through your Google Account. You can access the sample here.

Happy Googling!

My return

Well, that was a long month. Things have quieted down a bit so I'm hoping to resume my presence on the Internet again. Just thought I'd let people know I'm haven't forgotten about the blog.

Monday, April 5, 2010

On Jack Johnson, Trains and Curriculum ...

I was listening to Jack Johnson's excellent album In Between Dreams today when his song Breakdown came on. Here is an except of the lyrics for those who have not heard this song (which ranks as one of my favourite songs of all time):

I hope this old train breaks down
Then I could take a walk around
And, see what there is to see
And time is just a melody
All the people in the street
Walk as fast as their feet can take them
I just roll through town
And though my windows got a view
The frame I'm looking through
Seems to have no concern for now

When I first heard this album I was living in Cape Town, South Africa working as a waiter at a Mexican Restaurant (I know, it makes no sense). I listened to this song a lot as I was backpacking around Southern Africa and it resonated with my wish to get out of the bus I was in to explore everything that was rushing by me. But the bus kept going ...

Today, it hit me an entirely different way. I was thinking about all the times in school when we are exploring a curriculum mandated topic and the students and teacher would love to stop the curriculum train to explore the current topic. But the train keeps going ...

It seems to me that our current model of education views curriculum as the train; it drives education. This model may be preferred by some as it removes much of the control from the individual teachers, who may choose to teach different topics. However, what it fails to do is to allow for exploration, to permit creativity and to generate passion about the topics. We have a set time to explore a topic, and whether or not we want to move on, we must when the time is up (or we need to dredge through 3 more weeks on a topic no one cares about).

What if we instead switched our model and made the curriculum the track and allowed the teachers to control the train. We would all have a set path to follow, but we would be allowed to stop and gawk when it was appropriate. Or to speed on through when the scenery wasn't to the groups liking. We could even stop the train in the station for a day or so and go on a walkabout; exploring that stop in more detail because our students wanted to.

Imagine that, no longer needing to view the curriculum just through our window frame which, according to Jack Johnson, "seems to have no concern for now", but instead getting out of the train and seeing things unobstructed, freely, and without restraint.

Thursday, April 1, 2010

Where are the Students?

While wandering through the woods today:

I saw the deer and thought this is Biology.
I saw the different biomes and thought this is Geography.
I saw the roots of the upturned trees and thought this is History.
I saw chickadees flying through the air and thought this is Physics.
I heard the animals chattering around me and thought this is Music.
I saw the marsh grasses purifying the water and thought this is Chemistry.
I felt the perfection of nature and thought this is Math.
I saw the beauty around me and thought this is Art.
I felt connections to everything around me and thought this is Philosophy.
I felt these words flow through me and thought this is English.

Then I saw that I was alone,

And I thought, where are the students?

What did you learn in school today?

I learned that knowledge is static.
I learned that I have no hope of learning on my own, knowledge must come from my teacher.
I learned that learning is best done quietly and in rows.
I learned that fun has no place in life.
I learned that I am not smart enough to learn on my own.
I learned that conformity is valued more than creativity.
I learned that my opinion and ideas are worthless.
I learned that my greatest achievement will be a test score.

What did you teach your students today?