Webmaker/2015

Draft-only, internal planning wiki. Not ready for public sharing.

Top-Level

• Mozilla-wide plan (draft) http://mzl.la/mozilla_2015_draft
• Mozilla Learning plan (draft) http://mzl.la/webmaker_2015_draft

Sub-Level

• Webmaker.org / Webmaker app https://wiki.mozilla.org/Webmaker/2015/Product
  • Develop a fun and useful software product and attract a significant user base.

• MakerFox https://wiki.mozilla.org/Webmaker/2015/MakerFox
  • Run experiments that inform cross-product integration with Firefox and Firefox OS

• Mozilla Mentors https://wiki.mozilla.org/Webmaker/2015/Mentors
  • Empower significant number of people to teach digital skills & competencies.

• Web Literacy curriculum https://wiki.mozilla.org/Webmaker/2015/Clubs
  • Provide mentors with framework to develop learners' digital skills & competencies.

• Mozilla Leaders https://wiki.mozilla.org/Webmaker/2015/Leaders
  • Invest in the next generation of digital leaders.

Context & Links

• Meeting agenda + notes: https://etherpad.mozilla.org/2015planning
• 2015 Pipeline Analysis: https://foundation.etherpad.mozilla.org/2015-pipeline-analysis
• Opportunities, Risks, Tensions, Questions: https://etherpad.mozilla.org/learning2015
• Mentor Networks online & CRM requirements: https://teach.etherpad.mozilla.org/requirements
• Badges plan: https://etherpad.mozilla.org/badges2015plan
• Mozilla Mentor Network notes: https://hive.etherpad.mozilla.org/pink3
• Marketing Planning: https://foundation.etherpad.mozilla.org/webmakermarketing2015
• Webmaker Clubs: https://wiki.mozilla.org/Webmaker/2015/Mentors/Clubs

Roles

• Overall coordination (Matt, with support from Ben and Ops)
• Webmaker Product + App (Lead: Andrew. With: Cassie, Simon, Paul, Ben, David)
• Mozilla Mentor Program (and Webmaker Mentors) (Lead: Claw With: Michelle, Amira, Paul, Anme, Mark)
• Maker Fox Lab (Lead: David) (With: Andrew, Matthew W., Paul, Humph, Wex)
• Mozilla Fellows and Leaders (Lead: Mark) (With: Michelle, Dan, Kaitlin, Dave, Ben)

Roadmap

Week 0: High Level

• Agree on name / scope (TPS and Ops)
• Clean up top level plan (Mark)
• Finalize planning teams (TPS and Ops)
• Set up sub-plan template on wiki (Matt)
• Identify any major MoCo needs not in dependencies (TPS and Ops)

Week 1: Key initiative subplans

• Initial key initiative plans done (above)
• Identify priority geographies (Mark to propose)
• TPS and OPS meet to discuss mid-week
• Identify key tensions and questions for each initiative (all)
• Form working groups to address each of those key tensions and questions.
  • Clearly document that list and communicate about it. (Matt)
  • Be clear about the deliverable and tracking / structure / deadline for each.
• Ensure Ben's geography doc is well-reflected / merged into overall plan.
• Schedule meeting for Week 2 (Tuesday: tensions / questions deadline. Thursday: wiki sub-plan deadline)

Week 2: Key initiative details

• Debrief on key questions / tensions. Add more as needed. (Tues) (all)
• Build out more detailed milestones and KPIs for each sub-plan (all)
• Start to discuss resource gaps (plus existing roles we no longer need) (all)
• Drafts out for comment (to who until x)
• Finalize 'draft' plans for Portland discussions

Week 3: Budgets and resources (including operational/administrative needs/infrastructure/systems)

• Leads work w/ Angela on resource needs (all)
• We have a list of 'what we have' and 'what we don't'
  • We won't know what we can and can't do fully at this stage
  • But we will see where need to make some initial trade offs / where to move fast on critical gaps

Week 4: Portland

• Engage whole team in this process
• Revise based on discussion and input

December 19: Board meeting