I allowed two teams to swap one wheel dog after being approached by a student with the request due to a personality conflict with the musher. It was OK’d by both mushers, but objected to by the other wheel dog.
After crunching the numbers, it turned out that the deal would make the two teams more evenly matched, so by a meeting with all parties involved, I informed the reluctant fellow that he’d been traded. In the end, he was impressed that his numbers made such a big difference to the new team.
I’m finding quite a bit of instructional/management benefit to using hard copy documents to assist students in preparing for the race:
- Team Members document: Filled out by the mushers. A Google Docs file for Student Name, Position, Simulation Name (dogs, pilots, mushers) and checkoff for mask completion.
- Checkpoints document: This is used by the Musher to assign checkpoint research to all of the team members.
- Trail Log: I’m doing this hard copy to develop students’ notetaking skills and discourage copy/paste research.
If you are considering this approach to Iditarod/technology education, welcome aboardI
My students and I are super excited about this project. Some notable changes so far this year:
- Dog team members will be wearing paper-maché dog masks made in art class during each day’s running.
- Team member dogs will have dog names.
- The team musher will be named after one of this year’s real contestants.
- The Trail Log is undergoing major changes, so that team members are assigned more specific roles.
In order to get ready for the race, I will be documenting the skills and steps necessary for implementation in an orderly fashion, so that new adopters can make sense of the amazing complexities of the project.
Thanks for your interest…..Let’s go!