| 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%
|
75%
|
|
|
|
Priorities for support of Quantum/Photon in 57:
Carried over from the last sprint:
|
|
| 1.2 Close 50% of our Q3 quality backlog.
|
|
50%
|
75%
|
75%
|
|
|
|
Quality Priorities for Q3:
Active in this sprint:
|
- Continue to burn down issues along the projected ideal line.
- Prioritizing sign in/sign up flow for train-95. Know what we shouldn’t do but not necessarily what we should be doing. Trying to narrow down a solution that will work for everyone.
- 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%
|
40%
|
|
|
|
|
- FxA team's A/B/C testing continues. Now that we’re measuring "strict multi-device", numbers are going down. Confidence level for this key result has dropped because of questions around why this is happening. Maybe try to show CAD screen more often?
A/B/C testing is set up as follows:
- Mobile Push (Phase 1) for ⅓ of the users
- Mobile Push (Phase 2) for ⅓ of the users
- Mobile Push (Phase 3) for ⅓ of the users
- Marketing is evaluating the effectiveness of copy variations for the sign in/sign up flows. Their hypothesis: If we provide users with clear and concise copy about the features and benefits they’ll find in using a Fx account they’ll be more likely sign up, increasing conversions in the page and contribute to improved overall DAU/MAU. (Secondarily, users with Fx Accounts that are not logged in will find the new copy compelling enough to login.)
- Much of the Email First work will ship week of Aug 28 as part of Train-94. Before this feature is offered to users, rigorous internal testing must be conducted because of the scope of the change, and the marketing copy experiment will need to have completed.
|
| 1.4 Fix newsletter subscription when email is confirmed on a 2nd device.
|
95%
|
95%
|
95%
|
95%
|
|
|
|
Fixes a problem with getting marketing newsletter opt-in data over to Salesforce.
|
- Didn’t seem to be any big change in marketing's metrics after fixing the problem. Marketing is expected to look at the metrics again.
- Number didn’t drop to 0, so we didn’t break it. It was trending down even before our work landed. So 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%
|
|
|
|
|
- No change. Waiting for a bunch of stuff to land. But happy with code and getting it through the review process with the iOS team.
|
| 2.2 Complete 80% of Q3 mobile bugs.
|
N/A
|
60%
|
60%
|
60%
|
|
|
|
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%
|
|
|
|
|
Allow users to test out device pairing. This does not necessarily mean that QR codes are used.
- Feature doc and Issues coming soon.
|
- Tried QR scanner on phone and it failed. Scanning doesn’t work on pixel phone in fx because it doesn’t auto-focus.
- Will try Chrome Android phone to see if it works there. Looking at the specs. Looks like there’s an auto vs. manual focus option.
- Might need to make use of built-in scanner as part of Firefox mobile or something else. Need to figure out another way around this.
|
| 3.2 Ship secondary email.
|
80%
|
80%
|
90%
|
|
|
|
|
- We are allowing users to add a secondary email. Allows users to change primary email.
- Issues for changing primary email:
|
- Change email passed the SV testing.
- Should be enabled for all users in train-93.
- Client side patches (ios profile). Still working on iOS part
|
| 3.3 Land support for relier encryption keys.
|
70%
|
70%
|
75%
|
|
|
|
|
Relier encryption keys
|
|
| 3.4 Integrate 100% of high priority Amplitude events.
|
75%
|
75%
|
75%
|
|
|
|
|
Implementation of Amplitude
|
- Amplitude is comfortable with our taxonomy
- In a position to start integration
- Break down of the work needs to be placed in Github
|