MozillaWiki

Engagement/MDN Durable Team: Difference between revisions

< Engagement
(→‎Team Members: protect Stephanie's privacy)
(Updated team members)
 
(39 intermediate revisions by 5 users not shown)
Line 2: Line 2:
== Overview ==
== Overview ==
{{admon/note|[https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q1-sprint-1-1?kanban-status=649183 Q1 Sprint 1] starts on January 25!}}
{{admon/note|[https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q1-sprint-1-1?kanban-status=649183 Q1 Sprint 1] starts on January 25!}}
We are the [https://developer.mozilla.org/en-US/'''MDN'''] (Mozilla Developer Network) durable team.  See the main [[MDN]] wiki page for MDN's mission, vision, and KPI.
We are the [https://developer.mozilla.org/en-US/'''MDN'''] (Mozilla Developer Network) durable team.  See the main '''[[MDN]]''' wiki page for MDN's mission, vision, and KPI.
 
The MDN Durable Team is now part of the Developer Outreach group in Emerging Technologies (ET), and is no longer part of Marketing/Engagement. The content team moved to ET in July 2017, and the dev team moved in March 2018.


==Team Members==
==Team Members==
Line 8: Line 10:
! Role !! Name !! Area
! Role !! Name !! Area
|-
|-
| [[Engagement/MDN_Durable_Team/Agile_glossary#Product Owner|Product Owner]] || Kadir Topal ||
|colspan="3"| '''Managers and planners'''
|-
|-
| [[Engagement/MDN_Durable_Team/Agile_glossary#Scrum Master|Project Manager]] || Vik Iya ||
| [[Engagement/MDN_Durable_Team/Agile_glossary#Product Owner|Product manager]] || Kadir Topal ||
|-
|-
|colspan="3"| [[Engagement/MDN_Durable_Team/Agile_glossary#Maker|Makers]]
| Writers' Team Manager, Content Lead || Chris Mills ||
|-
|-
|rowspan="5" style="vertical-align:top;"| Content
| Agile coach
| William Bamberg
| Peter Chinaka
| Add-ons and extensions
|
|-
|-
| Chris Mills
|colspan="3"| '''[[Engagement/MDN_Durable_Team/Agile_glossary#Maker|Makers]]'''
| Learning area
|-
|-
| Jean-Yves Perrier
|rowspan="3" style="vertical-align:top;"| Content  
| Content lead (and Web)
|-
|-
| Florian Scholz
| Rachel Andrew
| Web
| CSS
|-
|-
| Eric ("Sheppy") Shepherd
| Daniel Beck
| Everything
| Browser compatibility
|-
|-
|rowspan="4" style="vertical-align:top;"| Web development
|rowspan="5" style="vertical-align:top;"| Web development
| Stephanie Hobson <br/>(temporarily unavailable)
| Peter Bengtsson
| Front-end
|-
| Jon Petto
| Front-end
|-
| John Whitlock
| Back-end
| Back-end
|-
|-
Line 43: Line 37:
| Back-end
| Back-end
|-
|-
| QA ||Matthew Brandt ||
| Schalk Neethling
|-
| Front-end
| Business  Analysis || Jeremie Patonnier ||
|-
|-
| Community || Janet Swisher ||
| Mustafa Al-Qinneh
| UX design
|}
|}


Line 53: Line 47:
===Objectives and Key Results===
===Objectives and Key Results===
What are [https://en.wikipedia.org/wiki/OKR Objectives and Key Results]?
What are [https://en.wikipedia.org/wiki/OKR Objectives and Key Results]?
====2017 Objectives====
====2017 Objectives and Q3 Key Results====
[https://docs.google.com/a/mozilla.com/spreadsheets/d/1tPEf3VVkLtaQK_3sXx_Sb3nK7ep4ZVlaXIL9v1gM4ZM/edit?usp=sharing|Complete Developer Outreach Q3 OKRs] (mozilla.com logins only)
{| class="wikitable"
{| class="wikitable"
! Marketing 2017 Objective
! Developer Outreach 2017 Objective
! Marketing 2017 Key Result / MDN 2017 Objective
! MDN Q3 Key Results  
! MDN Q1 Key Results
|-  
|-  
|rowspan="4" style="vertical-align:top;" | On a survey of developers in key markets (NoAm, India, Germany), 25% view Mozilla as highly influential, up from 18% in most recent study.
| style="vertical-align:top;" rowspan=6|Increase number of MDN sessions 40% y/y
| style="vertical-align:top;" | 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.
| style="vertical-align:top;" |Serve 39 million sessions on MDN (an increase of 11.2m sessions y/y)
| a. Complete qualitative user test for action oriented developers and rewrite first selection of articles in preparation of quantitative test in Q2.<br/>
b. Complete SEO Audit and SEO/SEM rollout prioritization. <br/>
c. Document the top 30 JS errors shown to developers (to be linked to from Firefox) <br/>
d. Document Advanced HTTP topics to offer complete coverage of an important web standard on MDN (to be linked to from Firefox)<br/>
e. Document the 101 web platform changes in Firefox 52 by the release of Firefox 52 and Firefox 53 by the release of beta <br/>
f. Activate 2 new localizers in one locale, prioritized by Dev Marketing<br/>
g. (removed from plan)
|-
|-
| 80%<sup>[[#1]]</sup> of MDN visitors understand that MDN is powered by Mozilla (baseline: 52%)
| Evaluate the impact of SEO recommendations on CTR
| h. Define 2017 brand strategy for MDN as a Mozilla property that balances core brand attributes (browser agnostic vs powered by Mozilla)
* Perform 2 less-complex development tasks for SEO gains
* 8 experiments from SEO recommendations executed
|-
|-
| Support emerging technologies and upcoming Firefox releases
| Complete static examples (excl. APIs)
| i. Publish 10 reference pages and tutorials about CSS grids<br/>
* Complete examples for all of JS
j. Publish 10 reference pages and tutorials about WebAssembly<br/>
* Complete 60 CSS output examples
k. Document new APIs for PWA for marketing push<br/>
* Complete HTML examples
l. Document DevTools features of Firefox 52 and 53<sup>[[#2]]</sup><br/>
* Plan API examples
m, n. (removed from plan)
|-
|-
| Move MDN to a sustainable tech stack to ensure uptime doesn't go below 99.9%
| Launch A/B test of final live sample code editor
| 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%.
| Content updates for Firefox 56/57 release support
| At least 1 editor offers integrated access to MDN compat data by end of 2017
* Firefox 56 release support
| p.Validate demand for compat data plan with editor developers <br/>
* Firefox 57 release support
q. Complete prototype for compat data as defined in budget plan
* CSS box alignment
* <input type=””> ref updates
* Flash to HTML5 transition
|-
| 100% of production traffic on AWS to provide stable technical foundation for MDN
* Serve maintenance mode from AWS with production traffic
* Serve dev R/W site from AWS
|-
| style="vertical-align:top;"  rowspan=2 |80% of MDN visitors to understand that MDN is powered by Mozilla (Baseline: 52%)
| Complete redesign for home page, all article pages, and all landing pages
* home page updated
* article pages updated
* landing pages updated
|-
| Run brand perception survey on MDN
|-
| style="vertical-align:top;" rowspan=2|At least 1 editor offers integrated access to MDN compat data by end of 2017
| style="vertical-align:top;" | Complete migration of 100% of compat data
* JS compat data complete
* CSS compat data complete
* HTML compat data complete
* API compat data complete
|-
| [https://docs.google.com/document/d/1qse7VhMVWN2WnIcP56nwhoHpP3V1xnAQTWEIfWUwWVo/edit Sign up one editor vendor for inclusion of compat data by end of 2017]
|-
| style="vertical-align:top;" rowspan=2|Launch experiments with 2 new types of community/contribution programs that help Mozilla promote web standards usage to developers
|-
| style="vertical-align:top;" | Deliver strategy and plan to establish and build a thriving core MDN Community that goes beyond casual editorial improvement of our documentation.
* Investigate refocusing MDN Community strategy on attracting and retaining core contributors on MDN
* Define and implement an onboarding process for institutional contributors
|-
|-
|
|Increase the first quartile<sup>[[#3]]</sup> of  3-week contributor retention to 3% from 1.48% (2016-H2 baseline).
| r. Redefine and begin re-implementing contributor pathways.<br/>
s. Run and analyze 5 contributor engagement experiments to select proven tactics for increasing retention
|}
|}
<ol>
<li id="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.</li>
<li id="2">We aim to document DevTools features  immediately after the Aurora launch.</li>
<li id="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.</li>
</ol>


* [[Engagement/MDN_Durable_Team/Accountability/2017#Q2_Key_Results|2017 Q2 Key Results]]
* [[Engagement/MDN_Durable_Team/Accountability/2017#Q1_Key_Results|2017 Q1 Key Results]]
* [[Engagement/MDN_Durable_Team/Accountability/2016|2016 Quarterly Targets]]
* [[Engagement/MDN_Durable_Team/Accountability/2016|2016 Quarterly Targets]]


Line 103: Line 113:
{| class="wikitable"
{| class="wikitable"
! Task Board !! Start !! End !! Demo/Outcomes
! Task Board !! Start !! End !! Demo/Outcomes
|-
| colspan="4" | 2017 Q2
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q2-sprint-1?kanban-status=649183 Sprint 1]
| April 3 || April 18
|
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q2-sprint-2 Sprint 2]
| April 24 || May 9
|
|-
| Sprint 3
| May 15 || May 30
|
|-
| Sprint 4
| June 5 || June 20
|
|-
|-
| colspan="4" | 2017 Q1
| colspan="4" | 2017 Q1
Line 112: Line 140:
|[https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q1-sprint-1-1?kanban-status=649183 Sprint 1]
|[https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q1-sprint-1-1?kanban-status=649183 Sprint 1]
| January 25 || February 7
| January 25 || February 7
|
| [https://groups.google.com/forum/#!topic/mozilla.mdn/4Slmxts-bIU demo summary]
|-
|-
| Sprint 2
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q1-sprint-2 Sprint 2]
| February 13 || February 28  
| February 13 || February 28  
|
| [https://docs.google.com/presentation/d/1_z7jkfqz2gkgWhdCZgTB-m5bXD8kpOpO2iUuxEOoZMM/edit#slide=id.p4 demo slides]; [https://groups.google.com/d/msg/mozilla.mdn/kH74h-YlhPw/h4mVIrP1AQAJ demo summary]
|-
|-
| Sprint 3
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q1-sprint-3-2 Sprint 3]
| March 6 || March 21
| March 6 || March 21
|
| [https://groups.google.com/forum/#!topic/mozilla.mdn/lEFGcwIKMVQ demo summary]; [https://docs.google.com/presentation/d/1Zl3TCCWhke8PEGulZZkjr0kNQ6Ksx7KvLJZ1VhVW8H8/edit?usp=sharing slides about User Testing]
|-
|-
| colspan="4" | 2016 Q4
| colspan="4" | 2016 Q4
Line 177: Line 205:


== Relevant Links ==
== Relevant Links ==
* [https://docs.google.com/spreadsheets/d/1K8RDKNO-oeimbRNBEWJEnKIPeJUEkPNXrMgmUmmgmMY/edit?usp=sharing Per-sprint user stories]
* [[Engagement/MDN_Durable_Team/Processes|MDN Durable team processes]]
* [[Engagement/MDN_Durable_Team/Processes|MDN Durable team processes]]
* [[Engagement/MDN_Durable_Team/Agile_glossary|Agile glossary]]
* [[Engagement/MDN_Durable_Team/Agile_glossary|Agile glossary]]
* [https://docs.google.com/spreadsheets/d/1TTMsjNUKWg5H7EZh6U7DWhC_ZYzb6jwn4---JDnJyGI/edit?usp=sharing MDN Roadmap]: [[Engagement/MDN_Durable_Team/Agile_glossary#Epic|Epics]] by theme and timeframe
* [https://tree.taiga.io/project/viya-mdn-durable-team/backlog MDN backlog] in Taiga
* [https://tree.taiga.io/project/viya-mdn-durable-team/backlog MDN backlog] in Taiga
* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1a36G1Qt2d8a9yptgm8ZnAtG6bTJtXho8KoNAQIxSV10/edit?usp=sharing Initial product backlog]
* [[Engagement/MDN_Durable_Team/Mentoring|How the MDN team handles mentoring]]
* [https://docs.google.com/spreadsheets/d/1TTMsjNUKWg5H7EZh6U7DWhC_ZYzb6jwn4---JDnJyGI/edit?usp=sharing 2016 MDN Roadmap]: [[Engagement/MDN_Durable_Team/Agile_glossary#Epic|Epics]] by theme and timeframe
* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1a36G1Qt2d8a9yptgm8ZnAtG6bTJtXho8KoNAQIxSV10/edit?usp=sharing 2016 Initial product backlog]
* [[Engagement/MDN_Durable_Team/Periodic_maintenance_checklist|MDN Periodic maintenance checklist]]
 


* [https://docs.google.com/a/mozilla.com/presentation/d/1VOIKQ7p9VtPGPCwUUxv6Dt5HYJMoHIFXe3I_XpJzrG8/edit?usp=sharing MDN Agile Playbook]
* [https://docs.google.com/a/mozilla.com/presentation/d/1VOIKQ7p9VtPGPCwUUxv6Dt5HYJMoHIFXe3I_XpJzrG8/edit?usp=sharing MDN Agile Playbook]
Line 195: Line 227:
! Meeting !! Time and Days !! Attendees !! Notes
! Meeting !! Time and Days !! Attendees !! Notes
|-
|-
| Sprint Planning Meeting || Every third Thursday, starting on April 21 || Core Team required|| Stakeholders may listen in.<br> This meeting lasts as long as it takes.
| Sprint Planning, Full Team Review || Every third Thursday, 8:30am PT<br>Planning meetings with sub-teams take place earlier in the same week. || Core Team required|| Stakeholders may listen in.<br> This meeting lasts as long as it takes.
|-
|-
| Daily Stand-Up <br>(15 minutes only) || 8:30am Pacific daily <br>  
| Daily Stand-Up <br>(15 minutes only) || 8:30am Pacific daily <br>  
* Content & Community: Monday & Wednesday, first week & second week of Sprint, Monday third week of Sprint<br>
* Content & Community: Monday & Wednesday, first week & second week of Sprint, Monday third week of Sprint<br>
* Development: Tuesday & Thursday, first week & second week of Sprint, Tuesday third week of Sprint |
* Development: Tuesday & Thursday, first week & second week of Sprint, Tuesday third week of Sprint  
| 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.
| 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.
| 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 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 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.
| Sprint Retrospective Meeting || every third Wednesday, starting on May 11 || Core Team only || No one else is invited to this meeting.
Line 228: Line 260:
* Email: mdn-team@mozilla.com
* Email: mdn-team@mozilla.com
* IRC: #mdn and #mdndev are our main channels (public conversations) / #team-awesome for private conversations.
* IRC: #mdn and #mdndev are our main channels (public conversations) / #team-awesome for private conversations.
* Mailing lists:
* Discussion forum: [https://discourse.mozilla-community.org/c/mdn MDN category on Discourse]
**[https://lists.mozilla.org/listinfo/dev-mdc dev-mdc] a.k.a. [https://groups.google.com/forum/#!forum/mozilla.dev.mdc mozilla.dev.mdc]
** [https://lists.mozilla.org/listinfo/dev-mdn dev-mdn] a.k.a. [https://groups.google.com/forum/#!forum/mozilla.dev.mdn mozilla.dev.mdn]
** [https://lists.mozilla.org/listinfo/mdn mdn] a.k.a. [https://groups.google.com/forum/#!forum/mozilla.mdn mozilla.mdn]
 
An explanation of these channels is on the [https://developer.mozilla.org/en-US/docs/MDN/Community/Conversations page for MDN community conversations]

Latest revision as of 04:29, 11 September 2020

Overview

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

The MDN Durable Team is now part of the Developer Outreach group in Emerging Technologies (ET), and is no longer part of Marketing/Engagement. The content team moved to ET in July 2017, and the dev team moved in March 2018.

Team Members

Role Name Area
Managers and planners
Product manager Kadir Topal
Writers' Team Manager, Content Lead Chris Mills
Agile coach Peter Chinaka
Makers
Content
Rachel Andrew CSS
Daniel Beck Browser compatibility
Web development Peter Bengtsson Back-end
Ryan Johnson Back-end
Schalk Neethling Front-end
Mustafa Al-Qinneh UX design

Accountability

Objectives and Key Results

What are Objectives and Key Results?

2017 Objectives and Q3 Key Results

Developer Outreach Q3 OKRs (mozilla.com logins only)

Developer Outreach 2017 Objective MDN Q3 Key Results
Increase number of MDN sessions 40% y/y Serve 39 million sessions on MDN (an increase of 11.2m sessions y/y)
Evaluate the impact of SEO recommendations on CTR
  • Perform 2 less-complex development tasks for SEO gains
  • 8 experiments from SEO recommendations executed
Complete static examples (excl. APIs)
  • Complete examples for all of JS
  • Complete 60 CSS output examples
  • Complete HTML examples
  • Plan API examples
Launch A/B test of final live sample code editor
Content updates for Firefox 56/57 release support
  • Firefox 56 release support
  • Firefox 57 release support
  • CSS box alignment
  • <input type=””> ref updates
  • Flash to HTML5 transition
100% of production traffic on AWS to provide stable technical foundation for MDN
  • Serve maintenance mode from AWS with production traffic
  • Serve dev R/W site from AWS
80% of MDN visitors to understand that MDN is powered by Mozilla (Baseline: 52%) Complete redesign for home page, all article pages, and all landing pages
  • home page updated
  • article pages updated
  • landing pages updated
Run brand perception survey on MDN
At least 1 editor offers integrated access to MDN compat data by end of 2017 Complete migration of 100% of compat data
  • JS compat data complete
  • CSS compat data complete
  • HTML compat data complete
  • API compat data complete
Sign up one editor vendor for inclusion of compat data by end of 2017
Launch experiments with 2 new types of community/contribution programs that help Mozilla promote web standards usage to developers
Deliver strategy and plan to establish and build a thriving core MDN Community that goes beyond casual editorial improvement of our documentation.
  • Investigate refocusing MDN Community strategy on attracting and retaining core contributors on MDN
  • Define and implement an onboarding process for institutional contributors


Sprint Schedule

Task Board Start End Demo/Outcomes
2017 Q2
Sprint 1 April 3 April 18
Sprint 2 April 24 May 9
Sprint 3 May 15 May 30
Sprint 4 June 5 June 20
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 demo summary; slides about User Testing
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, 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
  • Content & Community: Monday & Wednesday, first week & second week of Sprint, Monday third week of Sprint
  • Development: Tuesday & Thursday, first week & second week of Sprint, Tuesday third week of Sprint
 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.
  • Discussion forum: MDN category on Discourse
Retrieved from "https://wiki.allizom.org/index.php?title=Engagement/MDN_Durable_Team&oldid=1230750"