Engagement/MDN Durable Team: Difference between revisions

Updated team members
(Updated team members)
 
(29 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="5" style="vertical-align:top;"| Content
| Agile coach
| William Bamberg
| Peter Chinaka
| Add-ons and extensions
|
|-
| Chris Mills
| Learning area
|-
| Jean-Yves Perrier
| Content lead (and Web)
|-
|-
| Florian Scholz
|colspan="3"| '''[[Engagement/MDN_Durable_Team/Agile_glossary#Maker|Makers]]'''
| Web
|-
|-
| Eric ("Sheppy") Shepherd
|rowspan="3" style="vertical-align:top;"| Content
| Everything
|-
|-
|rowspan="4" style="vertical-align:top;"| Web development
| Rachel Andrew
| Stephanie Hobson
| CSS
| Front-end
|-
|-
| Jon Petto
| Daniel Beck
| Front-end
| Browser compatibility
|-
|-
| John Whitlock
|rowspan="5" style="vertical-align:top;"| Web development
| Peter Bengtsson
| Back-end
| Back-end
|-
|-
Line 43: Line 37:
| Back-end
| Back-end
|-
|-
| QA ||Matthew Brandt ||  
| Schalk Neethling
| Front-end
|-
|-
| Community || Janet Swisher ||
| Mustafa Al-Qinneh
| UX design
|}
|}


Line 51: 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 Q1 Key Results
|-  
|-  
|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)
|-
* Complete A/B test for “examples on top” for 100 CSS and JS pages.
| Evaluate the impact of SEO recommendations on CTR
* Complete SEO Audit and have a prioritized backlog of items for implementation.
* Perform 2 less-complex development tasks for SEO gains
* Support emerging technologies and upcoming Firefox releases
* 8 experiments from SEO recommendations executed
** Update web platform docs for Firefox 54 Beta (DL: April 21th) and 55 Beta (DL: June 16th)
|-
** WebVR 1.1 for Windows (DL: June 13th)
| Complete static examples (excl. APIs)
** Document modern clearfix and Masks phase 1
* 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
|-
| 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]
|-
|-
| 80%<sup>[[#1]]</sup> of MDN visitors understand that MDN is powered by Mozilla (baseline: 52%)
| 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
| * Initiate the separation between open web and Mozilla-specific documentation by moving at least one out of 24 product-specific projects out of MDN
* 100% of MDN pages on open web docs will carry the new Mozilla brand identity
* Establish a quarterly measurement for the “MDN is powered by Mozilla” objective (from annually today)
|-
|-
| The number of developers who self-report as testing and debugging for Firefox is 70%.
| 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.
| At least 1 editor offers integrated access to MDN compat data by end of 2017
* Investigate refocusing MDN Community strategy on attracting and retaining core contributors on MDN
| * Sign up one editor vendor for inclusion of compat data by end of 2017
* 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).
| * 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#Q1_Key_Results|Q1 Key Results]]
 
 
* [[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 91: 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 108: Line 148:
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q1-sprint-3-2 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 165: 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 216: 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]: Discussions about MDN content
** [https://lists.mozilla.org/listinfo/dev-mdn dev-mdn] a.k.a. [https://groups.google.com/forum/#!forum/mozilla.dev.mdn mozilla.dev.mdn]: Discussions about MDN platform development
** [https://lists.mozilla.org/listinfo/mdn mdn] a.k.a. [https://groups.google.com/forum/#!forum/mozilla.mdn mozilla.mdn]: Discussions for all stakeholders about planning and high-level issues
 
An more detailed explanation of these channels is on the [https://developer.mozilla.org/en-US/docs/MDN/Community/Conversations page for MDN community conversations].
canmove, Confirmed users
1,953

edits