always learning

One of the things I love about being a technology facilitator is that I get to see all sorts of fantastic management strategies in the many classrooms I visit. Every teacher seems to have a unique way of handling the variety of tools we have at our disposal here at ISB. Thankfully, as part of our CoETaIL course, Jeff and Dennis asked all of the participating teachers to add to a shared VoiceThread about technology management strategies in the classroom.

Check out all of the great tips they shared here:

Do you have any special tips to share about managing tech in the classroom? Please feel free to add them to our VoiceThread!

One of the issues that comes up again and again in our CoETaIL program is the “essential technology skills” that all of our students (and teachers) need to know. Now, I have to admit, I usually have a hard time with this idea, because it often comes with a list of skills like: bullets in Word, formulas in Excel or animations in PowerPoint. Basically all the things I’ve been trying to de-emphasize in favor of bigger, more wider-reaching concepts like collaboration across distances, communicating ideas to multiple audiences, or creating something new using technology tools.

Sure, you need to know how to add bullets – but you should learn how when you’re writing a list (“just in time“), not for the sake of knowing “just in case” you might need it. So, it was very interesting to me when our conversation in our last course took a turn to something I can really relate to – rather than the list of standard MS Office “skills” that were all the rage in the 1990s (with the previous edition of the NET*S), but those almost unidentifiable skills that frequent computer users just seem to take for granted. Things like:

• knowing to hold your mouse over an icon or a link to see what it does.
• understanding that the menus for any program are at the top of the screen, that they are usually very similar, and generally what you find within them (for example: “view” usually means how you see things on the screen and that menu is found in almost every program).
• recognizing when something is lit up (or underlined) on a website, you can click on it.
• knowing that the cursor changes when held over different parts of the screen and what that means (the little arrow turning into a hand over a weblink for example, or being able to stretch out a picture when it turns into the double-sided arrow).
• using tab to move from cell to cell or box to box on forms or websites.
• being able to recognize drop-down menus – and that they hold additional features.
• understanding that right clicking on things brings up more options.

These are things that are common from program to program as well as on multiple operating systems. They’re not specific tasks that you only use once in a while, they’re things we do every day, and those that are comfortable with these skills often find learning new technology tools a lot easier than those that are not. It’s like these skills are part of a special language that we can speak in order to understand how to interact in any given technology-based environment.

What’s especially interesting about these little, seemingly meaningless, skills is that they truly are transferrable and haven’t changed much over time – they’re certainly not dependent on a specific version of software. Unfortunately, despite their consistency, they often cause a lot of confusion for people who aren’t really comfortable with technology.

But here’s the thing: how many of these kinds of skills are there? Is there some kind of list? Because it’s almost impossible to think of all of them once they become second nature. Yet it’s easy to see how much people struggle when they haven’t learned them or don’t “see” them when they’re using technology. Even when we support people who are new to technology, we almost expect that they can see these small clues the computer gives us, in fact, they become implicit in our understanding of how to use a computer.

We simply expect people to know why the mouse and cursor change shape and what the shapes mean, or that you can figure out how to do pretty much anything by checking the help menu in any program, or that you need to highlight something before being able to change that item because that’s how you “tell” the computer what you want to change. These have become intuitive skills for those of us that use technology regularly, but unfortunately not knowing them has become an obstacle for others to overcome.

How can we make these simple and far reaching technology skills explicit?

A few weeks ago, I was in a grade 2 classroom demonstrating VoiceThread for a quick and easy science project. Based on our conversation in CoETaIL from the day before, I wanted to see what the second graders knew about these basic skills, so I spent a few minutes of my lesson specifically highlighting the many ways which the computer gives us “clues” about what to do.

First, when we logged into VoiceThread, we looked all around the screen to see if we could figure out how to make our own VoiceThread based on the options. It took them a few tries to understand that the “Create” button was telling us that this is the place where we can create our own Thread.

Once we got to the create screen, I asked them if they could tell me where to start. Again, it took a few tries, but once they realized the Upload button was the only one they could press, I asked them how they could know that in the future. They figured out that it was the only button in color, and it was the only button that, when you moused over it, turned the mouse into the shape of a hand.

We basically went on like this throughout the process of creating a VoiceThread. To be honest, I thought all of those “signs” would be blatantly obvious to these 7-year old students, who have grown up with computer games, but they weren’t. As soon as we pointed them out, it was clear to see that they made sense and that with continued discussion, they would become second-nature. But again, who’s going to be having this discussion with them if their teachers aren’t comfortable with these implicit skills either?

