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

From MozillaWiki
Jump to navigation Jump to search
(Update 1.1 with most recent issues)
(Updated 1.2)
Line 52: Line 52:
*[https://waffle.io/mozilla/fxa?milestone=FxA-131:%20Q3%20 Quality related P1s that we’ve identified to fix in Q3.]
*[https://waffle.io/mozilla/fxa?milestone=FxA-131:%20Q3%20 Quality related P1s that we’ve identified to fix in Q3.]
Active in this sprint:
Active in this sprint:
*[https://github.com/mozilla/fxa-content-server/issues/5193 Issue 5193: Sign-up flow: Add a “confirm password” field to minimize errors entering password, minimizing password reset.]
*[https://github.com/mozilla/fxa-content-server/issues/5203 Issue 5203: Device Manager: Make device icons accurate]
*[https://github.com/mozilla/fxa-content-server/issues/4863 Issue 4863: Add descriptions to Choose What to Sync]
*[https://github.com/mozilla/fxa-content-server/issues/4863 Issue 4863: Add descriptions to Choose What to Sync]
*[https://github.com/mozilla/fxa-content-server/issues/5194 Issue 5194: Sign-up/in flow: Ask for email first]
*[https://github.com/mozilla/fxa-content-server/issues/4857 Issue 4857: Firefox Android is having trouble with signin confirmation]
*[https://github.com/mozilla/fxa-content-server/issues/5198 Issue 5198: Settings: Communication preferences can end up in an odd state]
|
|
*Initial confidence assessment wasn't based on much data
*Continue to burn down issues along the projected ideal line.
*[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-131:%20Q3%20Quality Quality P1s Burndown] shows we’re on the ideal line  
*[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-131:%20Q3%20Quality Quality P1s Burndown] shows we’re on the ideal line  
|-
|-

Revision as of 00:31, 10 August 2017

August 8, 2017

Q3 OKR Progress

Objective Key Result Confidence Features Notes
Jul 10 Jul 24 Aug 8 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% 65% 70%

Active in this sprint:

1.2 Close 50% of our Q3 quality backlog. 50% 75%

Active in this sprint:

  • Continue to burn down issues along the projected ideal line.
  • Quality P1s Burndown shows we’re on the ideal line
1.3 Increase by 15% the rate of users that become multi-device as a result of going through our first run flow. 50% 50% 50%

The onboarding team, marketing retention team and Mozilla.org team would like our help to improve user retention (through converting first run users to multi-device users).

  • We've seen an increase in views but no noticeable increase in what happens after.
  • Need to start shipping some of the quality improvements before we change the confidence level.
1.4 Fix newsletter subscription when email is confirmed on a 2nd device. 95% 95% 95%

Fix the problem of how we currently lose newsletter subscribers if users confirm their emails on a different device.

  • Merged and should ship - we have everything but the measuring.
  • Will help marketing’s metrics.
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% 40% 55%
  • Rfeely shared mock ups on how it should look. Ryan prefers it to be native. Not sure of impact of this.
  • We don’t think iOS app. itself has something built in to perform the A-B test. Might be best to make it web based and use our own tools.
  • Feature doc is in draft.
2.2 Complete 80% of Q3 mobile bugs. N/A 60% 60%

Identification and fixing of the most impactful bugs on iOS

  • Came up with a list of 13 bugs that were reviewed with Stefan
  • 10 of the 13 we have high confidence in completing
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% 75% 50%

Allow users to test out device pairing. This does not necessarily mean that QR codes are used.

  • Feature doc and Issues coming soon.
  • Phil and Shane to get together to chat about a feature doc for this
  • Waiting for August 8th, when Android will support deeplinking in 55.
  • Test plan updated.
  • Plan is to enable it in train-93 because 55 will be out at that point.
  • We need to think about anything we need to get into 56 beta.
3.2 Ship secondary email. 80% 80% 90%

We are allowing users to add a secondary email. Allows users to change primary email.

  • Only thing remaining is how clients would handle the change on their GUI/interfaces
  • Can disable or enable on the content server.
3.3 Land support for relier encryption keys. 70% 70% 75%

Relier encryption keys

  • Did some work on this but not enough to change confidence further.
  • Biggest risk is not getting the crypto review done soon enough (reliance on other teams).
3.4 Integrate 100% of high priority Amplitude events. 75% 75% 75%

Implementation of Amplitude

  • Went through Amplitude onboarding.
  • Have gotten the ball rolling with coordination.