Mick - I've archived the older chapter outline
http://pad.p2pu.org/p/outline_old_open_workshop_spaces
--//
TO DO
- Mick circle back with invites for guest speakers -done
- Mick create a space to collaborative edit course for Week 4 - working on it
- Jane draft intro email
- Welcome!
- Communication tools
- RSVP for hangouts (max 10, first come first serve, explain it will be broadcast, etc.)
- what they can expect in facilitation: responses by us to their comments on disqus, any shared blog posts (links)
- what we expect from participants - a guideline for constructive contribution to the course
- introductions
- Comments on each others responses in Disqus, at each others blog posts, google group
- optional small grouping - if interested email google group with workshop topic of interest
- Feedback on coruse throughout through Disqus and google group
- Week 4 - we expect collaborative editing for improvement
Week 3 email (no Google hangut this week, but solicit RSVPs for next week)
Subject: You made it to Week 3 of the course!
Hi all!
We had a great hangout last week with Allen Gunn, the Godfather of collaborative workshops (he runs them for living through his org Aspiration Tech). Check out the recording here: https://www.youtube.com/watch?v=sOYiMo64bwo
This week is the second to last week of the course! Here's what's in store:
1. No Google hangout this week, but put next week's on your calendar and RSVP at http://pad.p2pu.org/p/Designing_Collaborative_Workshops. Our last Google hangout will take place on Thursday, 29 August at 17:00 BST, 18:00 CEST, 9:00am PDT and feature guest speaker Helen Varley Jamieson -- a writer, theatre practitioner and digital artist from New Zealand, based in Germany. You can read more about her and the hangout here: https://p2pu.org/en/courses/77/content/1448/.
2. Now is a great time to catch up on reviewing last week's sections, and go through this week's -- Sections 4.5, 4.6, 4.7. (insert links).
3. If you haven't engaged with the course on previous weeks - Dont' Panic! - it's easy to catch us up. Have a read through the following chapters which focus on some of the key techniques of participatory workshops and how to prepare to use them.
https://p2pu.org/en/courses/77/content/831/
https://p2pu.org/en/courses/77/content/838/
4. If you're ahead of the game, go ahead and get started on designing your agenda (Section 5). https://p2pu.org/en/courses/77/content/833/
As always, feel free to ping the google group list with questions and suggested additions to the course. We look forward to giving feedback via the Disqus comments forum on the foot of each page via email.
For a reminder of how to keep in contact with this course have a look at this page - https://p2pu.org/en/courses/77/content/1451/
Cheers,
Jane
Week 1 intro email
Hi everyone!
Welcome to the Designing Collaborative Workshops course! You are free to take this course at your own pace, but for those who would like to participate with others and meet new people to explore these ideas with, join us for the next 4 weeks!
The facilitators for this course are Mick Fuzz and Jane Park (that's me). You can reach us directly at any time at the following emails:
Mick Fuzz: mickfuzz@clearerchannel.org
Jane Park: janepark@creativecommons.org
For this first week, here's what we'd like you to do:
1. Review About, Communicating in this course, and Badges.
2. Join the Google Group and introduce yourself and your workshop interest: https://groups.google.com/forum/#!forum/designing-collaborative-workshops
3. Complete sections 1 and 2 of the course.
4. RSVP for the first synchronous Google hangout that is tomorrow at http://pad.p2pu.org/p/Designing_Collaborative_Workshops. First come, first serve! We will be broadcasting and recording the hangouts, which means that we can accommodate 10 at a time, including ourselves. Don't worry; you can follow along on the pad which will contain the livestream link. We will record for those who can't make it.
What we expect from you:
- Participation via Google Group, Disqus, sharing of blog post links, comments/feedback on each others posts
- Optional small grouping -- some of the tasks, esp the larger course project of designing your own workshop and running it -- may be done in collaboration with others. It is much more fun that way! Once you have introduced yourselves, pair or group off with others that you see have similar interests. If you would us to arrange you into a small group for your, let us know.
how should they do this? I'm not sure how this will work, is there anyway of automating it?
- Help improving this course via comments on each section and suggestions for additional resources. In Week 4 you will be invited to edit and add to the course directly to create an on-going openly licenced guide to delivering workshops.
- A collaborative spirit!
What you can expect from us:
- Responses to questions/comments via Disqus, email, the Google Group.
- Hosting of 3 Google hangout sessions (see etherpad http://pad.p2pu.org/p/Designing_Collaborative_Workshops.
- Feedback on your final workshop design and reflection (if you run it). Awarding badges to you for completion of those projects.
- A collaborative spirit!
Looking forward to meeting you all!
Best,
Mick Fuzz and Jane Park
Schedule 3 synchronous sessions according to Mick's and Jane's schedule - For me the following dates are good - OK, i created dates, invited you on gcalendar,a nd also added the meeting links to the course
- a) 5th August after 20:00 BST or 6th August after 17:00 BST (not too late please)
- b) 13th August after 17:00 BST 15th August after 19:00
- c) 27th August after 17:00 or 29th August after 19:00
- guest speakers for which ones? mick will circle back with invites
- 22 July - Two week sign-up period begins
- 5 August - Course starts. Review and complete sections 1 to 4 (not 4.1). 1st synchronous discussion session via Google hangout
- 12 August - Review sections 4.1 to 4.4. 2nd synchronous discussion session via Google hangout
- 19 August - Review sections 4.5 to 4.7
- 26 August - Review and complete sections 5 to 6. 3rd synchronous discussion session via Google hangout
- Mick and Jane should subscribe to all Disqus comments for each page of the course + general Discussion tab (jane - done; mick - ok if i must ;p)
- should we add link to How to use Disqus for participants? https://docs.google.com/a/creativecommons.org/document/d/1YaVZl3T2cY-a3Ni5Xwochq1WsgF61dbV97Gc1m1UXVo/edit?usp=sharing - yes why not -
ok i'll add it - Should we use announcements feature or export emails? (if we are doing small groups, thens we should use export i think) - I'm not sure what the announcement features is but I don't have a stong opinion on it.
- Draft first email/announcement to course participants to go out first week and inviting them to RSVP for hangout (max 10, first come first serve, explain it will be broadcast, etc.)
- what they can expect in facilitation: responses by us to their comments on disqus, any shared blog posts - I think it would be good to say what we expect from participants as well - a guideline for constructive contribution to the course, especially re-ordering the course, what to add to it, extra resources, feedback on the course / facilitation etc. - this is for Week 4 Mick will create on wiki or google docs
- 3 sync sessions with guest speakers? let's set the dates and i'll re-invite, is there anyone you can invite? I set the dates and invited you - are those times good?
- recordings of sessions posted after
- 2 badges: feedback on projects submitted (agenda design + blog post reflection on actually running workshop) -
- communication avenues: 1) disqus, 2) our emails? google group could be good I think for a catch all -
- Other Q's
- do we want to split people up into small groups? then we'd need to do initial course survey? what info do we want to solicit in survey? profession and timezone -can we let them self select if they want to go into smaller study groups? if so I wouldn't be against random groups of 4-5 people. I think this is what happened to me in mechanical mooc for python
- ok - how can they self select? i think people won't split into groups unless we assign them to one randomly or by method
- should we have a google group? I think we should.
ok -- I'll set one up as a optional forum for folks https://groups.google.com/forum/#!forum/designing-collaborative-workshops Add page for Communication tools https://p2pu.org/en/courses/77/content/1451/
To discuss - changes
- Changed Key Elements to Key Facilitation techniques: https://p2pu.org/en/courses/77/content/831/.
- Numbering and headings
- Revised language to be more action-oriented
- tCollapsing schedule to be 4 weeks (versus 8)
- 22 July - Two week sign-up period begins
- 5 August - Course starts. Review sections 1 & 2: Background + Propose your topic. Why are you here?
- + 1st synchronous discussion session via Google hangout. What makes a successful workshop? + Key elements of collaborative and open workshops.
- 12 August - Pre-workshop prep + Warm-up exercises
- + 2nd synchronous discussion session via Google hangout. Ground rules, roles, and resources + Flexibility and rough consensus
- 26 August - Working with large groups + Documentation
- + Feedback and Evaluation + Following Up & Reflection
- 9 September - 3rd synchronous discussion session via Google hangout. Design your own workshop
- Badges?
Action items by 26 June
- do comprehensive review
- preplan for 3 synchronous sessions
- middle session - feature guest speakers from seeds of change, libregraphics
- mick send note to SOO list, other lists, individuals for feedback
- badge - for running a workshop (jane find icon, summary, mick tweak)
Suggestion for badges
http://clearerchannel.org/wordpress/wp-content/uploads/2013/07/WORKSHOPDESIGNER_GS2.png
http://clearerchannel.org/wordpress/wp-content/uploads/2013/07/WORKSHOPDELIVERY2_GS.png
http://clearerchannel.org/wordpress/wp-content/uploads/2013/07/WORKSHOPDESIGNER_GS2_300.png
http://clearerchannel.org/wordpress/wp-content/uploads/2013/07/WORKSHOPDELIVERY2_GS2_300.png
Workshop Designer
Describe your Badge:*:
A badge to reward the creation of a workshop plan as part of the School of Open course on collaboartive workshops.
Because Folks With This Badge Can:*
plan a collaborative workshop in an informal learning space, showing awareness of techniques and activities to encourage interactive and peer learning.
Workshop Delivery
Describe your Badge:*:
A badge to reward the delivery of a workshop planned as part of the School of Open course on collaboartive workshops.
Because Folks With This Badge Can:*
deliver a collaborative workshop in an informal learning space, collect feedback from participants and reflect on how they delivered the workshops to keep learning by teaching.
Outreach list for participants
- libregraphics -done
- Floss Manuals & Net Time - done
- Seeds for Change // Hacktionlab - done
- Rhizome / London Roots Collective
Action items by June 5
- Add to course: https://p2pu.org/en/courses/77/collaborative-workshops-in-informal-learning-spaces/
Billy: Add examples of Scrum, logistics/administration/messaging (resources, time, people)- Jess: Add examples of successful CC events/tactics to appropriate key elements (brainstorming at CC global summit)
- Mick: Review Jane's additions (once added by May 22) and continue to iterate examples and intros and outros to situate more in world of free culture
- Jane: Add examples of Aspiration Tech, review and iterate on Mick's examples, add intros and outros, link 2 and 6 - reference 6, this is the beginning - final project due X date, start fleshing out "follow-up" section
- Change "Analysis" section to "additional resources, tips and tricks" or something similar
- Everyone: After June 5, review the course in its entirety for discussion during meeting June 12
- Will open for sign-ups mid-July, to run in late July or August
Ideas/Notes
- guest speakers - seeds for change
- ask course participants to add their own examples during course for each element
- what makes a successful workshop is more of an open question before preconceived notions
Action items by May 16
Jane add to course ux and make everyone organizers; Jane assign feedback- Mick's case study - open video course sprint
- Billy's case study - find examples of Scrum, logistics/administration/messaging (resources, time, people)
- Jess's case study - key elements of successful CC events (brainstorming at CC global summit)
SOO guidelines - How to run a collaborative workshop
- how open processes contribute to collaboration
- open resources and tools you can use to run the workshop
Rough outline
- Background to subject - define terms give short outline
- History of participatory / open workshops (a wide range of backgroups from activist, Free Culture, software professionals (Scrum / Agile) approach)
- Propose your topic. Why are you here/etc.
- Discuss what you think makes a successful workshop
- have some questions
- our impression of key elements of workshops: different roles, activities, resources/tools
- attribution of resources we are drawing on
- Our philosophy as related to SOO (drawn from several)
- Outline of Collaborative / Open workshops - List of key elements - how long should this be? 100-250 words per area?
- Break out each week by key element - each element week has tips and tricks
- Run through severa (3-6) examples of successful and not successful (openly/collaboratively run) workshops
- each has some of (blog post, agenda, any howtoguides, any media)
- after each case study, discuss what made it good, what made it bad. here's what we think made it successful, is there something missing?
- Jane - Aspiration Tech / Internet taskforce http://www.ietf.org/tao.html
- Mick - Introductions and getting on the same page - Case Study - open video course sprint -http://archive.org/details/FacilitationExampleOvlondonStubnitz
- Jessica - Large workshop facilitation
- Billy - Roles and Resources, Planning
- Mick - Overcoming problems - Case Study - Basement social centre - Looking at three issues - overcoming going in circles, unequal participation, lack of energy
- Wikimedia workshop http://blog.wikimedia.org/2013/02/14/wikipedia-education-program-sweden/
- Case study of a workshop that went really well (P2PU)
- Analyze, discuss etc. + Overall tips and tricks
- Design your own workshop
- Create an agenda
- Run it
- Report back - reflect (link to your blog post in disqus)
- How would you improve this course? How would you expand what you learned here into a larger workshop/unconference?
- Workshops ideas that would lend itself to courses - next steps? case study: Open Science Data sprint! - Billy: http://creativecommons.org/weblog/entry/37060
- Get a badge for 6, 8 and 9 (we need to design badges)
Virtual sessions
- Have office hour like synchronous session on air - record and post
- July/August 2013
CASE STUDIES & ROUGH SUBJECTS
Should we give ourselves a deadline? We want to have this ready for second cycle (June/July) so April 25
Mick - Introductions / Using movement, spaces, games
Jane - Internet - Rough Consensus model of make decisions by groups in offline setting http://www.ietf.org/tao.html
Vanessa - User generated content for courses - maybe map on to workshops
Jessica - common denominators - workshops ideas that would extend to planning courses or other learning experiences
Billy - Borrowing from code analogies - SCRUM - for workshops - iterative approaches, brainstorming, proof of concepts, rapid processes http://en.wikipedia.org/wiki/Scrum_(development)
===Chapter 1
What does "open" mean in the context of workshops?
Focusing specifically on "open" style workshops... eg. rough consensus, Internet Engineering Taskforce - http://www.ietf.org/tao.html
- Guest speaker relating their own experience?
The move away from formal learning environments to peer-led, often temporary learning spaces at conferences, gatherings or street occupations creates a new set of challenges for workshop leaders. This course is a peer-learning space to explore these issues.
some good resources on 'open spaces'
http://rhizomenetwork.wordpress.com/resources/
Assessment?
There is no assessment tasks for this course but "You have to be in it to win it!" - We encourage you to share your experiences on delivering collaborative workhops.
If there are no assessment tasks for this course, then how will participants know when they have completed it? If participation is the only metric, then do we bother with badges?
=== Case study: Rough Consensus Workshop Model (Jane) =
Brief summary:
Key elements of the workshop
Other elements of workshop
Example of event that took place
Resources for further reading
Other resources
===Chapter x - Introductions Case Study
Tools for Change Workshop http://www.seedsforchange.org.uk/tools
http://rhizomenetwork.wordpress.com/resources/
===Chapter x - Jump around
Over view of some fun, interactive techniques that can be used
http://www.seedsforchange.org.uk/tools#warmups
Some different techniques and where to find more.
===Chapter x - Borrowing from code analogies
Billy - Borrowing from code analogies - SCRUM - for workshops - iterative approaches, brainstorming, proof of concepts, rapid processes
===Chapter x - User Generated Workshops & Content
[Jessica + Vanessa] - common denominators - workshops ideas that would extend to planning courses or other learning experiences
Draw on the interest of the people in the workshop to help them collaboratively create content
Challenges of bringing together these ideas when working remotely
Some tips for making sure the converstation doesn't end at the end of the workhops
Have a possible forum for further conversation idenfied but be flexible if the group wants to lead in another direction
===Chapter x - Adding Badges in to the mix
Chapter specifically about workshops to do with badges?
High-level explanation of badges as representatons of achievement or experiences, not as an assessment tool (common misconception)
Aligning a badge or set of badges to challenges/tasks in a course - what "take away" skills will learners/participants want to share with others?
- Visual Design
- Issuing Platform (P2PU, OpenBadger, or by hand)
- Link back to criteria (evidence of task completion or participation)
Important note: leave badges alone until the course/end-product has been developed 80%+