During this course, I envisioned (1) having the opportunity to create my own videos, (2) learning how to use Adobe Premier, and (3) learning how to script and set-up camera shots. The actual course outcomes, however didn't exactly align with what I had envisioned. The simple photo story project was a good ice-breaker, however I would like to have had opportunity for more exposure to video editing software and use of video equipment. I decided to volunteer to edit my group's video in lieu of shooting the video because I have access to Adobe Premier. I personally would have valued more individual movie-making assignments instead of one big group project. However in light of the fact that this is a class toward my degree in instructional technology leadership, it is important to know how to collaborate among peers to produce a product.
The outcomes, though not exactly what I envisioned, are very relevant to the work I do in my school. I did have the opportunity to explore Adobe Premier and feel that in the absence of one of our district television production members, I could shoot video, import it to Premier, and make rudimentary edits. In our small department, cross-training is essential and the more skills I have to contribute to the team, the easier it is for all of us to get our jobs done. Plus, I now see why my coworkers in the video production field watch and cite so many TV newscasts, television shows and commercials. The video production specialist I work with used to work for TV news, and said he often watches television commercials, the news, and movies to find ideas that he'd like to integrate into videos he produces for the school district. He also said he often looks at what other people produce to decide how NOT to shoot something and find ways to do it better. I also will take with me the collaboration aspect of this project. We used a wiki to archive our assignment documents, chats and files. When collaborating with teammates who are geographically separated, a tool such as a wiki is invaluable for keeping lines of communication open (Desktop-Video-Guide, n.d.).
I did not have the opportunity to thoroughly learn how to use Adobe Premier. I realize that there are professionals who can spend years with the program and never learn all of the software's features. I would have enjoyed spending all five weeks having to produce assignments using Premier. I would recommend an individual assignment each week related to using a video editing software, in addition to the group work. This would give students the opportunity to learn more about video production and editing, as well as learn the collaboration aspect of the class.
I do not like group work, however this was the most painless group project and the best group I've collaborated with in a long time. Each member was very aggressive, eager to contribute and talented in the areas for which they volunteered. We created a wiki early on in order to catalog all of our documents and maintain an ongoing discussion as to how we each would contribute. We also held a group chat early in Week 4 to get some final decisions made on the direction we would take with our project. We were very successful in completing this assignment. As a matter of fact, the PSA project was complete several days prior to the end of class. It reminds me of the quote from Week 5: "What we mean by 'plussing' is this...you take a piece of work...and when it's given to you you don't judge it...you say here's where I'm starting what can I do with this, how can I 'plus' this (Nelson, 2008)?" When I received the raw video for editing, it was already so good that I really only had to find a couple of areas that I could "plus" the product, a couple of areas where I could take what was given and try to add something to it.
I wonder how each participant in this course would compare their experience earlier in this program with the UDL lessons and websites we had to create for EDLD 5364 and this experience for 5363. In my 5364 group, I had some very talented members who did a good job, but the collaboration just didn't feel as smooth as this one. As for this course, I learned that group collaboration, even across great distances, is not only "doable" but can be done efficiently and without much stress. Though I tried to take a firm leadership role early in the process, my group members were each so aggressive and willing to do their share that firm management wasn't necessary. I learned that as easily as I can take on the role of manager, I can also take on the role of facilitator and stand aside when others are able to manage their pieces accordingly.
For future learning and experiences, I would like to help people learn more about generating their own tech support opportunities. Most folks get stuck in a program and can't figure out how to undo, or end up spending so much time trying to make a program execute a certain feature that they run out of time to actually do the project. Users need to know how easy it is to find help for just about any software program simply by searching the Internet (Siegchrist, n.d.). Users also need to know that when you call a software company's tech support, often times they will try to charge extra for tech support. A user needs to know that most software includes a "Help" menu and that it is ok to try to figure out the solution to a problem by using the tools that are most readily available. When Seigchrist says it is likely someone has asked about the problem before, it is an understatement. Tech support blogs and forums are full of solutions to the most common problems found in most software. Oftentimes, in my opinion, users are simply too stubborn to look online for help.
Guidelines for shooting quality video (n.d.). Desktop-Video-Guide. http://www.desktop-video-guide.com/shoot-video.html.
Nelson, R. (2008). Learning and working in the collaborative age: A new model for the workplace. Edutopia. http://www.edutopia.org/randy-nelson-school-to-career-video.
Siegchrist, G. (n.d.). Before you buy video editing software. About. http://desktopvideo.about.com/od/editingsoftware/bb/Buyeditsoftware.htm.
Subscribe to:
Post Comments (Atom)
Posts
No comments:
Post a Comment