Engagement/MDN Durable Team
Jump to navigation
Jump to search
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 |
|---|---|---|
| Team Lead | Kadir Topal | |
| Program 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 | Front-end |
| Jon Petto | Front-end | |
| John Whitlock | Back-end | |
| Ryan Johnson | Back-end | |
| QA | Matthew Brandt | |
| Community | Janet Swisher | |
Accountability
Objectives and Key Results
What are Objectives and Key Results?
2017 Objectives and Q2 Key Results
| 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. | * Serve 38 million sessions on MDN (an increase of 10,8m sessions y/y)
|
| 80%#1 of MDN visitors understand that MDN is powered by Mozilla (baseline: 52%) | * Initiate the separation between open web and Mozilla-specific documentation by moving at least one out of 24 product-specific projects out of MDN
| |
| 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 | * Sign up one editor vendor for inclusion of compat data by end of 2017 |
| Increase the first quartile#2 of 3-week contributor retention to 3% from 1.48% (2016-H2 baseline). | * Migrate all 3 public MDN-related mailing lists to a single Discourse forum to lower the barrier for entry |
- 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.
- 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 | demo summary |
| Sprint 2 | February 13 | February 28 | demo slides; demo summary |
| Sprint 3 | March 6 | March 21 | |
| 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, Full Team Review | Every third Thursday, 8:30am PT Planning meetings with sub-teams take place earlier in the same week. |
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, 8:30 PT | 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 Demo Meeting | every third Monday, 9:00am PT | 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: Discussions about MDN content
- dev-mdn a.k.a. mozilla.dev.mdn: Discussions about MDN platform development
- mdn a.k.a. mozilla.mdn: Discussions for all stakeholders about planning and high-level issues
An more detailed explanation of these channels is on the page for MDN community conversations.