Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Key Result score card, the fourth
2 views
Skip to first unread message
Kadir Topal
Mar 7, 2017, 9:18:48 AM3/7/17
to MDN Team, mdn, Benjamin Sternthal, David Tenser, Peter German, Bradley Cohen, Ali Spivak, Danielle Vincent
Hey everyone,
We are a big team with lots of projects moving at the same time and a ton of amazing working being done every week, so I’d like to try regular Key Result updates this quarter to keep everyone on the same page. That’s me sending an email at the end of the week or sprint, giving everyone a snapshot of my understanding of where we are with each KR. I’ll certainly get some of these wrong and that would be a great opportunity to update me and others on what’s really going on. Alternatively, I can also post this to a GoogleDoc that we can edit together. Let me know if you have a preference.
A good place for a quick glance at status is here: https://docs.google.com/spreadsheets/d/1ZpzD9SAYKl9hBS-MZSL3NUAqcQjrdIBsfCBZRUvLJ80/edit#gid=0
So, without further ado, here’s the fourth one :)
Objective: 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% y/y
KR: Complete qualitative user test for action oriented developers and rewrite first selection of articles in preparation of quantitative test in Q2.
Project page: https://docs.google.com/document/d/1WU8D4khiU43w6oqBfgQpbWundQxqwWy01qSUHchqsxs/edit <https://docs.google.com/document/d/1WU8D4khiU43w6oqBfgQpbWundQxqwWy01qSUHchqsxs/edit>
User testing will commence this week with sharing of results in the following weeks.
The A/B testing infrastructure is being developed, should be ready once we have results from the user testing.
I’m optimistic that we’ll have this KR done by the end of Q1
KR: Complete SEO Audit and SEO/SEM rollout prioritization
Project page: https://docs.google.com/document/d/1_4Rt3VVo8CJ0pdLK49vT4TcJIg1cqyMH-KQR0qDehhw/edit <https://docs.google.com/document/d/1_4Rt3VVo8CJ0pdLK49vT4TcJIg1cqyMH-KQR0qDehhw/edit>
We got approval for the two main items of the SEO audit (technical audit and content opportunities assessment)
We’re now putting both through the contract signing process
We’ll most likely be able to start the audit this quarter, but results will only come in through Q2-
KR: Document the top 30 JS errors shown to developers (to be linked to from Firefox)
Started in this sprint.
Looks like we’ll hit this KR too.
KR: Document Advanced HTTP <https://tree.taiga.io/project/viya-mdn-durable-team/epic/1268>topics to offer complete coverage of an important web standard on MDN (to be linked to from Firefox)
The HTTP topic is complete for this quarter.
We’ve decided to break out HTTP 2.0 as its own topic for Q2
KR: Document the 101 web platform changes in Firefox 52 <https://tree.taiga.io/project/viya-mdn-durable-team/epic/1501> by the release of Firefox 52 and in Firefox 53 by the release of beta
Done for Fx 52: JS and DOM, HTTP WebExtensions, Layout, Media
Done for Fx 53: Layout, WebExtensions
In Progress for Fx53: JS, Dom, Media
Firefox 52 items were ready by release and it looks like most items for Firefox 53 should be ready this week.
KR: Activate 2 new localizers in one locale, prioritized by Dev Marketing
We have identified a target locale (pt-BR) and we have promising feedback from the locale
We should be able to define goals for the locale and get buy-in with 2 new localizers in the current sprint
Objective: 80% of MDN visitors to understand that MDN is powered by Mozilla (Baseline: 52%)
KR: Define 2017 brand strategy for MDN as a Mozilla property that balances core brand attributes (browser agnostic vs powered by Mozilla)
Project page: https://docs.google.com/document/d/1y2fRYFpIFIDrMEwKenI5JwSHbYPtjn2EjEmN1nAftBo/edit <https://docs.google.com/document/d/1y2fRYFpIFIDrMEwKenI5JwSHbYPtjn2EjEmN1nAftBo/edit>
Brad and Yuliya presented preliminary results to the team and will present refined results in 2 weeks
We should be able to present our brand strategy to leadership later this month
Objective: Support emerging technologies and upcoming Firefox releases
KR: Publish 10 reference pages and tutorials about CSS grids
Completed
KR: Publish 10 reference pages and tutorials about WebAssembly
Completed
KR: Document new APIs for PWA for marketing push
IntersectionObserver moved to Firefox 54, so not this quarter. There is no more work left for this KR.
KR: Document DevTools features of Firefox 52 and 53 beta
Completed
Objective: Move MDN to a sustainable tech stack to ensure uptime doesn’t go below 99.9%
KR: Reduce monthly hours of site downtime due to planned db maintenance to zero
Work on the maintenance mode has started. Deployment planned for this sprint.
Looks like we are on track with this KR.
Objective: At least 1 editor offers integrated access to MDN compat data by end of 2017
KR: Validate demand for compat data plan with editor developers
Project page: https://docs.google.com/document/d/1qse7VhMVWN2WnIcP56nwhoHpP3V1xnAQTWEIfWUwWVo/edit <https://docs.google.com/document/d/1qse7VhMVWN2WnIcP56nwhoHpP3V1xnAQTWEIfWUwWVo/edit>
completed
KR: Complete prototype for compat data as defined in budget plan <https://docs.google.com/document/d/1aNbbqwdbI_NQcSvtAKDKi6kdBTR2FeEe-B5Iee8RHjs/edit#>
This will depend on the result of the KR above, but one pre-requisit is having machine readable compat data
We’ve split the schema work out into the discussion, test, and the roll out.
We need to make a decision on what makes sense as a prototype here. Ideally it’s something that will allow us to work with editor vendors for inclusion in editors in Q2
Objective: Increase the first quartile of 3-week contributor retention to 3% from 1.48% (2016-H2 baseline).
KR: Redefine and begin re-implementing contributor pathways.
Pathway for localizers has been completed
Pathways for English language contributors, promoters and Kuma editors is in this sprint
KR: Run and analyze 5 contributor engagement experiments <https://wiki.mozilla.org/Engagement/MDN_Durable_Team/Community_hypotheses> to select proven tactics for increasing retention
We have analysis of 2 experiments in the sprint: collective thank you emails to all new contributors, and personalized thank you emails for specific work.
We should be able to finish this in the current sprint
—Kadir
We are a big team with lots of projects moving at the same time and a ton of amazing working being done every week, so I’d like to try regular Key Result updates this quarter to keep everyone on the same page. That’s me sending an email at the end of the week or sprint, giving everyone a snapshot of my understanding of where we are with each KR. I’ll certainly get some of these wrong and that would be a great opportunity to update me and others on what’s really going on. Alternatively, I can also post this to a GoogleDoc that we can edit together. Let me know if you have a preference.
A good place for a quick glance at status is here: https://docs.google.com/spreadsheets/d/1ZpzD9SAYKl9hBS-MZSL3NUAqcQjrdIBsfCBZRUvLJ80/edit#gid=0
So, without further ado, here’s the fourth one :)
Objective: 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% y/y
KR: Complete qualitative user test for action oriented developers and rewrite first selection of articles in preparation of quantitative test in Q2.
Project page: https://docs.google.com/document/d/1WU8D4khiU43w6oqBfgQpbWundQxqwWy01qSUHchqsxs/edit <https://docs.google.com/document/d/1WU8D4khiU43w6oqBfgQpbWundQxqwWy01qSUHchqsxs/edit>
User testing will commence this week with sharing of results in the following weeks.
The A/B testing infrastructure is being developed, should be ready once we have results from the user testing.
I’m optimistic that we’ll have this KR done by the end of Q1
KR: Complete SEO Audit and SEO/SEM rollout prioritization
Project page: https://docs.google.com/document/d/1_4Rt3VVo8CJ0pdLK49vT4TcJIg1cqyMH-KQR0qDehhw/edit <https://docs.google.com/document/d/1_4Rt3VVo8CJ0pdLK49vT4TcJIg1cqyMH-KQR0qDehhw/edit>
We got approval for the two main items of the SEO audit (technical audit and content opportunities assessment)
We’re now putting both through the contract signing process
We’ll most likely be able to start the audit this quarter, but results will only come in through Q2-
KR: Document the top 30 JS errors shown to developers (to be linked to from Firefox)
Started in this sprint.
Looks like we’ll hit this KR too.
KR: Document Advanced HTTP <https://tree.taiga.io/project/viya-mdn-durable-team/epic/1268>topics to offer complete coverage of an important web standard on MDN (to be linked to from Firefox)
The HTTP topic is complete for this quarter.
We’ve decided to break out HTTP 2.0 as its own topic for Q2
KR: Document the 101 web platform changes in Firefox 52 <https://tree.taiga.io/project/viya-mdn-durable-team/epic/1501> by the release of Firefox 52 and in Firefox 53 by the release of beta
Done for Fx 52: JS and DOM, HTTP WebExtensions, Layout, Media
Done for Fx 53: Layout, WebExtensions
In Progress for Fx53: JS, Dom, Media
Firefox 52 items were ready by release and it looks like most items for Firefox 53 should be ready this week.
KR: Activate 2 new localizers in one locale, prioritized by Dev Marketing
We have identified a target locale (pt-BR) and we have promising feedback from the locale
We should be able to define goals for the locale and get buy-in with 2 new localizers in the current sprint
Objective: 80% of MDN visitors to understand that MDN is powered by Mozilla (Baseline: 52%)
KR: Define 2017 brand strategy for MDN as a Mozilla property that balances core brand attributes (browser agnostic vs powered by Mozilla)
Project page: https://docs.google.com/document/d/1y2fRYFpIFIDrMEwKenI5JwSHbYPtjn2EjEmN1nAftBo/edit <https://docs.google.com/document/d/1y2fRYFpIFIDrMEwKenI5JwSHbYPtjn2EjEmN1nAftBo/edit>
Brad and Yuliya presented preliminary results to the team and will present refined results in 2 weeks
We should be able to present our brand strategy to leadership later this month
Objective: Support emerging technologies and upcoming Firefox releases
KR: Publish 10 reference pages and tutorials about CSS grids
Completed
KR: Publish 10 reference pages and tutorials about WebAssembly
Completed
KR: Document new APIs for PWA for marketing push
IntersectionObserver moved to Firefox 54, so not this quarter. There is no more work left for this KR.
KR: Document DevTools features of Firefox 52 and 53 beta
Completed
Objective: Move MDN to a sustainable tech stack to ensure uptime doesn’t go below 99.9%
KR: Reduce monthly hours of site downtime due to planned db maintenance to zero
Work on the maintenance mode has started. Deployment planned for this sprint.
Looks like we are on track with this KR.
Objective: At least 1 editor offers integrated access to MDN compat data by end of 2017
KR: Validate demand for compat data plan with editor developers
Project page: https://docs.google.com/document/d/1qse7VhMVWN2WnIcP56nwhoHpP3V1xnAQTWEIfWUwWVo/edit <https://docs.google.com/document/d/1qse7VhMVWN2WnIcP56nwhoHpP3V1xnAQTWEIfWUwWVo/edit>
completed
KR: Complete prototype for compat data as defined in budget plan <https://docs.google.com/document/d/1aNbbqwdbI_NQcSvtAKDKi6kdBTR2FeEe-B5Iee8RHjs/edit#>
This will depend on the result of the KR above, but one pre-requisit is having machine readable compat data
We’ve split the schema work out into the discussion, test, and the roll out.
We need to make a decision on what makes sense as a prototype here. Ideally it’s something that will allow us to work with editor vendors for inclusion in editors in Q2
Objective: Increase the first quartile of 3-week contributor retention to 3% from 1.48% (2016-H2 baseline).
KR: Redefine and begin re-implementing contributor pathways.
Pathway for localizers has been completed
Pathways for English language contributors, promoters and Kuma editors is in this sprint
KR: Run and analyze 5 contributor engagement experiments <https://wiki.mozilla.org/Engagement/MDN_Durable_Team/Community_hypotheses> to select proven tactics for increasing retention
We have analysis of 2 experiments in the sprint: collective thank you emails to all new contributors, and personalized thank you emails for specific work.
We should be able to finish this in the current sprint
—Kadir
0 new messages