Webmaker/2015: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 7: Line 7:


=Sub-Level=
=Sub-Level=
* '''Webmaker''' https://wiki.mozilla.org/Webmaker/2015/Product
* '''Webmaker.org / Webmaker app''' https://wiki.mozilla.org/Webmaker/2015/Product
** '''MakerFox''' / FFx experiments https://wiki.mozilla.org/Webmaker/2015/MakerFox
** '''MakerFox''' / FFx experiments https://wiki.mozilla.org/Webmaker/2015/MakerFox
* '''Mozilla Mentors''' https://wiki.mozilla.org/Webmaker/2015/Mentors
* '''Mozilla Mentors''' https://wiki.mozilla.org/Webmaker/2015/Mentors

Revision as of 22:43, 20 November 2014

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

Top-Level

Sub-Level

8uzpe_e6.png

Context & Links

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