Group Leadership Project: Wordle Tutorial

Below is our Wordle Tutorial video. Educators can learn the basics of Wordle.net as well as view an assortment of examples and ideas from various content areas to help get them "Wordling" in their classrooms.  Enjoy!

My Quick Overview of  Project Development:

As a group, we used a variety of tools to create and deliver our tutorial.  First of all, we began brainstorming using Google Docs since it allowed for sharing ideas without having to find a common time to "meet".  From there, Abbie created the basic PowerPoint of our tutorial and also shared it via Google Docs.  We were all able to easily edit and contribute to the PowerPoint this way.  We continued utilizing Google Docs as we created our Storyboard & Script for narration. 

As the volunteer final editor,  I first recorded Abbie using Jing, then (since Jing only allows a 5-minute movie in the free version--eek!) I had to record that version to my computer using GarageBand.  This program is also where I recorded my audio on the 2nd part.  Since I had to make a "copy of a copy" for Abbie's portion, the audio isn't as clear as mine, but it works!  I didn't want to lose her voice on the project since she had done such a great job with her narration. 

Lastly, I edited everything together using iMovie, but the project was 13 minutes long which meant the file size was HUGE and YouTube wouldn't accept it, nor could it be easily attached to an email.  In order to make our video more succinct and publishable, I spent extra time editing out any unneeded pauses or commentary to cut the time down to just under 10 minutes.  Once that was complete, I was able to FINALLY publish the project to "YouTube" from the iMovie Share options.  Phew!

If I had to create a similar product again, I would be sure to note any time limitations that might affect publishing from the beginning.  Since I'm new to Jing, I didn't think about the 5 minute limit until it was too late and the same applies to YouTube's 10 minute video restriction.  Those were the key factors that resulted in TONS of additional editing time and modifications.  Other than that, I really enjoyed the tools we chose--from Google Docs to iMovie--and I'm glad that we had a great group of motivated contributors.  :)

If the video isn't loading correctly, try this link:  http://www.youtube.com/watch?v=Y9uFo_TlteU

PART B - Storyboard and Script

For our Group Leadership Project (a Wordle Tutorial for Educators), Team4Tech created a storyboard and script using a shared PowerPoint presentation on Google Docs. Click the following link to view our work: Team4TechWordleScriptandStoryboard

Thus far, Abbie kicked us off by creating a shared PowerPoint to start our project.  She gave an example and listed the step-by-step instructions required to create a Wordle.  I added to the presentation by creating an Introduction/Attention-getter slide and a few slides titled "Why Wordle?" to explain the logic behind using Wordle in the classroom.  I also did some minor editing of the wording on a few of Abbie's slides.  

Therefore, as a group, we started the Storyboard and Script AFTER the PowerPoint itself.  Because of this, we had to "work backwards" a little bit--describing and scripting the slides that Abbie and I had already created, but then mapping out the other slides that had not yet been generated in the presentation.  

The Final Work distribution is as follows:

• Everyone:  Add any additional examples and details by Monday night, Feb. 21st.
  
• Abbie:  Incorporate various examples gathered during Computers class from students and record full voice-over of script
  
• Wheatley:  Generate FINAL product (recording, final editing of all slides, etc.) in conjunction with Abbie

I am looking forward to creating our final product.  Wordle is a tool that many teachers don't know about yet, and it is simple to use plus a GREAT way to get students to engage with reading and writing in any content area! :)   

PART A - Brainstorm Session

For the kick-off to our Group Leadership Project, we (Team4Tech) chose to meet using Adobe Connect.  We chose this tool because:

• We were all familiar with it already.
• It was free to us (since MSU has an account).
• We were able to have our professor set up our meeting, as well as help us get started, making a successful session more likely.
• It offered an easy way to record our conversation both via microphone and via chat.  

During the development process, I was able to note some additional features of Adobe Connect that I hadn't before.  This was in response to difficulties I had at first.  I was struggling with a slower Internet connection as well as choppy audio and was limited to TYPING rather than speaking like everyone else.  These glitches resulted in feelings of frustration and disappointment.  I can honestly say that, for the first portion of our session, it was the WORST Adobe Connect experience I've ever had.  One feature that came in handy, though, was the "raise your hand" feature. When my group was busy talking and I wanted to call their attention to a comment I had typed, I was able to "raise my hand".  I also noted the "agree/disagree" options, as well as other generic responses, which I hadn't seen before.  

My experience helped me realize how frustrating it can be to feel "silenced" when trying to contribute to a group.  While I wasn't being marginalized by anyone intentionally, the lack of a fully functioning program made me feel like I was on the "outside looking in", which is a miserable place to be when you long to be involved.  This reminds me of when students don't have technology available (or have sub-par tools) at home and are left feeling further disconnected, rather than connected, by technology.  

While we were brainstorming, our group also used Google Docs to document our "plan of attack."  Thank goodness for Google Docs!  This tool was easy for me to access and the chat feature there worked much more efficiently, too.  Our plan came together nicely and it was really helpful to have a common, editable-by-all document to log our progress.

If I had to develop a similar product again, I might choose a different forum.  While this was our best option with our current circumstances, I found that being limited to a chat feature while everyone else had audio/microphone access left me feeling isolated more often than not.  I also found that I prefer having a typed chat so that you can actually READ what someone wrote if you missed what was said.  Plus, people can't speak over one another.  When I logged on the main decisions had already been made, but by reviewing the chat log all I could see was a few quick "hellos".  The full "meat" of the decision-making process had been verbal, so by not being present at that point (or able to hear), I had missed out and would have to wait to watch the replay to feel fully caught-up. 


I would prefer using a typing-based tool (perhaps even a group chat on Skype) so that everyone could quickly read key points & re-visit them as the discussion progressed.  A typed chat also means an instant "hard-copy" of what was said and eliminates the need to watch a recording to seek out verbal comments.

Thankfully, I have a great group that was able to pull things together effectively, but in terms of tools--while I still love Google Docs, Adobe Connect was less than impressive this time around.  

If you'd like to view our recorded Brainstorm session, click below:
http://breeze.msu.edu/p91777893/