Tuesday, March 30, 2010

Critical Thinking on the Web with Alan November

As a member of a team beginning a 1-to-1 laptop program at ISBangkok, I was part of a meeting with Educational Technology consultant Alan November. I knew nothing about him other than what I just described, and I have to report a pretty fascinating meeting.

I walked in hoping to have a consultant take a unit and 1-to-1-ify it. Instead he started off saying the most important thing to teach kids about computers/internet was critical thinking on the web. He started us off with a mock unit plan for the following topic:

How did different countries respond to the crisis in Haiti?

As a Math/Science teacher, I thought first of data and statistics that could be used in a math lesson. At that point, our team sidetracked and wondered about the math curriculum our school had recently adopted, Connected Math Project 2.

Alan showed us the computational knowledge engine, Wolfram Alpha, which he said essentially takes care of the mechanics of math forever. He was able to demonstrate that it could produce steps to solve math problems, not just give final answers. When we protested that we wanted our students to understand the math, not just produce it from the internet, he showed us an interesting technology way of demonstrating understanding. Students would make a screencast of the Wolfram Alpha results of a math problem and record themselves explaining the steps to solve the problem. Alan's choice of screencasting software was Camtasia Studio.

Link to My Own Example of a Math Screencast a-la Alan November

Another point Alan November made about the use of laptops in Math was for simple homework practice. He referred to research on influences on student learning done by John Hattie which found that instant feedback was one of the most significant influences on learning. The connection was that students could do self-scoring homework online rather than correcting it in class the next day, a day after that by the teacher, or never. Thanks to our school's Moodle, we are able to concur with Alan's point, because we have started using self-scoring homework and are encouraged by the results to continue using and improving it.

