Engagement/MDN Durable Team
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 (temporarily unavailable) |
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. |
| 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 | |
| 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 |
- 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.
- We aim to document DevTools features immediately after the Aurora launch.
- 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.
Sprint Schedule
| Task Board | Start | End | Demo/Outcomes |
|---|---|---|---|
| 2017 Q1 | |||
| Sprint 0 | January 9 | January 24 | No demo; the MDN team started early, so work before Sprint 1's official start is "Sprint 0". |
| Sprint 1 | January 25 | February 7 | |
| Sprint 2 | February 13 | February 28 | |
| Sprint 3 | March 6 | March 21 | |
| Sprint 4 | March 27 | April 11 | |
| 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
- MDN Durable team processes
- Agile glossary
- MDN Roadmap: Epics by theme and timeframe
- MDN backlog in Taiga
- Initial product backlog
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
|
Relevant 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 Opportunity Review: Wednesdays, 9:00AM
- MDN Weekly Bug Swat: Fridays, 8:00AM
See full calendar for dates and participation info.
Communication Channels
- Email: mdn-team@mozilla.com
- IRC: #mdn and #mdndev are our main channels (public conversations) / #team-awesome for private conversations.
- Mailing lists:
- dev-mdc a.k.a. mozilla.dev.mdc
- dev-mdn a.k.a. mozilla.dev.mdn
- mdn a.k.a. mozilla.mdn
An explanation of these channels is on the page for MDN community conversations