canmove, Confirmed users, Bureaucrats and Sysops emeriti
2,104
edits
Events/London Learning Jam: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(Created page with " == What == A two-day hack jam with Mozilla, Nesta, and 10+ partners in the UK to build learning projects, and then playtest the projects with youth at a nearby school. == Whe...") |
No edit summary |
||
| Line 1: | Line 1: | ||
___NTOC___ | |||
== What == | == What == | ||
| Line 7: | Line 8: | ||
Hack jam: May 24 - 25, 2012 | Ravensbourne College, London | Hack jam: May 24 - 25, 2012 | Ravensbourne College, London | ||
Playtest: May 26, 2012 | School TBD | Playtest: May 26, 2012 | local London School, TBD | ||
== Why == | == Why == | ||
=== Goals === | === Goals === | ||
* Convey Mozilla vision for Hackasaurus and web literacy and invite feedback. | * '''Convey Mozilla vision for Hackasaurus and web literacy and invite feedback.''' | ||
** Test and iterate on Hackasaurus learning mission meta-model (shared ownership). | ** 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). | ** Deepen partnerships with groups teaching code and web literacy in UK (e.g. YRS). | ||
| Line 18: | Line 19: | ||
** "Learning Mission" = well designed webpage you're encouraged to hack. Template with instructions of where to put/remix content. i.e. two-pane editor | ** "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.''' | * '''Playtest and iterate on these missions with bigger group of youth.''' | ||
* Invite youth to host kitchen table events during the Summer Code Party. | * '''Invite youth to host kitchen table events during the Summer Code Party.''' | ||
** Limit this to lead generation. Invitation to skill up after the hackfest. | ** Limit this to lead generation. Invitation to skill up after the hackfest. | ||
** Ties into this into the creation of longer term testing and evaluation. | ** Ties into this into the creation of longer term testing and evaluation. | ||
| Line 40: | Line 41: | ||
== How =- | == How =- | ||
=== Agenda Overview === | |||
* Hack jam = 2 days (30-40 participants) | |||
* Playtest = 4hr (50 youth, 20 facilitators) | |||
* Debrief = 2hr (core team) | |||
=== May 24, Day 1 === | |||
Day 1 | |||
10:00: Welcome and Intros | 10:00: Welcome and Intros | ||
* Framing Discussion | |||
* Why are we here? | |||
10:30: Hacking a game | 10:30: Hacking a game | ||
11:30: Pitch Projects | 11:30: Pitch Projects | ||
11:45: Playtest | 11:45: Playtest | ||
12:00: Debrief | 12:00: Debrief | ||
* What makes up a game? | |||
* What would you change? | |||
— 12:30: Lunch — | — 12:30: Lunch — | ||
1:30: HTML Bug Game | 1:30: HTML Bug Game | ||
| Line 92: | Line 64: | ||
4:30: Brainstorming session on making their own projects | 4:30: Brainstorming session on making their own projects | ||
5:00: Group brainstorm shareout and plan for Day 2 | 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=== | |||
Day 2 | |||
10:00: Welcome. Review of Day1 | 10:00: Welcome. Review of Day1 | ||
10:30: Teams building on learning missions | 10:30: Teams building on learning missions | ||
| Line 108: | Line 78: | ||
5:30: Closing Circle | 5:30: Closing Circle | ||
6:00: Leave venue. Optional dinner/drinks. | 6:00: Leave venue. Optional dinner/drinks. | ||
Day 3 | |||
===May 26, Day 3=== | |||
10:00: Participants arrive | 10:00: Participants arrive | ||
10:15: Opening circle | 10:15: Opening circle | ||
10:30: Pitch session | 10:30: Pitch session — Each team introduces their project. | ||
11:00: Playtesting | 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 | * 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 | ||
| Line 120: | Line 88: | ||
1:30: Lunch for team members | 1:30: Lunch for team members | ||
2:00: Debrief with the missions makers | 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? | |||