I think the biggest thing that I learned in CEP 812 is that web-based technologies can have very diverse applications. For example, social bookmarking is an excellent collaborative research tool. However, it can also be used as a presentation tool (Like we did for our SIG presentation). In a social studies classroom it can be used to track current events, grading students on their awareness and insights to the world around them. It’s a great structuring tool for exploratory activities.
In the past, when my technology tool set was a bit smaller, I used to fall in love with specific technologies and think that I could use it for every application. Now that I’m completing the certificate program, I think I’m getting better at identifying specific attributes of applications that will be the most effective for a given problem of practice. I initially started my TechQuest on feedback because I fell in love with Jing. While I still think that Jing is a very effective tool for providing student feedback, I’ve learned that it will most likely be more efficient to combine it with Google Docs. I guess to sum up; I’ve learned to use the tools instead of letting the tools use me.
My goal when I started this course was to learn how to better use Web 2.0 to engage students in my classes. My SIG helped me to discover how to use collaborative technologies to promote socially constructed learning. Not only that, but I myself have become a better collaborative learner in the process. I hope to stay in touch with my SIG members and continue to grow our community of Collaborators ;)
My new goal is to finally APPLY all that I have been learning. I think I’ve thought more critically about education recently than I did when I was actually in the classroom. When I finally get back into the classroom, I want to continue to evolve the strategies I’ve developed in the certificate program.
Best of luck to everyone as we go our separate ways. Hopefully we will continue to follow each other’s status, and perhaps even work together on future projects.
Showing posts with label googledocs. Show all posts
Showing posts with label googledocs. Show all posts
Tuesday, May 4, 2010
Friday, April 30, 2010
TechQuest Project Evaluation
Before I get to my evaluation, I wanted to share my first attempt at giving feedback using Jing. As part of our paper swap, Shawn and I utilized screencasting to provide each other with feedback on our TechQuests. Click the image below to view my critique of her work:
It was great to finally implement part of my TechQuest. Although it wasn’t on student work, I believe the premise is the same. I really learned a lot by receiving Shawn’s feedback in this manner as well. Namely, teachers will need to be taught how to create their screencasts.
I experienced this as well. How a teacher would normally speak to a student in a one-on-one conference will not translate well to screencasted feedback. The ‘umms’, ‘ahhs’, and pregnant pauses are no no’s. However, it would also be ineffective to script a screencast. So really, a big challenge of mine going forward will be iron out a technique that best integrates screencasting into the grading/review process. I realize that many of my issues can be better addressed once I’m able to implement it in an authentic situation but it never hurts to think ahead.
What stinks about how I created Shawn’s feedback is that she can only listen and watch me interact with her paper. Especially in a format like Google Docs or Word, it may be more effective to use the comment feature to directly tag specific areas of the document. This way, changes could be made immediately rather than watching/listening to the screencast and then making a whole batch of changes later. This would ensure that all areas of concern are addressed individually rather than being buried amongst others.
Most likely this could save time on the teacher’s end as well. Why mention grammatical mistakes in a screencast with it would be much more effective to just put in a comment tag saying “consider revising” or something more specific to the situation. When communicating a more complex idea, the teacher could create a short screencast and then link the student to it via a link in a comment tag. I believe this would better help the student because it’s directly connected to their actual document.
Establishing this process will have obvious growing pains initially because I plan to implement the feedback loops as soon as I get back to the classroom. It needs to be implemented from day one to have the most effect and this will be overwhelming. Personally, I foresee having an urge to downscale or even do away with providing feedback via screencast if I get frustrated with the amount of time I’m spending on it. For the sake of the project, it will be critical to continue to innovate rather than give in.
In the future, I think I’ll approach my TechQuest’s from the viewpoint that I will never quite finish them. Much like all things in education, my TechQuest will need to be constantly revised in order for it to continue to be advantageous to myself and my students. Therefore, when selecting a future TechQuest it will be important to pick serious on-going problems of practice.
Getting help and advice from peers/colleagues is invaluable as well. My SIG group members offered perspectives that made my project better, and hopefully more adaptable from teacher to teacher. Replication is a very important part of lesson planning to me. So in the future I will want to keep in mind that I’m not only designing strategies like this one for myself, but for my colleagues as well.
Thursday, March 11, 2010
Wrapping things up
Looking back on my experiences in CEP 811, I have a lot to be proud of. Eight weeks is such a short period of time to accomplish all I have. There are plenty of things to be proud of, but I know that my accomplishments are merely building blocks upon which even greater teaching will be built upon.
The WebQuest and StAIR projects were clearly the most labor intensive, but I learned a lot of lessons during the process. Both projects encourage student exploration which is awesome. However, engaging exploration without boundaries can render your lesson largely ineffective and in some cases even put your kids in a dangerous situation. Building the WebQuest taught me that restricting internet research to a chosen list of sites can really help to focus students. The StAIR taught me to try to predict problem areas with content and create mechanisms that will provide extra assistance to students. A teacher can never think too far ahead, especially using when using technology.
Educational application of Web 2.0 has been the biggest eye opener for me. While WebQuests and StAIR’s are very powerful tech tools, they take a very long time to create. I see Web 2.0 as a digital update to classic analog classroom activity. It takes very little effort to move student notebooks from spiral notebooks to a blog format, but there are very real benefits on top of that ease.
I will take advantage of wiki’s and Google Doc’s for collaboration. I will use jing to provide dynamic feedback to my students on projects so that I do not need to use valuable class time. I will use Web 2.0 to expand my classroom beyond the classroom walls and beyond school hours. Really, there is so much that I want to do with Web 2.0… but I need to implement these tools in a logical manner.
The philosophical difference between my tech approach now after taking CEP 811 is that I start with an educational need and then think of the tools that will help me to address it. I’ve always used technology to enhance learning, never to use technology just to use it. However, using the “problem solving” philosophy allows me to maximize my instruction.
A new goal of mine going forward is to keep building upon the work that I’ve already started. I want to make my StAIR and WebQuest better than they already are and I want to continue to make new ones. As a lifelong learner I cannot be satisfied with my teaching, I must continually improve it.
The WebQuest and StAIR projects were clearly the most labor intensive, but I learned a lot of lessons during the process. Both projects encourage student exploration which is awesome. However, engaging exploration without boundaries can render your lesson largely ineffective and in some cases even put your kids in a dangerous situation. Building the WebQuest taught me that restricting internet research to a chosen list of sites can really help to focus students. The StAIR taught me to try to predict problem areas with content and create mechanisms that will provide extra assistance to students. A teacher can never think too far ahead, especially using when using technology.
Educational application of Web 2.0 has been the biggest eye opener for me. While WebQuests and StAIR’s are very powerful tech tools, they take a very long time to create. I see Web 2.0 as a digital update to classic analog classroom activity. It takes very little effort to move student notebooks from spiral notebooks to a blog format, but there are very real benefits on top of that ease.
I will take advantage of wiki’s and Google Doc’s for collaboration. I will use jing to provide dynamic feedback to my students on projects so that I do not need to use valuable class time. I will use Web 2.0 to expand my classroom beyond the classroom walls and beyond school hours. Really, there is so much that I want to do with Web 2.0… but I need to implement these tools in a logical manner.
The philosophical difference between my tech approach now after taking CEP 811 is that I start with an educational need and then think of the tools that will help me to address it. I’ve always used technology to enhance learning, never to use technology just to use it. However, using the “problem solving” philosophy allows me to maximize my instruction.
A new goal of mine going forward is to keep building upon the work that I’ve already started. I want to make my StAIR and WebQuest better than they already are and I want to continue to make new ones. As a lifelong learner I cannot be satisfied with my teaching, I must continually improve it.
Saturday, February 20, 2010
Google Spreadsheets
As part of the Google Docs suite, Google Spreadsheets is a remotely hosted spreadsheet application intended for collaborative works. At first glance, Google Spreadsheets is like Microsoft Excel with less toolbar capabilities and to some a less friendly user interface. But to uncover its true potential it should be viewed as a live data collector rather than for static data compilation.
My Experience
I’ve used Google Docs a great deal in the past, as far back when it was still Writely. Mostly I used Documents with classmates to take notes in college classes. Google Wave has improved upon this real-time concept and I see that as the next generation of the remote based collaborative document.
Spreadsheets I have used less frequently, but lately I have become very interested in the forms element of the application. When I have a classroom again I would really like to use forms to collect contact information from parents. Sending out forms (either via email or embedded on my website), would be both paperless and better organized than the traditional contact card method.
Something to be weary of is that if most of the information is being provided by one user, the interface is not worth the frustration. I would much rather use Excel or OpenOffice Calc if I was making a spreadsheet with very little input from others. But again, if thought of as a collaborative tool only, you can minimize this frustration.
Student Knowledge
In order for students to use this software in the classroom they will need to have a basic knowledge of spreadsheet software. Students must know that a spreadsheet is a grid with vertical columns, horizontal rows, and each individual box is called a cell. Students should know that each cell can simply hold data or hold equations that reference other cells. These equations are hidden so as to show the data seamlessly.
Students need to also be taught how to create and use forms as this is perhaps the best unique feature that Google Spreadsheets offers in comparison to other spreadsheet software.
Sharing
Spreadsheets can be shared by simply clicking on the “Share” button in the upper right corner of the spreadsheet and then choosing one of the share options (Seen at right). Collaborators can be invited via email and/or the creator can choose to make the document public and establish a web link for it.
Teaching Social Studies with Google Spreadsheets
Google forms can be used quite effectively for surveys which would be good for collecting opinion data. The information can be displayed graphically to the class as a whole to illustrate the range of responses. Teachers could design forms for their students to respond to, or students could create their own surveys to collect opinion data from friends, family, and community members.
Check out this two part tutorial on how to create a self-grading quiz using Google Forms:
Part I | Part II
Helping Students Collaborate
Unlike Google Documents, the collaborating benefits of spreadsheets are not as easily apparent. It will be important to model the use of forms for students, for this might be the most foreign concept.
Organization
With remotely hosted collaborative applications it is important to establish appropriate editing etiquette. Students should use comments to indicate rationale for changes. A great environment all stems from good communication. You have to be overly detailed in your statements so that there is no misinterpretation.
My Experience
I’ve used Google Docs a great deal in the past, as far back when it was still Writely. Mostly I used Documents with classmates to take notes in college classes. Google Wave has improved upon this real-time concept and I see that as the next generation of the remote based collaborative document.
Spreadsheets I have used less frequently, but lately I have become very interested in the forms element of the application. When I have a classroom again I would really like to use forms to collect contact information from parents. Sending out forms (either via email or embedded on my website), would be both paperless and better organized than the traditional contact card method.
Something to be weary of is that if most of the information is being provided by one user, the interface is not worth the frustration. I would much rather use Excel or OpenOffice Calc if I was making a spreadsheet with very little input from others. But again, if thought of as a collaborative tool only, you can minimize this frustration.
Student Knowledge
In order for students to use this software in the classroom they will need to have a basic knowledge of spreadsheet software. Students must know that a spreadsheet is a grid with vertical columns, horizontal rows, and each individual box is called a cell. Students should know that each cell can simply hold data or hold equations that reference other cells. These equations are hidden so as to show the data seamlessly.
Students need to also be taught how to create and use forms as this is perhaps the best unique feature that Google Spreadsheets offers in comparison to other spreadsheet software.
Spreadsheets can be shared by simply clicking on the “Share” button in the upper right corner of the spreadsheet and then choosing one of the share options (Seen at right). Collaborators can be invited via email and/or the creator can choose to make the document public and establish a web link for it.
Teaching Social Studies with Google Spreadsheets
Google forms can be used quite effectively for surveys which would be good for collecting opinion data. The information can be displayed graphically to the class as a whole to illustrate the range of responses. Teachers could design forms for their students to respond to, or students could create their own surveys to collect opinion data from friends, family, and community members.
Check out this two part tutorial on how to create a self-grading quiz using Google Forms:
Part I | Part II
Helping Students Collaborate
Unlike Google Documents, the collaborating benefits of spreadsheets are not as easily apparent. It will be important to model the use of forms for students, for this might be the most foreign concept.
Organization
With remotely hosted collaborative applications it is important to establish appropriate editing etiquette. Students should use comments to indicate rationale for changes. A great environment all stems from good communication. You have to be overly detailed in your statements so that there is no misinterpretation.
Subscribe to:
Posts (Atom)