This is the P2PU Archive. If you want the current site, go to www.p2pu.org!
Course Design Orientation
My recent threads
You haven't posted any discussions yet.
Recently updated threads
- The End of Courses: Capturing Meaningful Reflections Sat, 2011-05-14 18:03
- Welcome new organizers - please introduce yourself! (April 2011) Thu, 2011-04-28 19:10
- How is your course going? Let us know! Wed, 2011-04-27 05:31
- Become a tester on new.p2pu.org! Mon, 2011-04-25 22:03
- when not to run a course? Mon, 2011-04-25 22:00
Have you planned for the end of your course?
We've had a lot of conversations about how to start a course - make introductions, discuss personal learning goals and expectations for the course - but we have yet to talk about the end of courses.
In general, when courses end the P2PU research group sends surveys out to organizers and participants. We also encourage organizers to experiment with the idea of certificates to signify participation/completion. The School of Webcraft is also beginning to experiment with a handful of badges to measure competencies.
Have any of you thought of other ways to formalize the end of your course? Do you have ideas, recommendations or questions?
Read more in the handbook: http://wiki.p2pu.org/finishing-a-course
FWIW, I am currently running this pre-course survey to help identify the experience level of each member in various technical areas as well as identify members willing to facilitate a smaller peer group:
jQuery Pre-Course Survey
https://www.quickbase.com/db/bfykhnu7n?a=dbpage&pagename=survey.html&key...
The results are coming in fast and look extremely promising.
I would like to do a closing survey as well and would appreciate not having to construct the survey apparatus myself.
I like that idea, Dan, especially that it will help make groups. I wonder if a pre-course survey can even get something to measure at the end. For example: I hope to learn X, Y, and Z. And at the end, How well do you feel you know X? 0-4
Things I'd like Webcraft organisers to incorporate into their end of course processes:
* course-organisers to write a reflective report of the course back to the Webcraft list / blog
* participants invited to write a reflective blog post about their experience and to provide constructive criticism.
* any reusable code / outputs that can be used learning resources to be openly licensed on GitHub / shared in the P2PU Wiki
* reviewing, updating and reflecting on the course materials and design and identifying modifications and improvements that can be made.
* identifying participants in the course who'd be willing to 'adopt' the course and lead it in the following round
* querying participants about new courses they'd be interested in leading as a follow on.
* all participants to identify the next step on their learning journey.
* invite participants to provide each other with feedback about their participation and team-working skills
* invited to write references for the course-organiser to include in their work-portfolio / CV / for inclusion with a certificate
* provide participants with a guide to all the ways they can become more involved with both P2PU and School of Webcraft
Besides sharing code most of these tasks are probably consistent for courses in general (not just Webcraft). I'd love feedback on these ideas and will write them up with sample questions in the handbook.
P*