Not that I’m looking to make another old-school list of standards, but what else would you put on the list of implicit tech skills like these? Do you teach them in your school?

Sunflowers by marcomagrini
Key Blanks by Ben Oh
Steps by two more days

It’s hard to believe, but it’s been two full years since I taught my own technology classes. Of course I’ve done all sorts of co-planning and co-teaching in the last couple of years at ISB, but it’s certainly not the same as having your own group of students to work with. So, this year, in my new role of Middle School Technology and Learning Coordinator, I am thrilled to be back in the classroom, teaching our one middle school IT class – a sixth grade quarter-long exploratory course – for just one quarter this year. With the end of the semester quickly approaching, we’re almost finished with our ‘big project’, so I thought I’d share it here.

Given that I’m only teaching one section of this class (and my colleagues Ross, Matt and Jean are teaching the others), I felt it was important to keep the content as consistent as possible, but of course, I couldn’t resist transforming the process of how we would learn that content, along with the finished product that we would use to demonstrate our learning. As can be expected, since this is the first time I’ve taught this particular class in this particular way, there are a few things I would change for next time around, but overall, I think it turned out pretty well.

Basically the course is intended to teach the “basics” of Microsoft Office (you know the course, you probably taught it back in the 1990′s like I did when I was first teaching). So, considering the content, I tried to develop a project-based unit that would emphasize independent learning (since so many of the students would probably already know the basics), as well as allow them to share what they’ve learned in an authentic environment, and utilize some new technology tools in a creative way.

As usual, I followed the Understanding by Design model to plan the unit and the MYP Technology Design Cycle to break down the stages of the project into manageable chunks. Basically, what we’re working towards is a shared wiki with student-created tutorials on all of the MS Office basics (inspired by Chad Bates, our fantastic tech director who taught the class last year and experimented with the tutorial idea with his class) and an overview of digital citizenship, which we will share with the entire middle school as a resource for their potential technology needs.

Here’s what it looks like:

Established Goals (ISTE NETS Standards)

2. Communication and Collaboration: Students use digital media and environments to communicate and work collaboratively, including at a distance, to support individual learning and contribute to the learning of others. Students:

a. interact, collaborate, and publish with peers, experts or others employing a variety of digital environments and media.
b. communicate information and ideas effectively to multiple audiences using a variety of media and formats.

4. Critical Thinking, Problem-Solving & Decision-Making: Students use critical thinking skills to plan and conduct research, manage projects, solve problems and make informed decisions using appropriate digital tools and resources. Students:

b. plan and manage activities to develop a solution or complete a project.

5. Digital Citizenship: Students understand human, cultural, and societal issues related to technology and practice legal and ethical behavior. Students:

d. exhibit leadership for digital citizenship.

6. Technology Operations and Concepts: Students demonstrate a sound understanding of technology concepts, systems and operations. Students:

b. select and use applications effectively and productively.
d. transfer current knowledge to learning of new technologies.

Enduring Understandings:
Students will understand that:

• Responsible digital citizens demonstrated shared characteristics, habits and attitudes.
• We can work together to teach others what we have learned.
• We can use web 2.0 tools to collaborate and communicate with a global audience.

Essential Questions:

• What are the characteristics, habits and attitudes of a responsible digital citizen?
• How can we work together to teach others about responsible digital citizenship?
• How can we collaborate and communicate with others online?

Assessment Evidence

GRASPS Task

• Goal: Your goal is to produce a multimedia handbook about basic technology tools and digital citizenship for ISB elementary students.
• Role: You are a team of student leaders at ISB.
• Audience: Elementary students at ISB, and around the world.
• Situation: You will need to collaborate together to produce a thorough, easy to understand, multimedia tutorial wiki about basic technology tools and digital citizenship for a school and worldwide audience.
• Product/Performance: Your wiki must demonstrate everything that you have learned about digital citizenship and basic technology tools this quarter.

Six Facets of Understanding:

• Explain: Produce a screencast tutorial about how to use a specific technology feature in MS Office.
• Apply: As a team, create a multimedia handbook about digital citizenship for ISB elementary students.
• Interpret: As part of your presentation to ISB elementary students, write a skit to demonstrate your understanding of digital citizenship.
• Perspective: Develop and deliver a lesson to ISB elementary students presenting all facets of responsible digital citizenship.
• Self-Knowledge: On your blog, describe what you know about digital citizenship. At the end of the course, go back to your first post and reflect on what you’ve learned. What more do you need to learn?
• Empathize: On your blog, write a post in the perspective of one of the characters in the public service announcements. Reflect on the events of that day and how they made you feel.

