670
edits
(Deleted old bullet) |
(Corrected August 21st update) |
||
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
<big><big>'''August | <big><big>'''August 21, 2017'''</big></big> | ||
== Q3 OKR Progress == | == Q3 OKR Progress == | ||
| Line 17: | Line 17: | ||
|style="text-align: center; background-color: #f9d9a8"|Aug 8 | |style="text-align: center; background-color: #f9d9a8"|Aug 8 | ||
|style="text-align: center; background-color: #f9d9a8"|Aug 21 | |style="text-align: center; background-color: #f9d9a8"|Aug 21 | ||
|style="text-align: center; background-color: #f9d9a8"|Sep | |style="text-align: center; background-color: #f9d9a8"|Sep 5 | ||
|style="text-align: center; background-color: #f9d9a8"|Sep 18 | |style="text-align: center; background-color: #f9d9a8"|Sep 18 | ||
|style="text-align: center; background-color: #f9d9a8"|Score | |style="text-align: center; background-color: #f9d9a8"|Score | ||
| Line 37: | Line 37: | ||
*[https://github.com/mozilla/fxa-auth-db-mysql/issues/229 Issue 229: Update device name column to utf8mb4] | *[https://github.com/mozilla/fxa-auth-db-mysql/issues/229 Issue 229: Update device name column to utf8mb4] | ||
| | | | ||
* | *25% remaining to fix. Fixed some bugs this cycle. | ||
*Animation on svg’s needs to be started | *Animation on svg’s needs to be started. Once we’re done with the non-BMP char device names (unicode), that will free up some time (#5 on the list). | ||
*Rest seem pretty manageable but just need to get them to the top of the list. | *Rest seem pretty manageable but just need to get them to the top of the list. | ||
*[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-130:%20Crouton%20Flow Crouton Flow Burndown Chart] | *[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-130:%20Crouton%20Flow Crouton Flow Burndown Chart] | ||
|- | |- | ||
| Line 60: | Line 58: | ||
*[https://github.com/mozilla/fxa-content-server/issues/5009 Issue 5009: Only show "email verified" on /connect_another_device if the user actually verfied their email.] confirmation] | *[https://github.com/mozilla/fxa-content-server/issues/5009 Issue 5009: Only show "email verified" on /connect_another_device if the user actually verfied their email.] confirmation] | ||
| | | | ||
* | *Following desired burn-down pace. | ||
* | *Anything that needs browser work? Yes #5197 requires a browser patch. Never send users to about: preferences after Sign-in | ||
*[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-131:%20Q3%20Quality Quality P1s Burndown] | *Prioritize 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. #5196 #5009 #5197 | ||
*[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-131:%20Q3%20Quality Quality P1s Burndown] | |||
|- | |- | ||
|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="left"| 1.3 Increase by 15% the rate of users that become multi-device as a result of going through our first run flow. | ||
| Line 79: | Line 79: | ||
*[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/5194 Issue 5194: Sign-up/in flow: Ask for email first] | ||
| | | | ||
* | *Now that we’re using strict multi-device, numbers are going down, leading us to have less confidence. | ||
*Uptick in engage but no change in ? | |||
* | *Graph not moving in the right direction | ||
*Try to show CAD screen more often | |||
* | |||
* | |||
|- | |- | ||
|align="left"| 1.4 Fix newsletter subscription when email is confirmed on a 2nd device. | |align="left"| 1.4 Fix newsletter subscription when email is confirmed on a 2nd device. | ||
| Line 98: | Line 95: | ||
Fixes a problem with getting marketing newsletter opt-in data over to Salesforce. | Fixes a problem with getting marketing newsletter opt-in data over to Salesforce. | ||
| | | | ||
*Didn’t seem to be any big change in | *Didn’t seem to be any big change in their metrics. Marketing is expected to look at them again. | ||
*Number didn’t drop to 0 | *Number didn’t drop to 0 so we didn’t break it. | ||
*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. | |||
|- | |- | ||
|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 134: | Line 132: | ||
*[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. | ||
*[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] | ||
|- | |- | ||
edits