Google Apps

by

Achievements in the Idea Hive

It’s year two in the Idea Hive, and the learning continues for our students. The seasoned gr. 8 students (our 7’s from last year) seemed to pick right up from where we left off in June. As my teaching partner, Clarence Fisher, wrote in a previous post, these students have got “Skillz”. Similar to last year, we continued to foster the connections between our students through an Interest Survey and Flickr photo contest.

As we move towards a shared read aloud of the novel Half Brother, by Canadian author, Kenneth Oppel, our students have begun researching topics covered in the novel in order to better relate to the context: animal research, sign language, chimpanzees, and life in the 70’s, to name a few. Working in groups, two from Wingham, two from Snow Lake, they’re moving onto creating a shared Google Presentation, complete with the updated chat feature, which they’ll present to both classes via Skype.

While our students have become quite skilled at working together in a shared Google Doc, the skills required to create a shared Google Presentation needed some focus. Students struggled to agree on a number of issues including types of images, background themes, and the amount of text on a slide. New to this collaborative process, there were hick-ups and bumps, so we took some time to regroup as a class of 59. That included a shared class writing activity which we call the Knowledge Care document. Via Skype, our students shared their insight on what they need to consider and practice as they write and create together. We ended the call with guidance on how to apply these skills as they create their collaborative Google Presentation.

Clarence then spoke about the “Achievements” points that the Idea Hive students could earn through their activity in the Idea Hive site. The goal is to have our students strengthen their connections in this community. The more time our students interact with each other in this learning space, the more points they earn.  After our call, I had my kids spend the last few minutes of the day adding a comment to the Passions forum where some of Clarence’s students had previously posted on their interest: music, pets, sports, hunting, and more. And once again, I had to beg my students to log off and head out for the bus home. However, this time it wasn’t just a few – it was the entire class.

And the day ended….or so I thought.

Two hours after the school day ended, one of my students began to write about his passion – hunting. He shared the doc with me, and after dinner when I discovered it, he was still writing. While this might not be unusual to some, it was particularly moving for me. This student struggles with writing, and has never seen himself as a writer. Yet clearly, he wants to share; he has a voice.

I wondered if the “Achievements” had something to do with this. And so I asked my student, “Can I share this doc with Mr. Fisher?”. He responded with the same drive that lead me to his doc in the first place, “What’s his email? I’ll share it with him myself”.

Within minutes, both Clarence and I, the Idea Hive teachers, were in the Google doc chat room with my student, guiding him as he looked for feedback.

Teaching in a collaborative classroom helps support our students in unexpected ways and in learning spaces and lesson times driven by our students. “Achievements” came in several different forms today. Are the mindsets of educators ready to recognize and value these different forms?

It’s year two in the Idea Hive, and the learning continues for me.

Advertisement
by

Peer Editing in the Clouds with Google Docs

EduCon 2.2 is a conference where education innovators meet to discuss the use of technology as a learning aid in schools.  The tweets posted by those in attendance, and the EduCon 2.2 philosophy,  mirrored the steps I was taking my students through as they  worked  towards posting their first major piece of writing on their wiki’s.   These principles are as follows:

  • Technology must serve pedagogy, not the other way around.
  • Technology must enable students to research, create, communicate and collaborate.
  • Learning can — and must — be networked.

Writing is hard work.  For some students, that is a concept they fight tooth and nail.  Their preferred process often looks something like this:  rushed thoughts scribbled onto a template, convert to full sentences, hand it in, done.   That’s why principle #1 is important.  Technology can support the pre-writing process of brainstorming, modeling, and graphic organizers that bring out higher level thinking and student achievement in writing.

In my classroom, once students have their graphic organizer completed, the “clouds” move in.  Google Apps is an example of “cloud computing”, a techie term used to describe distant servers that store data.  It’s a free online program, similar to Microsoft Office, which students can safely access from school and home.  The apps include word processing, spreadsheet, presentations (Power Point) and form (useful to make quizzes).   At the beginning of the year, each new student is set up with their own account, supplied by DDoc from the board’s Tech Team.  Their account is designed with a username based on the school and a number instead of their real name (e.g. turnstudent01).   Students who were in my gr. 7/8 class the previous year maintained their original account.  Using the word processing app (Google Docs), students type their first draft.   They get a kick out of the fact that they are writing “online”.  I know they are safe and no one other than me and their parents, can access their work.

Principle #2 focuses on communicating and collaboration.  In this example, that means peer editing.  Once the initial draft is complete, students “share” their doc with two other students for peer editing.  Using different coloured font, the peer editors type suggestions based on the rubric, a recent grammar lesson, or basically whatever needs to be added to help the” owner” of the document.   Peer editors can write at the same time as the owner to speed up the process.  Struggling writers who are linked with a stronger writer, get the chance to read some good examples before revising and editing their own.

Effective peer editing takes time and comes with its own set of challenges.  Over the past two years, I’ve learned that peer editors using Google Docs need constant training.  We practice, practice, practice on how to constructively comment.  Surprisingly to some, inappropriate comments are not an issue, lack of constructive criticism is (perhaps not wanting to hurt someone’s feelings?).  So we practice some more, emphasizing the fact that you’re helping your peer when you give specific feedback so the owner can edit before I see it. “Great job” doesn’t cut it.  I’ve also learned this lesson needs constant reviewing.

Sometimes students don’t buy in. They couldn’t care less about another student’s writing.  They are not yet sold on the importance of developing  “communication and collaboration” skills.   As a result, I sometimes assess students on their own peer-editing skills. That usually convinces them buy in.

The peer-editing groups are changed each term. I align them based on strengths and struggles, ensuring strong and struggling students each receive some constructive peer feedback.  Sometimes students, no matter how clear you make it, will not follow a rubric. Having a peer comment on their work seems to help.  “You got to add..……to get a better mark.  You know Mrs. D will tell you the same thing”.

The beauty of networking with other students using Google Docs supports principle #3. After the owner has had two other students read and evaluate their work, they have time to make improvements before being graded.  Google Apps is accessible anywhere there’s internet, so students can, and do, work on their assignments from home.   Since I can view each student’s history, I see they are excited and engaged based on the times of day (and night!) they are working.

We are a small school in a rural area.  Not all students in my class have access to technology at home.  It’s important they are given numerous opportunities to become digitally literate.  Recently, when I ran into several of my grade 8 grads at their high school, they told me they continue to value and use Google Apps on their own.

Peer editing with Google Apps helps support my students with the writing process by creating a community where students support each other.   “Computing in the clouds” supports the writing process outside of school, since it’s accessible anywhere there’s an internet link.

When I first started using Google Apps with last year’s class, I wasn’t sure how things would go.  But we all learned together, modeling the three principles supported by Educon.  Students love the process and the benefits are clear.  After all, who wouldn’t want to spend their days writing in the clouds?