~300 words, ~2 min reading time
- My students need deadlines throughout the semester – too many are just not very good at organizing their work on their own.
- Satisfactory/Unsatisfactory (with revision) grading is AWESOME. – Highly recommend.
- Asking students to ask “FEEDBACK PLEASE” is also a great time-saver. – Highly recommend.
- Need to clearly label all assignments as “Engagement” or “Mastery” assignments, to make clear what I’m looking for – and to make it clear in my mind, too!
- I’m not comfortable with late penalties – make a form for requesting late work being allowed, which asks them to explain why and to develop a prevention plan.
- All revisions should have a reflection attached, too. “Why didn’t I meet specs” and “What I will do to meet specs in the future.”
- All assignments should have a meta-cognitive “What I learned” component. (A “cognitive wrapper”)
- For Specs grading, I need to “adjust” the bars in certain ways. For Analytics, I set the bar too low, on the whole – except for the A level. Need to raise it for B and C levels, and reform my project to just being an “A” requirement, but make it more demanding. The bar isn’t way off for Micro, but ends up overweighting the Final in a way that is inconsistent with the Specs grading philosophy (that is, putting grades mostly in the student’s control, so that there’s little uncertainty for them). Shifting the Final to the way I’m treating the Final in Analytics would be an improvement. Need to replace with a more predictable “Mastery” component that happens throughout the semester. Need to think more about what that looks like. (Knewton is an option – but I don’t like making my face-to-face students pay to do homework…)
- LOVED the Learning Target Quizzes in Analytics – sadly, can’t do it for Micro, because of scheduling issues.