MozillaWiki

Engagement/MDN Durable Team

< Engagement
Revision as of 21:44, 23 January 2017 by Jswisher (talk | contribs) (→‎Objectives and Key Results: Added 2017 Q1)

Overview

We are the MDN (Mozilla Developer Network) durable team. See the main MDN wiki page for MDN's mission, vision, and KPI.

Team Members

Role Name Area
Product Owner Kadir Topal
Project Manager Vik Iya
Makers
Content William Bamberg Add-ons and extensions
Chris Mills Learning area
Jean-Yves Perrier Content lead (and Web)
Florian Scholz Web
Eric ("Sheppy") Shepherd Everything
Web development Stephanie Hobson
(on leave of absence) 		Front-end
Jon Petto Front-end
John Whitlock Back-end
Ryan Johnson Back-end
QA Matthew Brandt
Business Analysis Jeremie Patonnier
Community Janet Swisher

Accountability

Objectives and Key Results

What are Objectives and Key Results?

2017 Objectives

Marketing 2017 Objective Marketing 2017 Key Result / MDN 2017 Objective MDN Q1 Key Results
On a survey of developers in key markets (NoAm, India, Germany), 25% view Mozilla as highly influential, up from 18% in most recent study. MDN is rated as the second most valuable resource for developers on a survey that asks Developers to rate MDN, Stack Overflow and w3schools among others. / Increase number of successful sessions 40% year/year. a. Complete qualitative user test for action oriented developers and rewrite first selection of articles in preparation of quantitative test in Q2.

b. Complete SEO Audit and SEO/SEM rollout prioritization.
c. Document the top 30 JS errors shown to developers (to be linked to from Firefox)
d. Document Advanced HTTP topics to offer complete coverage of an important web standard on MDN (to be linked to from Firefox)
e. Document the 101 web platform changes in Firefox 52 by the release of Firefox 52 and Firefox 53 by the release of beta
f. Activate 2 new localizers in one locale, prioritized by Dev Marketing
g. (removed from plan)

80%#1 of MDN visitors understand that MDN is powered by Mozilla (baseline: 52%) h. Define 2017 brand strategy for MDN as a Mozilla property that balances core brand attributes (browser agnostic vs powered by Mozilla)
Support emerging technologies and upcoming Firefox releases i. Publish 10 reference pages and tutorials about CSS grids

j. Publish 10 reference pages and tutorials about WebAssembly
k. Document new APIs for PWA for marketing push
l. Document DevTools features of Firefox 52 and 53#2
m, n. (removed from plan)

Move MDN to a sustainable tech stack to ensure uptime doesn't go below 99.9% o. Reduce monthly hours of site downtime due to planned db maintenance to zero
The number of developers who self-report as testing and debugging for Firefox is 70%. At least 1 editor offers integrated access to MDN compat data by end of 2017 p.Validate demand for compat data plan with editor developers

q. Complete prototype for compat data as defined in budget plan

Increase the first quartile#3 of 3-week contributor retention to 3% from 1.48% (2016-H2 baseline). r. Redefine and begin re-implementing contributor pathways.