And here’s how I broke it down into the stages of the MYP Technology Design Cycle:

Investigate

During the first part of the project, we spent most of our class time exploring different types tutorials and determining what the criteria are for a quality tutorial. To get the discussion started, we watched and critiqued the first one (on adding a survey in Moodle) as a class. Then, they had class (and homework) time to watch at least 2 other tutorials from the list below (or a different tutorial that they found and shared with the class):

• Adding a chart in Google Docs
• How to draw realistic eyes
• Student Sample from last year
• Discussion Settings in WP
• RSS in Plain English
• VoiceThread tutorial
• Switch to Mac

For each tutorial they watched, they added a response to the Moodle discussion forum answering the following questions:

• What did the creator of this tutorial do well?
• What would you change about this tutorial?
• What aspects of this tutorial would you like to include in your own tutorial?

In the end, we came up with a list (as a class) of criteria for a good tutorial that all students will be assessed with at the end of the project. Then, because we had so many different skills to create tutorials on, I asked students to form groups based on the tutorials we needed (this list was based on the course curriculum I was given). Finally, each student wrote a blog post reflecting on what they learned in that section of the project , which tutorial they had chosen to create and why, and what they need to learn to complete their tutorial.

The next time I teach this course, I would also add some exploration time with ScreenRecorder and MovieMaker (and maybe even GarageBand) since we ended up doing quite a lot more editing than I thought we would. I would also add in brainstorming time for students to create a mini-storyline for their tutorial to help give them focus and to make the tutorials a little more interesting.

Plan

During the planning, students created a storyboard and script of their tutorial, keeping in mind all of the criteria we developed during the investigate stage. We focused on: making the tutorial understandable by anyone (even people who are not in our class), using simple and clear directions, including a basic introduction and credits, and changing the view and “zoom” on the screen to keep the tutorial interesting. Once the students completed their storyboard and script, they posted it on their individual blog along with a reflection on this part of the project.

Create

At this point, students have a good idea of what their tutorial will look like and exactly what steps they need to take to complete their tutorial. They spent a little bit of time exploring with the SmartNotebook SmartRecorder (which happens to be our only screencasting software available to students), after watching this tutorial created by Matt, and then got right down to the recording.

Aside from some serious Windows-related drama about recording volume (oh how I miss working in a Mac lab), it really only took one lesson for the students to record their complete screencast. Of course, they all wanted to add the extra features, so we brought their screencasts into MovieMaker and started adding the finishing touches. Once they had their introductions and credits, it was time to add background music. Since we have access to a smaller Mac lab, we spent one lesson exploring with GarageBand to create simple (and original) background tracks.

As each student finished their tutorial, they did a peer assessment based on the class criteria. Once they had feedback from their peers, they had time to edit and fix any issues with their completed tutorial. After they were satisfied, they uploaded their finished tutorial to YouTube, embedded it in a blog post and reflected on their finished product.

Evaluate

For the last few days of the project, we spent some time determining which aspects of the ISB Definition of Learning we achieved throughout the process of completing our tutorials:

I used a simple checklist to get students thinking about which aspect of learning they met during each stage, then they shared their results with a peer knowing that they would be asked to share 1 or 2 ideas with the whole class, and then we had a whole class reflection. Finally, they wrote a personal reflection as a blog post.

Here are a few highlights from what they shared with me during the whole class-reflection:

• We learned a lot having to do our tutorials independently instead of being directly taught each skill. This way we learned it when we needed it and as we were doing our project, which helps us remember how to do it.
• We learned more by being able to test out the tools by ourselves and helping each other than by having the teacher teach us everything together.
• We would have preferred to do one single blog post at the end of the project reflecting on everything, instead of one for each stage.
• By writing a blog post at the end of each stage, we really reinforced everything we learned during that stage.
• We learned a lot about what makes a good blog post from having to write so many.
• We learned about ISB’s Blogging Guidelines and how to write a blog post with just the right kind of information.
• We learned how to be independent in our projects, but we liked having the checklists and all the steps broken down for us.
• We would have liked the steps to be broken down into even smaller chunks so we could meet our deadlines better.
• We learned that we can use websites and YouTube to learn new things and to teach other people things that we know.

Putting it all together

I waited until the last three weeks of class to have the students start compiling the wiki because I really didn’t know how long it would take to complete the tutorials. So now we’ll spend the next few days putting the finishing touches on the wiki and publicizing it around the middle school so that other students can learn from our work.