Finally, we returned to the initial Haiti example. Alan shared some Google search tricks, such as "zooming in" on links from a particular country by using a country code in a search including the "site command", for example, "site: hn" for Honduras. During one of his searches, he found a relevant link at the Australian Ministry of Foreign Affairs, I believe. What he showed us was a link on the page that he said was gold. It was the "Contact Us" link. This link he said allows kids to interact with real people in the world. Via Skype they can have conversations with experts. They can record these phone conversations, edit them, and finally upload them as podcasts to iTunes to share with world. (His two technical notes were that the audio file must first be loaded to blog, and that Skype calls can be recorded with a piece of software called Audio Hijack Pro (on Macs)

He also briefly showed an example of validating a website. Honestly, it went by so quickly, I don't remember the details, but one idea was that through checking what pages link to a particular page, one can evaluate the particular page. He used Alta Vista and explained that it was better suited to this end.

While he showed these examples, he summed up the big picture by saying that one of our main goals should be teaching kids basic architecture of information, the grammar of Google. Doing this could be a learning for G6.

It was a very rich hour and a half and the list goes on. I'll summarize the last few items briefly.

He mentioned new classroom jobs of the technology age - tutorial designer, daily scribe, and he didn't get to what he said were an additional four. Each of the jobs would need to be taught, just as teachers teach anything else. He acknowledged that tutorials were work intensive and should be started using a volunteer system, which kids would sign up for once they saw how cool a tutorial was. In this context he also mentioned freeware for animation/movie making called Scratch that was created and run by MIT.

He showed an example of making a documentary using a screencast of Google Maps street view. He narrated while he panned Google's street cam along the road. It was as if he had been on the road with a hand-held video camera. This was probably the "coolest" use of technology he showcased. His example was for a Social Studies report about the Battle of Lexington (US History).

He showed an example of discussions that can go on via the web surrounding a video posted on a Ning.

He showed examples of posting pictures on Flickr and let students tag the image with overlays - This he called "no end to creativity."

When a concern arose about authentic audiences for student work, he mentioned that another way to get students connected rather than have them post on a blog and wait for the world to comment, was to got to a major website with extensive traffic and comment there, for example CNN's blog.

His ultimate message was that technology was a tool to to reach the goal of personalized education. He made a convincing case that there was ample information technology to begin moving Education in that direction.

Google Docking for Feedback, Collaboration, and Managing Assignments

I've always dreaded the paper trail of teaching.

Collecting papers. Marking on papers. Returning papers. Taking up second drafts. Rewrites. Edits. Corrections. All on paper. Lost papers. Damaged papers. Sloppy papers.

In the "dark" pre-Google-Doc ages, I started trying to circumvent that with emailed word documents. Then when our school's Moodle opened, I had students upload files to a page on the Moodle where I could open and read them. After a few edits, I could post the new file back for the student to download.

Still too many files floating around.

Now I'm experimenting with Google Docs. I distribute papers to student via Google Docs. They work on the tasks, mostly writing tasks, and I see their work while they are doing it. Best of all, I can leave feedback on the draft-in-progress. I feel like my feedback gets more attention than when I write comments/corrections on students printed drafts.

Here's an example of a student's work that I gave feedback to. Her work addresses my feedback, but the feedback has not been deleted. She changed the font color of the questions so they would stand out from her answers. I used a third and fourth color for two separate feedback sessions.



Then there's the student-student wiki function of a Google Doc that works so well. In the example below, I asked students to populate a table with presumed identities of mystery mixtures and with evidence from lab tests they used to come up with their conclusions. Students could compare conclusions and evidence from their classmates. Some identities were ambiguous. After sorting the data in the table, we were able to have a class discussion around the discrepancies. (Unfortunately the formatting of the table was lost when uploading the file to SlideShare, but you get the gist.)



I've already reduced paper usage and paper management issues by going to Google Docs for student work. Below is a screen capture of Google Docs' file management box. As easy as any Windows Explorer system.


Looking forward to next year's 1-to-1 program and using Google Docs full-time for all its advantages.


Tuesday, March 23, 2010

Trialing Science Blogging

With the ultimate goal of connecting two classrooms across the Pacific to share and discuss science experiments, my fellow teacher next door and I embarked on a trial run with our own students. Our first step was to simulate the cross-Pacific relationship by having our own classrooms blog with each other about a common science experiment to determine various snail preferences. For our purposes, we limited preference options for each of our classes so that they would not have conducted the same experiments as their classmates next door. The hope was to simulate the kind of blog conversations that they might have with students from other schools. We planned to begin working with these other schools once we felt comfortable with some basic procedures about documenting and blogging.

The most exciting aspect of the ultimate phase of our project was for students to share experiments with each other as their audience rather than with the teacher or fellow classmates who likely conducted a similar, if not the same, experiment. Their questions could be answered and discussed by fellow 6th grade scientists across the world. They could describe their procedures for students who did not know them and who might seek to reproduce them in their own schools. 6th grade science had a potential for authenticity we had rarely seen in our own teaching and classrooms.

I will let the student blogs below to give you some details about what the experiments were about. But I can report that guiding an experiment while students took and uploaded photos to their blogs was entirely overwhelming. Even with a technology piece as theoretically simple as digital photography, the management of this on top of the management of a science experiment was enough work for at least two teachers. Science experiment issues (uncooperative animal specimen) were compounded by some technology troubleshooting issues, and we just about gave up.

Unfortunately, we were only a few days away from the end of the semester, and we lost momentum in the chaotic final days before the Winter break. But below are photos posted to the blogs of the team digital documenter(s). I believe only one group out of 6 was not represented by the photos posted to the blogs linked below. Better than I expected while in the chaos of the moment. Have a look and see a first pass at sharing a science experiment via a blog post.

http://blogs.isb.ac.th/miom/science/

http://blogs.isb.ac.th/briane/category/science/

http://blogs.isb.ac.th/celinae/2009/12/14/our-snail-experiment/

http://blogs.isb.ac.th/nicoleg/page/2/

http://blogs.isb.ac.th/teganm/2009/12/14/science/

http://blogs.isb.ac.th/nicolekrause/2009/12/14/science/