MozillaWiki

Engagement/MDN Durable Team: Difference between revisions

Page Discussion

Engagement/MDN Durable Team (view source)

Revision as of 04:29, 11 September 2020

18 bytes removed ,  11 September 2020
Updated team members
(mailings lists -> Discourse)
(Updated team members)
 
(21 intermediate revisions by 4 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|Team Lead]] || Kadir Topal ||
|colspan="3"| '''Managers and planners'''
|-
|-
| [[Engagement/MDN_Durable_Team/Agile_glossary#Scrum Master|Program 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="4" style="vertical-align:top;"| Content
| Agile coach
| William Bamberg
| Peter Chinaka
| WebExtensions
|
|-
|-
| Chris Mills
|colspan="3"| '''[[Engagement/MDN_Durable_Team/Agile_glossary#Maker|Makers]]'''
| Content Lead and Learning area
|-
|-
| Florian Scholz
|rowspan="3" style="vertical-align:top;"| Content
| Web
|-
|-
| Eric ("Sheppy") Shepherd
| Rachel Andrew
| Everything
| CSS
|-
|-
|rowspan="4" style="vertical-align:top;"| Web development
| Daniel Beck
| Stephanie Hobson
| Browser compatibility
| Front-end
|-
|-
| John Whitlock
|rowspan="5" style="vertical-align:top;"| Web development
| Peter Bengtsson
| Back-end
| Back-end
|-
|-
Line 40: Line 40:
| Front-end
| Front-end
|-
|-
| QA ||Matthew Brandt ||
| Mustafa Al-Qinneh
|-
| UX design
|}
|}


Line 47: 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 and Q2 Key Results====
====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 Q2 Key Results (with links to project documents)
|-  
|-  
|rowspan="2" 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)
|
|-
* Serve 38 million sessions on MDN (an increase of 10,8m sessions y/y)
| Evaluate the impact of SEO recommendations on CTR
* [https://docs.google.com/document/d/1WU8D4khiU43w6oqBfgQpbWundQxqwWy01qSUHchqsxs/edit Complete A/B test for “examples on top” for 100 CSS and JS pages.]
* Perform 2 less-complex development tasks for SEO gains
* [https://docs.google.com/document/d/1_4Rt3VVo8CJ0pdLK49vT4TcJIg1cqyMH-KQR0qDehhw/editComplete SEO Audit and have a prioritized backlog of items for implementation.]
* 8 experiments from SEO recommendations executed
* Support emerging technologies and upcoming Firefox releases
|-
** Update web platform docs for Firefox 54 Beta (DL: April 21th) and 55 Beta (DL: June 16th)
| Complete static examples (excl. APIs)
** WebVR 1.1 for Windows (DL: June 13th)
* Complete examples for all of JS
** Document modern clearfix and Masks phase 1
* Complete 60 CSS output examples
* Complete HTML examples
* Plan API examples
|-
| Launch A/B test of final live sample code editor
|-
|-
| 80%<sup>[[#1]]</sup> of MDN visitors understand that MDN is powered by Mozilla (baseline: 52%)
| Content updates for Firefox 56/57 release support
| * [https://docs.google.com/document/d/1GB4VA-IiR3hDyj0ETjhZs3tgZm059dp54azzWnMASjU/edit Initiate the separation between open web and Mozilla-specific documentation by moving at least one out of 24 product-specific projects out of MDN]
* Firefox 56 release support
* [https://docs.google.com/document/d/1y2fRYFpIFIDrMEwKenI5JwSHbYPtjn2EjEmN1nAftBo/edit 100% of MDN pages on open web docs will carry the new Mozilla brand identity]
* Firefox 57 release support
* [https://docs.google.com/document/d/1y2fRYFpIFIDrMEwKenI5JwSHbYPtjn2EjEmN1nAftBo/edit Establish a quarterly measurement for the “MDN is powered by Mozilla” objective (from annually today)]
* CSS box alignment
* <input type=””> ref updates
* Flash to HTML5 transition
|-
|-
| The number of developers who self-report as testing and debugging for Firefox is 70%.
| 100% of production traffic on AWS to provide stable technical foundation for MDN
| At least 1 editor offers integrated access to MDN compat data by end of 2017
* Serve maintenance mode from AWS with production traffic
|  
* Serve dev R/W site from AWS
* [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 |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>[[#2]]</sup> of  3-week contributor retention to 3% from 1.48% (2016-H2 baseline).
|
* [https://docs.google.com/document/d/1KrODOAkYPCnH44wOgVH2u6goIOTzBLoxgb28v-L0FL0/edit?usp=sharing Migrate all 3 public MDN-related mailing lists to a single Discourse forum to lower the barrier for entry]
|}
|}
<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">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/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 186: Line 209:
* [[Engagement/MDN_Durable_Team/Agile_glossary|Agile glossary]]
* [[Engagement/MDN_Durable_Team/Agile_glossary|Agile glossary]]
* [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
* [[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/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]
* [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]]




Jswisher
canmove, Confirmed users
1,953

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1173995...1230750"