Webmaker/2015

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

Top-Level

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

Sub-Level

• Webmaker https://wiki.mozilla.org/Webmaker/2015/Product
  • MakerFox / FF experiments https://wiki.mozilla.org/Webmaker/2015/MakerFox
• Mozilla Mentors https://wiki.mozilla.org/Webmaker/2015/Mentors
• Mozilla Fellows+++ https://wiki.mozilla.org/Webmaker/2015/Leaders

Context

• 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

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)
  • Comments needed now if big read flags
• Finalize planning teams (TPS and Ops)
• Move most of key initiative text into sub plans (Matt)
• Identify any major MoCo needs not in dependencies (TPS and Ops)

Week 1: Key initiative subplans

• Initial key initiative plans done (above)
• TPS and OPS meet to discuss mid-week
• Identify top level goals plus tensions for each initiative (all)
• Identify priority geographies (Mark to propose)
• Drafts out for comment (to who until x)

Week 2: Key initiative details

• 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