Next time I approach a project such as this I will make it much shorter. I feel that the assignment was too lengthy so instead of putting the lessons together over a rushed 3 day period I would actually make the assignment cover the entire semester so this project is more like a journey as opposed to a quick sprint. Throughout the lesson I learned that grouping students in pairs is the best way to tackle an assignment such as this. When students are learning a software for the first time pairs give them an opportunity to work together on a solution to a problem. The collaborating solutions allow students to work on their team work skills and the knowledge of how to do something stays with the student longer.
If I were to do this project again I would not spend so much time searching for a large number of links. When I put together tech lessons my search is a little more focused and streamlined. I felt that I was looking for links just for the goal of meeting a quota instead of an actual useful purpose. However I do intend to do more projects similar to this in the future because I believe it brings ideas to life more than what a textbook can do. I really want to get more interactive pieces similar to this. I don't think I will change how I structure the over all assignment in terms of individual responsibility or the technical steps that are needed to master the software.
Subscribe to:
Post Comments (Atom)
"I feel that the assignment was too lengthy so instead of putting the lessons together over a rushed 3 day period I would actually make the assignment cover the entire semester so this project is more like a journey as opposed to a quick sprint."
ReplyDelete- I felt the same way with my TechQuest... I have a habit of allocating too short of a time period for projects like these. In the end it's crucial to provide enough time or the students don't really get what they could out of it if they were able to take their time. Good insight.