User Services/Sync/Relaunch: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 7: Line 7:
Johnathan Nightingale said of the Sync-Tactics mailing list, "This list is for coordination, fast communication about changing circumstances, and next-step hand offs." Likewise, this one-pager is for continuously surfacing, tracking and addressing the critical path to relaunch on deadline.
Johnathan Nightingale said of the Sync-Tactics mailing list, "This list is for coordination, fast communication about changing circumstances, and next-step hand offs." Likewise, this one-pager is for continuously surfacing, tracking and addressing the critical path to relaunch on deadline.


<p style="text-align: center; font-size: 300%; font-weight:bold; border: solid 2px black;">20 Work Days to Go</p>
<p style="text-align: center; font-size: 300%; font-weight:bold; border: solid 2px black;">19 Work Days to Go</p>


=== Burndown Worksheet ===
=== Burndown Worksheet ===

Revision as of 23:08, 3 January 2014

Firefox 29 Cycle Sync Relaunch Burndown

At the Mozilla 2014 Planning offsite on Dec 11th, Johnathan Nightingale, Andreas Gal, and Mark Mayo agreed to jointly accelerate Sync relaunch on Firefox Desktop and Android as their teams’ top priority, targeting the Firefox 29 release and thus a January 29th code freeze.

We must efficiently collaborate across teams to meet our impending deadline. This constantly updated, cross-team, master dependency burn list is our collaboration tool, consolidating the dependencies and our focus to resolve them to a single page.

Johnathan Nightingale said of the Sync-Tactics mailing list, "This list is for coordination, fast communication about changing circumstances, and next-step hand offs." Likewise, this one-pager is for continuously surfacing, tracking and addressing the critical path to relaunch on deadline.

19 Work Days to Go

Burndown Worksheet

Iteration Story Team Sub DRI Task Status
Friday, December 20th - 20 Work Days Remaining
  As a Product Manager, I want a clear mandate and deadline for FxAcct + Sync launch so that everyone involved can effectively plan their work focus and time.
  All PM Chad
Karen
Rob 		Johnathan Nightingale, Mark Mayo and Andreas Gal elevated FxAcct + Sync to first priority for their respective teams and the 29 iteration as the deadline. ✔
Friday, January 3rd - 18 Work Days Remaining
  As a Product Manager, I want a clear migration so that everyone involved can effectively plan their work focus and time.
  All PM Chad
Karen
Rob 		Chad indicated that he's ready to flag day desktop. Karen researching Android users response to a flag day. On Track
Friday, January 10th - 13 Work Days Remaining
Friday, January 17th - 8 Work Days Remaining
Friday, January 24th - 3 Work Days Remaining
Wednesday, January 29th - Code Freeze

Product User Stories

UX

  • In progress: UX is dependent on the final stories

User flow diagrams, low-fidelity wireframes, and links to higher-fidelity artifacts that illustrate the incorporation of Sync.next / Firefox Accounts.

Treat these documents as the visual equivalent of a wiki, and if you drop in a comment, please leave your name.

Cloud Services Dependencies

Contacts: Lloyd Hilaiel, Chris Karlof, Tauni Oxborrow, Ryan Feeley, John Gruen, Rob Lord

  • Complete by Fri, Dec 20
    • [ON TRACK] [PM] Populate UX, Eng, QA deliverables for the remaining four Fridays.
    • [ON TRACK] [OPS] (edwong) Deploy staging Sync server cluster for load testing
    • [ON TRACK] [ENG] Demonstration build on elm
  • Fri, Jan 3
    • [ON TRACK] Finalize definition and build "onepw" login API in the FxA Auth Server
  • Fri, Jan 10
  • Fri, Jan 17
  • Fri, Jan, 24

Backend Engineering Dependencies

Contacts: Ryan Kelly, Toby Elliott

Dependencies

  • API needs to be locked down
    • once locked down, coding can be turned around in a week

Blockers:

  • Need a staging sever for sync that matches current infrastructure

Cloud Services QA Dependencies

Contact: Edwin Wong (:edwong)

Blockers

  • Auth Server API need to be final Issue #344
  • Migration issues need to be sorted when nightly goes live
  • Sync Storage server API needs to be final. Sync v1.5 is minimal change, risk is low.

Schedule

  • [ON TRACK] Complete by Fri, Dec 20 - Define load requirements and SLA for Auth and Sync testing
    • Smoke Desktop Elm, Fennec, Stage Auth server
  • [ON TRACK] Fri, Jan 3 - Smoke Nightly.
  • [AT RISK] Fri, Jan 10 - Dev to hand off build using frozen auth and sync storage api. Define migration plan for Nightly/Aurora/Beta/Stable
  • Fri, Jan 17 - First Test Pass, Load Test complete
  • Fri, Jan, 24 - Final Test Pass, Load Test complete
  • Wed, Jan, 29 - Buffer and GMC/GA testing

