Students have to decide what things that want to see with their last three days of sight. I was under the impression that students had already been told to start gathering pictures (bringing them from home) and thinking about what they wanted. The teacher was under the impression that students would start planning out their projects on the first day in class.
Basically, the first class was instructed on how to use Photo Story, and then told to start planning things out before going on a hodge podge truck through google images, searching for anything that popped into their minds. So, they rather predictably put aside paper and pencil that were meant for planning, and started going searching and saving, and importing photos. During class, I wrote an "order of operations" for the project on the board:
1. Plan
2. Find
3. Import
4. Create
I can't say that I'm 100% satisfied with that order of operations. Again, though, it comes down to not necessarily knowing the class as well as I would like. For some students, especially less organized students, this is probably great structure. For others, its going to be restrictive. I don't think kids need to find ALL pictures before importing, but it might help them stay organized. I don't think that all students need to import ALL pictures before creating--creating covering all aspects of using the program, including scripting, ordering, etc. I think for some kids, it would be good if they felt that they could do a little--write a note or a caption, befor they forget some good idea they had.
I do think, however, that some students will do things in their own order despite what was on the board. So, again, I think that the organization will help some students, and I hope that it won't hinder others. I do agree with the teacher that having kids plan out WHAT they want before beginning an image search will prevent them from being wasteful with their time. However, I hope that students who have an idea or two know that they can still go back and add it, even if the've moved on to import or create.
For the rest of the classes, I went through the "order of operations," as I for some reason insisted on calling it, before showing them how to use Photo Story.
I was rather pleased with how my intro went. I think Photo Story is very easy to use, and most students could have picked up on it without much help. However, I took the opurtunity to go over some other computer basics. I stressed the importance of checking for network drives before beginning any work. I don't know if it is a laptop issue or a wireless issue, but frequently, students cannot connect to their network drives. They work half the class, and then can't save. Sometimes they end up saving to the desktop without telling anyone, and lose their work. So I stressed that, if they do work, they deserve to have something to show for it.
Then, when going over saving photos, I went over file organization. I talked about putting things in folders, putting things where you will remember them, and naming things with some amount of logic. I'm sure a few kids already knew what I was talking about, but my experience tells me that most of them didn't. I think we live in a world where kids have always had the latest technology, and we assume they can use it. Largely that is true. But that doesn't mean that we don't have to take a minute to teach them old time skills like organization. Most teachers know student folders end up a mess, with papers sticking out, for a majority of students. I don't think its safe to assume their computer folders look any different. I probably didn't win any converts to the cause of hyper organization, but I think I opened a few eyes to the idea that they don't have to have one giant folder full of files they can't recognize.
I also focused on the idea of this being a story telling project. I talked about how, if they scripted themselves, they would sound better. I talked about giving the narration some interest. I tend to get a little sarcastic in front of classes. So to demonstrate what I wanted, I demonstrated what I didn't want. I started with "this is a...um...a picture of my friend Janet. I would want to see her...uh...be-uh-cause...she's my friend...and, uh, yeh...that would be good to see." Then, in a monotone: "This is the ocean. It's pretty. This is a flower. It's pretty. This is my mom. She's pretty." The kids laughed--which was the point--but I think they got it. Modeling is important. A lot of times things seem obvious to teachers, and we are frustrated by students who "don't have any motivation." But, I've found that modeling will improve student outcomes significantly. Just because its obvious to a teacher, doesn't mean its as obvious to a 14 year old who is going to be a bit less self aware. And, humor sticks with people better. I think just showing them a well put together example would have been good, if I'd had one (this is the first time doing this project, so I don't), but showing them what not to do--and making it funny--is also helpful in terms of modeling.
After going through the intro, I let students get started on the project. A few kids have photobucket accounts and were looking through them for photos. Others pulled out cameras. Many went straight to google images.
I did see a few lists started. The teacher instructed students to break their project into 3 days, since it is the last three days of sight. They have to specify what they will see on day one, day two, and day three. For the most part, I saw lists for day one. This is not exactly the amount of planning the teacher wanted--she wanted full lists that could be divided by days later--but at least it is something.
One thing I noticed during class was that a few students had lists that made it look like they were going to die, not go blind. I told the teacher, who laughed, and said she'd make a small announcement tomorrow.
Since the students didn't have a full day to work, most of them focused on pictures that came easily to mind--friends and family. I'm curious what they will think of after they get past the familiar.
Posts
No comments:
Post a Comment