View source for Engagement/MDN Durable Team


== 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!}}
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.

==Team Members==
{| class="wikitable"
! Role !! Name !! Area
|-
| [[Engagement/MDN_Durable_Team/Agile_glossary#Product Owner|Product Owner]] || Kadir Topal ||
|-
| [[Engagement/MDN_Durable_Team/Agile_glossary#Scrum Master|Project Manager]] || Vik Iya ||
|-
|colspan="3"| [[Engagement/MDN_Durable_Team/Agile_glossary#Maker|Makers]]
|-
|rowspan="5" style="vertical-align:top;"| 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
|-
|rowspan="4" style="vertical-align:top;"| Web development
| Stephanie Hobson <br/>(temporarily unavailable)
| Front-end
|-
| Jon Petto
| 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 [https://en.wikipedia.org/wiki/OKR Objectives and Key Results]?
====2017 Objectives and Q1 Key Results====
{| class="wikitable"
! Marketing 2017 Objective
! Marketing 2017 Key Result / MDN 2017 Objective
! 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;" | 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.
| 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%)
| h. Define 2017 brand strategy for MDN as a Mozilla property that balances core brand attributes (browser agnostic vs powered by Mozilla)
|-
| Support emerging technologies and upcoming Firefox releases
| i. Publish 10 reference pages and tutorials about CSS grids<br/>
j. Publish 10 reference pages and tutorials about WebAssembly<br/>
k. Document new APIs for PWA for marketing push<br/>
l. Document DevTools features of Firefox 52 and 53<sup>[[#2]]</sup><br/>
m, n. (removed from plan)
|-
| Move MDN to a sustainable tech stack to ensure uptime doesn't go below 99.9%
| 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%.
| At least 1 editor offers integrated access to MDN compat data by end of 2017
| p.Validate demand for compat data plan with editor developers <br/>
q. Complete prototype for compat data as defined in budget plan
|-
| 
|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/2016|2016 Quarterly Targets]]

== Sprint Schedule ==
{| class="wikitable"
! Task Board !! Start !! End !! Demo/Outcomes
|-
| colspan="4" | 2017 Q1
|- 
| [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
|
|-
| Sprint 2
| February 13 || February 28 
|
|-
| Sprint 3
| March 6 || March 21
|
|-
| Sprint 4
| March 27 || April 11
|
|-
| colspan="4" | 2016 Q4
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q4-sprint-1-1 Sprint 1] 
| 10 October || 25 October
|  [https://docs.google.com/presentation/d/1NneuyvcnIklv9xFkK9M10dmz3zm6nDWp4sahhRrdwiU/edit?usp=sharing Demo]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q4-sprint-2-1 Sprint 2]
| 31 Oct || 15 Nov
| [https://docs.google.com/presentation/d/15_v5OSMiOXMUANtTw6_XUQ8sZ-cZxdz91cviH1w3Ck4/edit#slide=id.p4 Demo]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/working-sprint-backlog Sprint 3]
| 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="4" | 2016 Q3
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/sprint-3-1557 Sprint 1] 
| 27 June || 12 July  
| [https://docs.google.com/presentation/d/1mycek61a_icdxc0jsksfX9hnB5ovUQ35VqyohPzX6yE/edit?usp=sharing Demo]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q3-sprint-2-1 Sprint 2]
| 18 July || 2 August
|
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q3-sprint-3-1 Sprint 3]
| 8 August || 23 August
| [https://docs.google.com/presentation/d/1ooNMa3hkpR9qFX2806aN8ZehCBgTtGxa1ddI2PrmzEU/edit?usp=sharing Demo]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q3-sprint-4-1 Sprint 4]
| 29 August || 13 September
| [https://docs.google.com/presentation/d/1R-lluQZP67AAYBL_bfiz8SYNuE-ZPlF9sJJsQhoUZFE/edit?usp=sharing Demo]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/q3-sprint-5-draft Sprint 5]
| 19 September || 4 October
| [https://docs.google.com/presentation/d/1YJ171Ei9e4PS8g50yj12pfZ6q1N8XiI2saHeTT_rPbk/edit?usp=sharing Demo]
|-
| colspan="4"| 2016 Q2
|-
| [https://mozilla.kanbanery.com/projects/68288/board/?key=775e5e65ceb38d40d0dc1a4e481901387d08abdf Sprint 1] 
| 25 April || 10 May
| [https://drive.google.com/open?id=1DEBELSYe8nQezlGa13A_qDwmvWiuckjaeAt_YecVZCU Demo]
|-
| [https://tree.taiga.io/project/viya-mdn-durable-team/taskboard/sprint-2-2059 Sprint 2]
| 16 May || 31 May
| [https://docs.google.com/presentation/d/1gbf6EsNVuPb1EJhynEYqNTAsL3QPwZGzEGaxY46AR_M/edit?usp=sharing Demo]
|-
| Sprint 3 
| colspan="2" | Mini-sprint weeks of 6-10 and 20-24 June 
|}

== Relevant Links ==
* [[Engagement/MDN_Durable_Team/Processes|MDN Durable team processes]]
* [[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://docs.google.com/a/mozilla.com/spreadsheets/d/1a36G1Qt2d8a9yptgm8ZnAtG6bTJtXho8KoNAQIxSV10/edit?usp=sharing Initial product backlog]

* [https://docs.google.com/a/mozilla.com/presentation/d/1VOIKQ7p9VtPGPCwUUxv6Dt5HYJMoHIFXe3I_XpJzrG8/edit?usp=sharing MDN Agile Playbook]
* [https://docs.google.com/a/mozilla.com/document/d/1blL_Jvu3FhPMTE7PkrqvVLiUqAYDvnmCTTIK5s2b-Yg/edit?usp=sharing MDN's Definition of Done]
* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1fV2_wiA_wwVwK8k69lr1wU-LkkOuOmGOxvFWcgacy0Y/edit?usp=sharing Project Issues / Risks / Requests Log]
* [https://drive.google.com/a/mozilla.com/folderview?id=0B0Nv3O9ZjM0ZNzlabk5La1RFZlU&usp=sharing Meeting Notes]

==Meetings==
'''Sprint Meetings:''' 

{| class="wikitable"
|-
! 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.
|-
| 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.
|-
| 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 Opportunity Review: Wednesdays, 9:00AM
* MDN Weekly Bug Swat: Fridays, 8: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.

== Communication Channels ==

* Email: mdn-team@mozilla.com
* IRC: #mdn and #mdndev are our main channels (public conversations) / #team-awesome for private conversations.
* Mailing lists:
**[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]