Ship Criteria

  • No 5 star or P1 bugs
  • Load 600 requests/sec

Firefox Desktop Dependencies

Contacts: Chad Weiner (PM), Gavin Sharp (Eng), Tim Taubert (Eng), Mark Hammond (Eng)

  • Complete by Fri, Dec 20
    • [PM] Populate UX, Eng, QA deliverables for the remaining four Fridays.
    • [ON TRACK] [ENG] Demonstration build on elm
    • [ON TRACK] Merging elm to mozilla-central
  • Fri, Jan 3
  • Fri, Jan 10
  • Fri, Jan 17
  • Fri, Jan, 24

Firefox for Android Dependencies

Contacts: Karen Rudnitski, Mark Finkle, ...

  • Complete by Fri, Dec 20
    • [PM] Populate UX, Eng, QA deliverables for the remaining four Fridays.
    • [ON TRACK] [ENG] Demonstration build on elm
    • [ON TRACK] Merging elm to mozilla-central
  • Fri, Jan 3
  • Fri, Jan 10
  • Fri, Jan 17
  • Fri, Jan, 24

Platform Dependencies

  • Fri, Dec 20
    • [PM] Populate UX, Eng, QA deliverables for the remaining four Fridays.
  • Fri, Jan 3
  • Fri, Jan 10
  • Fri, Jan 17
  • Fri, Jan, 24

Migration discussion

Sync.next migration discussion go here

Communications

Mailing List

  • Sync-Tactics Mailing List 'Ground Rules' by Johnathan Nightingale
    • This list is for coordination, fast communication about changing circumstances, and next-step hand offs.
    • This list is NOT for UI or protocol design discussion - other channels exist if needed, and [January] 29 is going to be very focused on shipping today, not designing tomorrow.
    • If someone should be on this list who isn't, they can service-now themselves onto it. You are likewise invited to [service-now] yourself off of it, if it's not for you.

Service Now will process your add/drop requests to the sync-tactics mailing list.

IRC Channel

MozNet #sync-tactics

Meeting Notes Etherpad

https://etherpad.mozilla.org/sync-tactics

Q & A

On Migration

Q. What about existing Sync users migration to Firefox Accounts + Sync?
A. Good question. Minimizing disruption of existing Sync users is highly desirable, however Firefox Account + Sync technical, branding and marketing requirements and execution time remaining leave only messaging to minimize disruption for existing Sync users.
Note from rnewman: define "migration". We have no technical way to migrate user data, so we don't plan to do that. We do plan to "grease the skids", both technically and in the UX, to make the user transition to a Firefox Account less unpleasant. My goal is to have a user log in once only, and jump straight from working Sync to working Sync on all their devices. See https://services.etherpad.mozilla.org/sync-migration , and the Sync Migration tab in the UX flows.

On Marketing

Q. Does this relaunch include marketing sign-up/migration to Firefox Account + Sync in this release concomitant with the Australis introduction?
A. Per Johnathan and Chad's current best thinking, yes. Per Johnathan Nightingale, "It would be almost criminal to not introduce [Firefox Accounts + Sync] to the 100s of millions of users being introduced to Australis." Also, some technical thoughts on migration here: https://services.etherpad.mozilla.org/sync-migration

On Deadline

Q. Is the January 29th code freeze date a hard deadline?
A. Yes. We have an aggressive Firefox Account sign-up goal for 2014. If we miss the date, we lose substantial 2014 time to sign-up users. Also, we have a significant OEM to service. Finally, we’ve already waited a long time to ship user accounts. That said, as Mark Finkle notes, "My clarification is that we don't ship Fx29 on January 29th. We do need to have the code in a state that it can be merged to Aurora. That means a certain level of stability and string-freeze. We have every expectation that code will continue to be changed and uplifted as Fx29 rides the trains to a release on April 29th."

On Edge Cases

Q. Does this include Firefox desktop for Metro?
A. No.

Team

  • The cross-functional team and a list of what they own can be viewed here.

Key Deliverables

DRI TEAM TASK DUE NOTES STATUS
Karen, Chad Product Validate & confirm user stories are still relevant. Update if needed. Dec 19 Confirm success criteria is defined for each user story [ON TRACK]
John, Ryan UX Bare bones approach for both Desktop & Android Dec 20 Will need validation of these designs very rapidly by Product [ON TRACK]
Auth Server API need to be final Issue #344 ASAP
Sync Storage server API needs to be final ASAP
Karen, Chad Product Migration Strategy ASAP [AT RISK]
Prod, UX, Prod Mktg Sync Branding ASAP [AT RISK]
Tauni, Mika, Alina Program, Legal, Privacy ToS & Privacy Notices Jan 15 [ON TRACK]
Retrieved from "https://wiki.mozilla.org/index.php?title=User_Services/Sync/Relaunch&oldid=859520"