s. Run and analyze 5 contributor engagement experiments to select proven tactics for increasing retention

  1. 80% target is our understanding of what will lead to desired impact. Actual target will be decided once 2017 brand strategy (another Key Result in Q1) is defined.
  2. We aim to document DevTools features immediately after the Aurora launch.
  3. That is, 75% of cohorts have 3-week retention rates above this value. The 3-week mark was chosen to be about a month, while fitting with our sprint cadence.

    4. 2016 Q4

    Area Objective Key Result(s)
    Coordination with Developer Marketing Sign up 150,000 developers for a web-development focused email newsletter
    • 50,000 sign-ups for a web-development focused email newsletter via MDN.
    Content Increase number of successful sessions per year by xx%#1 by 2018
    • Deliver 3 reports covering a) stakeholder agreed upon strategy for MDN for 2017 and beyond, b) resource needs to execute on this strategy, and c) define and agree on 3-5 objectives for MDN in 2017
    • Deliver 20 reference pages and 5 tutorials about security-related features of HTTP. (Next step of what has been defined in Q3 research)
    • In the Learning Area, publish 12 tutorials about testing, accessibility and Web APIs
    • Publish documentation for all identified P1 topics of WebExtensions.
    • Evaluate and document the 76 new developer features of Firefox 50 by the release#2 of Firefox 50.
    • Evaluate and document the 77* new developer features of Firefox 51 by the release 50.0.1#3
    Development Move MDN to a sustainable tech stack (ensure uptime doesn't go below 99.9%)
    • Complete at least the top 5 of 8 prioritized key items listed in the MDN development plan to move MDN over to AWS
    Coordination with Brand Marketing Get xx%#1 of MDN visitors to understand that MDN is powered by Mozilla (currently 52%)
    • Achieve xx% click-through rate on MDN home page for the End of Year Donation campaign
    Community Set up community strategy
    1. Actual target will be determined once 2017 strategy is defined.
    2. The discovery phase is not terminated yet (as the Nightly cycle finished Tuesday Sept. 20th); this number will slightly go up (by experience: 5-10%)
    3. We are playing catch-up. In the future we want to be ready by the release of Beta, and we are using the longer 52 cycle to resync. Hence this unusual deadline. Firefox 50.0.1 is the current name of an intermediary release; it may be renamed by the product teams.

    Initiatives and Deliverables

    What are initiatives and deliverables?

    2016 Q3

    Area Initiative Deliverable(s)
    Meta Define a clear set of goals for MDN and a roadmap to achieve them that support our overall Developer Marketing priorities.
    • Roadmap that represents the strategic contribution of MDN to Developer Marketing objectives and KPIs;
    • establish baseline for Successful Sessions KPI
    Development Move MDN to a sustainable technology stack.
    • Transition away from Persona.
    • Establish a development environment using Docker.
    Content Complete, simplify, and extend the reach of the documentation of core web technologies for mainstream Web developers.
    • HTTP basics (To be delivered this quarter);
    • JS introduction (To be delivered this quarter);
    • page structure updated for HTML reference (To be started this quarter);
    • overview written for most-requested APIs (To be started this quarter).
    Community Taking stock

    2016 Q2

    Area Initiative Deliverable(s)
    Meta Define a clear set of goals for MDN and a roadmap to achieve them that furthers our overall Developer Marketing priorities. Goals and roadmap
    Development Mitigate our current spam problem so users continue to trust MDN. Implementation of spam mitigation solution
    Content Establish value proposition for web developers & designers to build, test and debug websites and web apps across browsers. MDN content focus on cross-browser APIs, Web Extensions, and Dev Tools

    Sprint Schedule

    Task Board Start End Demo/Outcomes
    2017 Q1
    Sprint1 TBD TBD
    Sprint 2 TBD TBD
    Sprint 3 TBD TBD
    Sprint 4 TBD TBD
    2016 Q4
    Sprint 1 10 October 25 October Demo
    Sprint 2 31 Oct 15 Nov Demo
    Sprint 3 November 21 December 2 No demo due to All-Hands
    Sprint 4 December 12 December 30 No demo, due to lots of PTO
    2016 Q3
    Sprint 1 27 June 12 July Demo
    Sprint 2 18 July 2 August
    Sprint 3 8 August 23 August Demo
    Sprint 4 29 August 13 September Demo
    Sprint 5 19 September 4 October Demo
    2016 Q2
    Sprint 1 25 April 10 May Demo
    Sprint 2 16 May 31 May Demo
    Sprint 3 Mini-sprint weeks of 6-10 and 20-24 June

    Relevant Links

Meetings

Sprint Meetings:

Meeting Time and Days Attendees Notes
Sprint Planning Meeting Every third Thursday, starting on April 21 Core Team required Stakeholders may listen in.
This meeting lasts as long as it takes.
Daily Stand-Up
(15 minutes only)		 8:30am Pacific daily
Monday-Thursday first week of Sprint, Monday-Thursday second week of Sprint, Monday-Tuesday third week of Sprint		 Core Team required Anyone is welcome to listen, but only core team members speak. All questions from non-core team members should be taken offline with Kadir or Vik.
Mid-sprint check-in every third Tuesday Core team required High-level check of how the sprint is going, adjustments that need to be made immediately, and progress toward completing the committed user stories for the sprint.
Sprint Review Meeting every third Wednesday, starting on May 11 Everyone welcome The team will show the work completed in the sprint. It's a place to ask questions and give feedback.
Sprint Retrospective Meeting every third Wednesday, starting on May 11 Core Team only No one else is invited to this meeting.
  • Unless otherwise specified, all team meetings will be in Vik's Vidyo room.


Non-Sprint MDN Meetings:

(All times Pacific)

  • MDN Weekly Dev Planning: Mondays, 10:00AM
  • MDN Content Coordination meeting: Tuesdays, 9.00AM
  • MDN Weekly Doc Request Triage: Tuesdays, 9:30AM
  • MDN Weekly Bug Swat: Fridays, 8:00AM
  • MDN Community Meeting: Bi-weekly, Wednesdays, 10:00AM

See full calendar for dates and participation info.

Communication Channels

An explanation of these channels is on the page for MDN community conversations

Retrieved from "https://wiki.allizom.org/index.php?title=Engagement/MDN_Durable_Team&oldid=1160651"