Engagement/MDN Durable Team: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎Sprint Schedule: Q4 sprint 3)
(Updated team members)
 
(53 intermediate revisions by 5 users not shown)
Line 1: Line 1:


== Overview ==
== Overview ==
{{admon/note|[https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/working-sprint-backlog Q4 Sprint 3] started on November 21!}}
{{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|Scrum Master]] || 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="3" style="vertical-align:top;"| Web development
|rowspan="5" style="vertical-align:top;"| Web development
| Stephanie Hobson
| Peter Bengtsson
| Front-end
|-
| John Whitlock
| Back-end
| Back-end
|-
|-
Line 40: 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 50: 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]?
====2016 Q4====
====2017 Objectives and Q3 Key Results====
{| class="wikitable"  
[https://docs.google.com/a/mozilla.com/spreadsheets/d/1tPEf3VVkLtaQK_3sXx_Sb3nK7ep4ZVlaXIL9v1gM4ZM/edit?usp=sharing|Complete Developer Outreach Q3 OKRs] (mozilla.com logins only)
! Area !! Objective !! Key Result(s)
{| class="wikitable"
|- style="vertical-align:top;"
! Developer Outreach 2017 Objective
| Coordination with Developer Marketing
! MDN Q3 Key Results
| Sign up 150,000 developers for a web-development focused email newsletter
|-  
|
| style="vertical-align:top;" rowspan=6|Increase number of MDN sessions 40% y/y
* 50,000 sign-ups for a web-development focused email newsletter via MDN.
| style="vertical-align:top;" |Serve 39 million sessions on MDN (an increase of 11.2m sessions y/y)
|- style="vertical-align:top;"
|-
| Content
| Evaluate the impact of SEO recommendations on CTR
| Increase number of successful sessions per year by xx%<sup>[[#1]]</sup> by 2018
* Perform 2 less-complex development tasks for SEO gains
|  
* 8 experiments from SEO recommendations executed
* Deliver 3 reports covering a) stakeholder agreed upon strategy for MDN for 2017 and beyond, b) resource needs to execute on this strategy, and c) define and agree on 3-5 objectives for MDN in 2017
|-
* Deliver 20 reference pages and 5 tutorials about security-related features of HTTP. (Next step of what has been defined in Q3 research)
| Complete static examples (excl. APIs)
* In the Learning Area, publish 12 tutorials about testing, accessibility and Web APIs
* Complete examples for all of JS
* Publish documentation for all identified P1 topics of WebExtensions.
* Complete 60 CSS output examples
* Evaluate and document the 76 new developer features of Firefox 50 by the release<sup>[[#2]]</sup> of Firefox 50.
* Complete HTML examples
* Evaluate and document the 77* new developer features of Firefox 51 by the release 50.0.1<sup>[[#3]]</sup>
* Plan API examples
|- style="vertical-align:top;"
|-
| Development
| Launch A/B test of final live sample code editor
| Move MDN to a sustainable tech stack (ensure uptime doesn't go below 99.9%)
|-
|  
| Content updates for Firefox 56/57 release support
* Complete at least the top 5 of 8 prioritized key items listed in the [https://docs.google.com/document/d/1q0rNBieya_9NPqjWYX93_QwEge-K2wqLPPvdtZGyinE/edit#heading=h.s2f04kcitoh9 MDN development] plan to move MDN over to AWS
* Firefox 56 release support
|- style="vertical-align:top;"
* Firefox 57 release support
| Coordination with Brand Marketing
* CSS box alignment
| Get xx%<sup>[[#1]]</sup> of MDN visitors to understand that MDN is powered by Mozilla (currently 52%)
* <input type=””> ref updates
|  
* Flash to HTML5 transition
* Achieve xx% click-through rate on MDN home page for the End of Year Donation campaign
|-
|- style="vertical-align:top;"
| 100% of production traffic on AWS to provide stable technical foundation for MDN
| Community
* Serve maintenance mode from AWS with production traffic
| Set up community strategy
* Serve dev R/W site from AWS
|
|-
* Run X [[Engagement/MDN Durable Team/Community hypotheses|hypothesis testing]] to check our assumption
| 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
|-
|}
|}
<ol>
<li id="1">Actual target will be determined once 2017 strategy is defined.</li>
<li id="2">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%)</li>
<li id="3">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.</li>
</ol>


===Initiatives and Deliverables===
What are [[Engagement/MDN_Durable_Team/Agile_glossary#Initiative|initiatives]] and [[Engagement/MDN_Durable_Team/Agile_glossary#Deliverable|deliverables]]?


====2016 Q3====
 
* [[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]]
 
== Sprint Schedule ==
{| class="wikitable"
{| class="wikitable"
! Area !! Initiative !! Deliverable(s)
! Task Board !! Start !! End !! Demo/Outcomes
|-
|-
| Meta
| colspan="4" | 2017 Q2
| Define a clear set of goals for MDN and a roadmap to achieve them that support our overall Developer Marketing priorities.
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q2-sprint-1?kanban-status=649183 Sprint 1]
| April 3 || April 18
|
|
* Roadmap that represents the strategic contribution of MDN to Developer Marketing objectives and KPIs;
* establish baseline for Successful Sessions KPI
|-
|-
| Development
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q2-sprint-2 Sprint 2]
| Move MDN to a sustainable technology stack.
| April 24 || May 9
|
|
* Transition away from Persona.
* Establish a development environment using Docker.
|-
|-
| Content
| Sprint 3
| Complete, simplify, and extend the reach of the documentation of core web technologies for mainstream Web developers.
| May 15 || May 30
|
|
* HTTP basics ('''To be delivered this quarter''');
* JS introduction ('''To be delivered this quarter''');
* page structure updated for HTML reference (''To be started this quarter'');
* overview written for most-requested APIs (''To be started this quarter'').
|-
|-
| Community
| Sprint 4
| Taking stock
| June 5 || June 20
|
|
* [https://drive.google.com/open?id=1_RYq2OX6STvvZ3Wrl6OpB8pkGsXAjbxzUxO5I7qNvTM Research: Impact and involvement of community with MDN content (2013 - Mid 2016)]
* [https://docs.google.com/document/d/1KDmEtXnCPren7At8vAmCN3gwqqpnkbBo0PYo-lVnQ2w/edit?usp=sharing Research: MDN Stakeholder Expectations about MDN Community]
* [https://drive.google.com/open?id=13mvbjcc7TQI4kQ6ItU3iUbg2E890l2Pn3ESiYy2XN8E Research: MDN Community Impact (2013 - Mid 2016)]
* [https://drive.google.com/open?id=1dFtPeOBnChDq3gB50LEwZHO0PuGL25wXLOKvLaGFTlQ Research: MDN Contributors survey (Mid 2016)]
* [https://docs.google.com/document/d/14-wuLyDE8NxmIhWSaTP6PuUy1bMklYh7Hrv41abNCZk/edit?usp=sharing MDN Community: Vision & Success]
|}
====2016 Q2====
{| class="wikitable"
! Area !! Initiative !! Deliverable(s)
|-
|-
| Meta
| colspan="4" | 2017 Q1
| Define a clear set of goals for MDN and a roadmap to achieve them that furthers our overall Developer Marketing priorities.
|-
| Goals and roadmap
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q1-sprint-1?kanban-status=649183 Sprint 0]
| January 9 || January 24
| No demo; the MDN team started early, so work before Sprint 1's official start is "Sprint 0".
|-
|[https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q1-sprint-1-1?kanban-status=649183 Sprint 1]
| January 25 || February 7
| [https://groups.google.com/forum/#!topic/mozilla.mdn/4Slmxts-bIU demo summary]
|-
|-
| Development
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/2017-q1-sprint-2 Sprint 2]
| Mitigate our current spam problem so users continue to trust MDN.
| February 13 || February 28
| Implementation of spam mitigation solution
| [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]
|-
|-
| Content
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q1-sprint-3-2 Sprint 3]
| Establish value proposition for web developers & designers to build, test and debug websites and web apps across browsers.
| March 6 || March 21
| MDN content focus on cross-browser APIs, Web Extensions, and Dev Tools
| [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]
|}
 
== Sprint Schedule ==
{| class="wikitable"
! Task Board !! Start !! End !! Demo/Outcomes
|-
|-
| colspan="3" | 2016 Q4
| colspan="4" | 2016 Q4
|-
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q4-sprint-1-1 Sprint 1]  
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q4-sprint-1-1 Sprint 1]  
| 10 Oct || 25 Oct
| 10 October || 25 October
|  [https://docs.google.com/presentation/d/1NneuyvcnIklv9xFkK9M10dmz3zm6nDWp4sahhRrdwiU/edit?usp=sharing Demo]
|  [https://docs.google.com/presentation/d/1NneuyvcnIklv9xFkK9M10dmz3zm6nDWp4sahhRrdwiU/edit?usp=sharing Demo]
|-
|-
Line 159: Line 161:
|-
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/working-sprint-backlog Sprint 3]
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/working-sprint-backlog Sprint 3]
| Nov 21 || Dec 2
| November 21 || December 2
|
| No demo due to All-Hands
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/next-sprint-working-backlog Sprint 4]
| December 12 || December 30
| No demo, due to lots of PTO
|-
|-
| colspan="3" | 2016 Q3
| colspan="4" | 2016 Q3
|-
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/sprint-3-1557 Sprint 1]  
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/sprint-3-1557 Sprint 1]  
Line 184: Line 190:
| [https://docs.google.com/presentation/d/1YJ171Ei9e4PS8g50yj12pfZ6q1N8XiI2saHeTT_rPbk/edit?usp=sharing Demo]
| [https://docs.google.com/presentation/d/1YJ171Ei9e4PS8g50yj12pfZ6q1N8XiI2saHeTT_rPbk/edit?usp=sharing Demo]
|-
|-
| colspan="3"| 2016 Q2
| colspan="4"| 2016 Q2
|-
|-
| [https://mozilla.kanbanery.com/projects/68288/board/?key=775e5e65ceb38d40d0dc1a4e481901387d08abdf Sprint 1]  
| [https://mozilla.kanbanery.com/projects/68288/board/?key=775e5e65ceb38d40d0dc1a4e481901387d08abdf Sprint 1]  
Line 199: 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 217: 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> 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.
| 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>
* 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 || 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 238: Line 251:
* MDN Content Coordination meeting: Tuesdays, 9.00AM  
* MDN Content Coordination meeting: Tuesdays, 9.00AM  
* MDN Weekly Doc Request Triage: Tuesdays, 9:30AM  
* MDN Weekly Doc Request Triage: Tuesdays, 9:30AM  
* MDN Opportunity Review: Wednesdays, 9:00AM
* MDN Weekly Bug Swat: Fridays, 8:00AM
* MDN Weekly Bug Swat: Fridays, 8:00AM
* MDN Community Meeting:  Bi-weekly, Wednesdays, 10:00AM


See full [https://calendar.google.com/calendar/embed?src=mozilla.com_2d35383434313235392d323530@resource.calendar.google.com&ctz=GMT&pli=1 calendar] for dates and participation info.
See full [https://calendar.google.com/calendar/embed?src=mozilla.com_2d35383434313235392d323530@resource.calendar.google.com&ctz=GMT&pli=1 calendar] for dates and participation info.
Line 247: 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

Note.png

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"