Engagement/MDN Durable Team
Jump to navigation
Jump to search
Overview
Q4 Sprint 4 started on December 12!
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 | 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?
2016 Q4
| Area | Objective | Key Result(s) |
|---|---|---|
| Coordination with Developer Marketing | Sign up 150,000 developers for a web-development focused email newsletter |
|
| Content | Increase number of successful sessions per year by xx%#1 by 2018 |
|
| Development | Move MDN to a sustainable tech stack (ensure uptime doesn't go below 99.9%) |
|
| Coordination with Brand Marketing | Get xx%#1 of MDN visitors to understand that MDN is powered by Mozilla (currently 52%) |
|
| Community | Set up community strategy |
|
- Actual target will be determined once 2017 strategy is defined.
- 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%)
- 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. |
|
| Development | Move MDN to a sustainable technology stack. |
|
| Content | Complete, simplify, and extend the reach of the documentation of core web technologies for mainstream Web developers. |
|
| 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
- 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 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
- 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