Firefox/Accounts/Progress Report/2017Q3: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(added new dates)
(added OKRs for first objective)
Line 21: Line 21:
|style="text-align: center; background-color: #f9d9a8"|Score
|style="text-align: center; background-color: #f9d9a8"|Score
|-
|-
|rowspan=2| 1. To enable webextension developers to provide value with Firefox Accounts on desktop.
|rowspan=4| 1. To have improved the quality for the Firefox Account experience on desktop.
| align="left"|1.1 To have created 1 mvp of a webextension API for FxA on desktop.  
| align="left"|1.1 Close ALL (100%) issues in the Quantum/Photon milestone. (Crouton)
|align="center"|50%
|align="center"|60%
|align="center"|50%
|align="center"|
|align="center"|60%  
|align="center"|
|align="center"|70%
|align="center"|
|align="center"|75%
|align="center"|
|align="center"|80%
|align="center"|
|align="center"|1
|align="left"|
|[https://waffle.io/mozilla/fxa?milestone=FxA-130:%20Crouton%20Flow Issues for 57 release.]
|
|-
|align="left"| 1.2 Close X% of our Q3 quality backlog.
|align="center"|X%
|align="center"|
|align="center"|
|align="center"|
|align="center"|
|align="center"|
|align="left"|
|align="left"|
Web Extension API for FxA on Desktop
*[https://github.com/mozilla/fxa-features/issues/121 Issue 121: OAuth Support for Web Extensions]
|
|
*Will ship what we can for Hoverpad. Implementing Auth Server PKCE, the "Proof Key for Code Exchange" spec **[https://openid.net/2015/05/26/enhancing-oauth-security-for-mobile-applications-with-pkse/ Enhancing OAuth Security for Mobile Applications with PKCE]
*This KR is to focus on the P1s that we’ve identified.
**[https://www.authlete.com/documents/article/pkce/index Proof Key for Code Exchange (RFC 7636)]
*[https://docs.google.com/document/d/1_EAW0YY6Ly3-tVY1raDr_rHDoJxhdRY4ntQPyfeZNU0/edit?pli=1 The entire list of quality issues in the backlog] is being converted to [https://docs.google.com/spreadsheets/d/1ahQVcRuadXcCNwSy5RxUFnaTjOLZLUnuGISeDvCmpcyw/edit#gid=0 a list of Quality Related P1s]
**[https://github.com/mozilla/fxa-oauth-server/pull/466/files#r121266395 Issue 466 - feat(pkce): add PKCE support to the oauth server]
*[https://waffle.io/mozilla/fxa?milestone=FxA-131:%20Q3%20Quality Issues in Github]
**[https://github.com/mozilla/fxa-oauth-server/issues/465 Issue 465 - Implement PKCE to support public clients using the code grant flow]
|
**[https://github.com/mozilla/fxa-content-server/pull/5126 Issue 5126 - feat(oauth): support PKCE oauth parameters]
*
|-
|-
|align="left"| 1.2 To have at least 1 internal project consuming our API on desktop.
|align="left"| 1.3 Increase by 15% the rate of users that become multi-device as a result of going through our first run flow.
|align="center"|50%
|align="center"|50%
|align="center"|50%
|align="center"|
|align="center"|60%
|align="center"|
|align="center"|65%
|align="center"|
|align="center"|70%
|align="center"|
|align="center"|80%
|align="center"|
|align="center"|1
|align="center"|
|
|
*
|-
|align="left"| 1.4 Fix newsletter subscription when email is confirmed on a 2nd device.
|align="center"|95%
|align="center"|
|align="center"|
|align="center"|
|align="center"|
|align="center"|
|align="center"|
|
|
Hoverpad or ScreenShot integration
|
|
*Actively collaborating.
*
*Plan to meet with Screenshots team at SF Work Week.
|-
|-
|rowspan=2| 2. To have improved the quality of the Firefox Account experience on mobile.
|rowspan=2| 2. To have improved the quality of the Firefox Account experience on mobile.
Line 65: Line 83:
|align="center"|
|align="center"|
|align="center"|
|align="center"|
|rowspan=2; align="left"|
|align="left"|
*[https://docs.google.com/spreadsheets/d/1tPE4KSNd_RU-ahSAK7a5hMcP5EAKGMlHJHegna87xLg/edit#gid=0 FxA Sync prioritization backlog for iOS]
*[https://docs.google.com/spreadsheets/d/1tPE4KSNd_RU-ahSAK7a5hMcP5EAKGMlHJHegna87xLg/edit#gid=0 FxA Sync prioritization backlog for iOS]
|
|
*Still need to figure out what caused the numbers to go down on May 24th.
*  
*Good metrics were the result of users being incorrectly identified as being in the experiment.
*[https://groups.google.com/a/mozilla.com/forum/?hl=en#!topic/fxa-core/Dg3HPIDItrY Current working theory documented in an email thread after confidence level was estimated]:
|-
|-
| align="left"|2.2 Complete X% of Q3 mobile bugs.
| align="left"|2.2 Complete X% of Q3 mobile bugs.
Line 81: Line 97:
|align="center"|
|align="center"|
|align="left"|  
|align="left"|  
*Need to finalize the list.
*
|-
|-
|rowspan=4| 3. To have completed all features that are still in flight from Q1 and Q2.
|rowspan=4| 3. To have completed all features that are still in flight from Q1 and Q2.

Revision as of 23:23, 14 July 2017

July 10, 2017

OKR Progress

Objective Key Result Confidence Features Notes
Jul 10 Jul 24 Aug 7 Aug 21 Sep 4 Sep 18 Score
1. To have improved the quality for the Firefox Account experience on desktop. 1.1 Close ALL (100%) issues in the Quantum/Photon milestone. (Crouton) 60% Issues for 57 release.
1.2 Close X% of our Q3 quality backlog. X%
1.3 Increase by 15% the rate of users that become multi-device as a result of going through our first run flow. 50%
1.4 Fix newsletter subscription when email is confirmed on a 2nd device. 95%
2. To have improved the quality of the Firefox Account experience on mobile.


2.1 Measure and A/B test best push opt-in screen on iOS. 50%
2.2 Complete X% of Q3 mobile bugs. X%
3. To have completed all features that are still in flight from Q1 and Q2. 3.1 Have a device pairing flow ready to A/B test. 75%
  • Device pairing is ready. Shane to open issues for the deliverables of this key result.
3.2 Ship secondary email. 80%
  • Have only a little work to finish up from Q2.
3.3 Land support for relier encryption keys. 70%
  • Awaiting 2 reviews for encryption protocol.
3.4 Integrate 100% of high priority Amplitude events. 75%
  • Have gotten the ball rolling with coordination.
Retrieved from "https://wiki.allizom.org/index.php?title=Firefox/Accounts/Progress_Report/2017Q3&oldid=1175793"