Events/London Learning Jam
What
A two-day hack jam with Mozilla, Nesta, and 10+ partners in the UK to build learning projects, and then a playtesting event with youth at a nearby school.
Design Brief
Preparation for all hack jam participants: Design Brief
Where
- Hack jam: May 24 - 25, 2012 | Ravensbourne College, London
- Youth Playtest: May 26, 2012 | local London School, TBD
Why
Goals
- Convey Mozilla vision for Hackasaurus and web literacy and invite feedback.
- Test and iterate on Hackasaurus learning mission meta-model (shared ownership).
- Deepen partnerships with groups teaching code and web literacy in UK (e.g. YRS).
- Develop 5 new Hackasaurus learning missions with UK youth and partners.
- "Learning Mission" = well designed webpage you're encouraged to hack. Template with instructions of where to put/remix content. i.e. two-pane editor
- Playtest and iterate on these missions with bigger group of youth.
- Get real feedback that we can build into the missions for the Summer Campaign.
- Explore models for longer term testing and evaluation.
- Invite youth to host kitchen table events during the Summer Code Party.
- Invitation to skill up after the playtest.
- Strengthen relationships among aligned communities of practices.
- Bring organizations together under shared goals and continued collaboration.
What does success look like?
- 5 missions reflecting key interest areas of youth in the UK (and reflecting missions of key partnerships we want to have)
- 50+ youth involved in an engaged/enthusiastic day of learning
Example Projects
Who
Hack Jam
30-40 participants representing 10+ organisations. Mixture of instructors, developers, and designers.
- Mozilla
- Nesta
- ZFL
- Young Rewired State
- ReMo
- Goldsmiths
- Digital Me (x)
- Ravensbourne (x)
- Whole Education (x)
- Nominet Trust (x)
- British Telecom (x)
- Double Negative (x)
- JISC (x)
- Drexel University (x)
- Ministry of Stories (x)
- Raspberry Pi (x)
- Good for Nothing (x)
Playtest
- 50 youth, aged 13+ yrs and up. Range of web skills.
- 20+ facilitators from participating organisations
How
Agenda Overview
- Hack jam = 2 days (30-40 participants)
- Playtest = 4hr (50 youth, 20 facilitators)
- Debrief = 2hr (core team)
The agenda below is a draft. Sessions and times subject to change!
May 24, Day 1
10:00: Welcome and Intros
- Framing Discussion
- Why are we here?
10:30: Hacking a game
11:30: Pitch Projects
11:45: Playtest
12:00: Debrief
- What makes up a game?
- What would you change?
12:30: Lunch
1:30: HTML Bug Game
2:15: Hacking with the X-Ray Goggles
3:00: Break
3:15: Intro to Webmaker Tool/Lovebomb
4:00: Share hacks
4:30: Brainstorming session on making their own projects
5:00: Group brainstorm shareout and plan for Day 2
- What are strengthens of these approaches?
- What are weaknesses of these approaches?
6:00: Leave venue. Optional dinner/drinks.
May 25, Day 2
10:00: Welcome. Review of Day 1
10:30: Teams building on learning missions
12:00: Group check-in
12:30: Lunch
1:30: Team mission building continued
3:00: Playtest missions among groups
4:30: Evaluation. Playtesting preparation
5:30: Closing Circle
6:00: Leave venue. Optional dinner/drinks.
May 26, Day 3
10:00: Participants arrive
10:15: Opening circle
10:30: Pitch session — Each team introduces their project.
11:00: Playtesting
- Depending on how many missions are made either we can allocate time slots for people to go to sessions at each table, or we can have youth roam freely
1:00: Closing
1:30: Lunch for team members
2:00: Debrief with the missions makers
- How did playtest go?
- What would you do differently?
- How did you structure your playtest?
- How would you iterate on your project?