We also have a collaborating class in the US who are doing something very similar, except using the Mac version of all of these applications. We’re hoping that they will finish their tutorials before the end of our semester so we can also include them on our wiki and have a brief discussion about the transferability of skills from one platform to another.

We’ll also use this time to discuss digital citizenship and online safety and responsibility to be able to add those sections to the wiki. If we have time, I would love to do something in one or two elementary classrooms to share what we’ve learned  with an authentic audience (that can always use some reinforcement about appropriate online behavior).

Final Thoughts

Considering that I really didn’t have a good idea of how long it would take students to complete this type of tutorial – especially in a PC lab working with MovieMaker (my old enemy), I’m quite impressed with how things turned out. I was so happy to see how much the students learned in this very project-based course. I did very little direct instruction, even though some of the screencasting and editing tools were completely new to most students. It was a pleasure to see how much they appreciated being able to learn independently and to create something new with their knowledge.

Next time I would really like to add a more in-depth collaborative element – having our global partners do the peer assessment instead of simply within our class, potentially sharing more directly via our blog posts, and maybe coming up with some kind of collaborative lesson for our elementary classrooms that could involve multimedia elements (or a Skype connection) from our partner class. Of course, this is all dependent on timing, commitment and logistics. Hopefully, I’ll have a chance to teach this course again to make it even better!

Musical Composition and Podcasting in the Elementary Classroom

Back in November, our absolutely amazing Elementary music teacher, Vince Bullen, and I led an EARCOS Weekend Workshop on GarageBand. Our goal was to spend two full days exploring GarageBand in a hands-on, project-based environment, tailored to the needs of both music and elementary classroom teachers. Even with this very specific focus, we had 10 international school teachers from around Asia join us in Bangkok for the weekend.

Thankfully, Vince is a complete expert in all things musical, so he started the workshop off with a thorough overview of pretty much everything GarageBand has to offer: from creating your own music, to editing pre-created tracks, to making “magic GarageBand” songs. Within about 1 minute of his introduction I had learned a number of useful tricks:

• How to raise and lower the volume of a specific track (use the little “down arrow” on any track to get the volume for that specific track)
• How to block out background noise and get rid of the “echo” and “reverb” on self-recorded tracks
• How to edit individual notes in any track (including pre-created tracks)

After getting the musical basics, the workshop switched gears to learn about easy ways to integrate music, video, photos and voice recordings to make enhanced podcasts.  I started off this session by sharing the absolutely fantastic podcasts our fifth graders here at ISB made at the end of last school year as part of the Reader’s and Writer’s Workshop book club unit (here’s our unit planner), and then went over the basics of recording your voice and adding jingles, images or movies to a podcast. It always amazes me just how easy it is to create a podcast with GarageBand!

Once our participants had the basics, we split into two groups to delve deeper into the ways that teachers can use GarageBand in the classroom. Under Vince’s extremely capable guidance, the music teachers worked together to create their own songs using MIDI instruments and all of the pre-created tracks in Garage Band.

Separately, the classroom teachers worked with me to collaborate on their very first podcast – a multimedia book recommendation they can share with their students in class, which can also be used as a model for student-created podcasts:

One of the things the classroom teachers were most interested in was the process that I use to guide students through a technology-rich project like a podcast, specifically using the MYP Technology Design Cycle. Although it was created for middle years students, I find the design cycle to be an authentic, practical, useful way to tackle technology projects. It’s actually the process you naturally go through when working with technology, but if you don’t break down the steps, you can tend to skip through and end up at the computer before you’re ready.

So we ended up spending quite a bit of time working through the stages of the design cycle, as I would with a class of students. Here’s how I would break down a podcasting project according to the design cycle:

Investigate:

• Explore with the software – some time to play with Garage Band to get to know the basics – what are the strengths and weaknesses of this tool, what can it do, with the goal to generally feel comfortable with the tool towards the beginning of the project.
• Brainstorm a topic for your podcast (even if there is a specific topic, each group/individual will most likely have some individual choice involved. At this stage, it’s important for them to come up with a number of ideas (thought through to a basic level) so they can choose the best one. Have students justify their choice to you.
• Organize resources: take the time to figure out what is needed to complete the project (pictures, books, cameras, special clothing, etc). Make sure they have a list and it’s clear who is going to bring in each item.
• If any research needs to be done, this would be the best time. Begin with a focused research question and organize all relevant information in one central place.

Plan:

• Write your script (you might want to use a checklist like this with your students)
• Use a storyboard to organize your pictures and audio. (this one is more for digital video, so you may want to change the directions on the boxes).

Create:

• This stage should be no longer than the Investigate stage (as long as they have done a good job with the Investigate and the Plan). This should be simply transferring all of the work they’ve already done on paper to their finished podcast.
• Export the finished product into AAC format if you have pictures (without pictures, you can choose .mp3)
• Publish the podcast on iTunes or a podcasting service like Gcast, PodBean, or Podomatic. (Usually the teacher will compile all student podcasts into one account so that the RSS feed includes all student work. As a teacher, you can also embed a widget on your class blog or website so parents and students can listen anytime).
• Create an iTunes channel for your podcast following these steps.

Evaluate:

• Listen to their podcast, looking for strengths and weaknesses – what did we do well? what do we need to improve?
• Listen to other group podcasts, looking for similarities and differences, what did we do well? what do we need to improve?

Finally, on the second workshop day, participants had a chance to develop their own GarageBand projects for use in the classroom. Teachers worked on everything from designing a podcasting project from scratch, following the technology design cycle and Understanding by Design curriculum planning process, to creating their own musical compositions, to exploring new ways to integrate technology into classroom practice.

In my opinion, podcasts are a fantastic way to share student learning, allow time for reflection and metacognition and to connect your classroom to other learners around the world. This quick, but engaging, weekend workshop was a great way to get participants excited about this new mode of learning and to put the process of implementing authentic technology projects into practice in a safe environment.

How do you use podcasting in your classroom?

One of the challenges of an integrated technology program is the fact that some responsibility for teaching essential technology concepts is placed on the shoulders of teachers who are not specialists in that field. Although adopting (or creating your own) technology standards is a step in the right direction, those statements are often general enough to leave room for uncertainty, especially for those teachers that don’t have a special interest in technology. This can lead to situations where classroom teachers feel that they lack guidance or concrete expectations about how to authentically and appropriately embed technology into their curriculum in a way that’s relevant to students and deepens their learning, which in turn leads to frustration and confusion.

In schools that are fortunate to have technology facilitators, often this kind of confusion is resolved through conversation and collaboration. However, even in those schools, usually there’s not enough time in the day for the facilitator to be able to support every single teacher. And even if there were enough facilitators to work closely with every single teacher, it’s simply not sustainable or advisable to place all of the essential knowledge about such a critical subject in the hands of one or two specialists. Although many teachers appreciate the personal support of a technology facilitator, it should be possible for individual teachers to get a sense of what they could or should be doing without having to go through a “gatekeeper.”

Having been a technology facilitator for 10 years now, I had always thought that individualized, personal conversations were the best way to help teachers embed technology into their classroom practice. While I still believe that collaborative planning and teaching is by far the most effective approach, I’m also realizing that having a clearly defined and readily accessible set of examples of classroom experiences, alongside a set of standards, would not only help teachers understand what’s expected of them, but would also provide an approachable starting point for conversations with teachers who may be unsure where to start.

So, here at ISB, we’ve decided to adapt and revise the ISTE Learner Profiles so that they reflect specific examples of units being done here at school. Currently, the general profiles provided by ISTE, which are broken down by division, provide basic examples of age-appropriate learning experiences (which meet the NET*S standards) that teachers can use to develop projects at their grade level. Of course, these examples are quite broad and don’t include samples of student work. So, we’re hoping that by documenting, on the ISB21 wiki, these types of experiences that are happening at our school, with links to completed student work, unit planners, and feedback from teachers, our faculty will feel they have a strong starting point for planning new projects (and implementing those that are currently part of our curriculum).

We’re just in the begining stages, but the ISB21 team will start this documentation process by linking and describing the projects we have collaborated on here at ISB, on the ISB21 wiki:

• PK-2
• 3-5
• 6-8
• 9-12

Next, we will ask the CoETaIL cohort teachers to share other projects that they may be working on independently. Finally, we will bring the profiles to the rest of the school community and ask them to contribute as well. In the end we hope to have an easily accessible, frequently updated, relevant and specific list of projects that meet our Technology and Information Literacy standards (TaILs) that all teachers can use to guide their planning, spark their interest, and start conversations.

Do you have these kinds of Learner Profiles at your school? Are they helpful? How do you build or clarify shared expectations for authentic, technology-rich student experiences with the faculty at your school?

signpost mage by will_hybrid
scaffolding image by kevindooley