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

From MozillaWiki
Jump to navigation Jump to search
(completed through 2.1)
(Updated with Sept. 5th confidence levels.)
Line 49: Line 49:
*[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.]
|
|
*Great progress has been made on the Quality P1s. Nearly at 50% closure, the goal for this OKR.
*Good progress has been made on the Quality P1s. Nearly at 50% closure, the goal for this OKR.
*In this sprint (as of Sept. 14th):  
*In this sprint (as of Sept. 14th):  
**A couple are in review: [https://github.com/mozilla/fxa-content-server/issues/5197 Issue 5197: Sign-in flow: Never send users to about:preferences after Sign-in] and [https://github.com/mozilla/fxa-content-server/issues/5262 Issue 5262: Expand Connect Another Device to all sync Desktop sign-ins]
**A couple are in review: [https://github.com/mozilla/fxa-content-server/issues/5197 Issue 5197: Sign-in flow: Never send users to about:preferences after Sign-in] and [https://github.com/mozilla/fxa-content-server/issues/5262 Issue 5262: Expand Connect Another Device to all sync Desktop sign-ins]
Line 101: Line 101:
*[https://mozilla.invisionapp.com/share/76CPM7AC2#/screens/240561291_Desktop-_Connect_Another_Device Proposed mock up]
*[https://mozilla.invisionapp.com/share/76CPM7AC2#/screens/240561291_Desktop-_Connect_Another_Device Proposed mock up]
|
|
*Next step is to design test to measure results.
*A little bit of code needs to land. Need to land the copy and set things up in LeanPlum.
 
|-
|-
| align="left"|2.2 Complete 80% of Q3 mobile bugs.
| align="left"|2.2 Complete 80% of Q3 mobile bugs.
Line 119: Line 120:
*[https://github.com/mozilla/fxa-bugzilla-mirror/issues/332 Issue 332: Use Firefox Account server's /.well-known/fxa-client-configuration to configure servers in Firefox for iOS [bz1237407]]  
*[https://github.com/mozilla/fxa-bugzilla-mirror/issues/332 Issue 332: Use Firefox Account server's /.well-known/fxa-client-configuration to configure servers in Firefox for iOS [bz1237407]]  
|
|
*Did the easy ones first. Medium level ones are left to do. Should have 9/13 done by next week.
*Did the easy ones first. Medium level ones are left to do.
*[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-132:%20Q3%20Mobile Mobile Quality Burndown Chart]
*[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-132:%20Q3%20Mobile Mobile Quality Burndown Chart]
|-
|-
Line 135: Line 136:
*Feature doc and Issues coming soon.
*Feature doc and Issues coming soon.
|
|
*Not confident that we’ll have QR codes ready to test
*Saw movement on the bug with Android camera not auto-focusing, but bug has recently been re-prioritized from P1 to P2.
*Too many unknowns to have any confidence
*We can try a file input but that would be a crappy experience. Have never tried to import a photo into the encoder. What if there’s too much noise in the photo or the QR code?
*We can play with the one built into iOS but still might not have time to figure it out by the end of the quarter.
*Confidence level for use of a QR code is <25%; type a code maybe >50%
*Need to regroup now that we know more about technical limitations and figure out what we want to do. Need a smaller discussion about what the next steps are.
*Ryan will reach out to iOS team.
|-
|-
| align="left"|3.2 Ship secondary email.
| align="left"|3.2 Ship secondary email.
Line 175: Line 170:
Relier encryption keys  
Relier encryption keys  
|
|
*Waiting to engage crypto consultants.
*Focusing on completing pieces for crypto review
*We have an end-to-end demo with Notes
*[https://github.com/mozilla/fxa/issues/245 Issue 245: Prototype key support api for Firefox Notes]
*[https://github.com/mozilla/fxa/issues/245 Issue 245: Prototype key support api for Firefox Notes]
|-
|-
Line 189: Line 185:
Implementation of Amplitude
Implementation of Amplitude
|
|
*Getting help from Amplitude to move forward
*Played with the test data, and it looks good.
*Still discovering new things
*Working on minor changes to remove duplicate properties.
*Should have environment with train-95 that we can send events to.
*Made a dot release in 95 and should be able to add more with 96 so that we have data to play with for Amplitude training.
 
|-
|-
|}
|}

Revision as of 14:39, 18 September 2017

Sept 5, 2017

Q3 OKR Progress

Objective Key Result Confidence Features Notes
Jul 10 Jul 24 Aug 8 Aug 21 Sep 5 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% 75% 90%

Priorities for support of Quantum/Photon in 57:

  • As of Sept. 5th, there were only a handful of "crouton" bugs remaining. Confidence % reflects where we were at on Sept. 5th. By week of Sept 11th, they were all finished! Confidence will be updated to 100% at next team review on Sept. 18th.
  • Crouton Flow Burndown Chart
1.2 Close 50% of our Q3 quality backlog. 50% 75% 75% 90%

Quality Priorities for Q3:

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% 40% 0%
  • Still not seeing any difference in outcomes between the different phases in our ABC test. Landed our iOS deeplink patch on Sept 7th so signinCodes consumption should have increased since that date. Form views on iOS should also have increased since that date thanks to deeplinks. Leif will compare form views per phase.
  • The bottom charts of our dashboard are not measuring phase 2 and 3 the same way. They show very different results because phase 3 uses the flow_id. There may be a bug with the flow_id so Leif will copy the phase 2 chart for phase 3. Will see what difference that makes.
1.4 Fix newsletter subscription when email is confirmed on a 2nd device. 95% 95% 95% 95% 90%

Fixes a problem with getting marketing newsletter opt-in data over to Salesforce.

  • Not sure if the fix is working. Maybe the situation it fixed was small numbers and just not noticeable. We should be able to go through the flow ourselves and have Ben verify.
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% 55% 50%
  • A little bit of code needs to land. Need to land the copy and set things up in LeanPlum.
2.2 Complete 80% of Q3 mobile bugs. N/A 60% 60% 60% 65%

Identification and fixing of the most impactful bugs on iOS

Currently working on:

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% 25% 0%

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

  • Feature doc and Issues coming soon.
  • Saw movement on the bug with Android camera not auto-focusing, but bug has recently been re-prioritized from P1 to P2.
3.2 Ship secondary email. 80% 80% 90% 90% 90%
  • Shipped
  • Shaking out the downstream bugs in terms of getting the devices to update themsleves. That’s browser work that we don’t have a lot of control over.
  • Grisha is working on Android piece.
  • Still confident we an get it out the door.
3.3 Land support for relier encryption keys. 70% 70% 75% 75% 75%

Relier encryption keys

3.4 Integrate 100% of high priority Amplitude events. 75% 75% 75% 75% 75%

Implementation of Amplitude

  • Played with the test data, and it looks good.
  • Working on minor changes to remove duplicate properties.
  • Made a dot release in 95 and should be able to add more with 96 so that we have data to play with for Amplitude training.