User Services/Sync/Relaunch

From MozillaWiki
Jump to navigation Jump to search

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 deadline. This constantly updated, cross-team, master dependency burn list/wiki is our collaboration tool, consolidating the dependencies and our focus to resolve them to a single page.

20 Days to Go

Proposed Burndown List Thing

Features

  • First field/sort is weekly iteration. Time is immutable, invaluable and scarce.
  • Second field/sort is story. All work should (must?) have a clearly articulated customer (who), feature (what) and benefit (why), also known as value proposition. Anyone can add stories following the "As a 'customer, I want feature so I can benefit terse humane format then drop their tasks under the story. Stories deemed not sufficient priority are subject to punt.
  • Next three fields identify responsibility/accountability.
  • Final field scopes task providing brief description with detail links to BZ, Wiki, Zombo.com, etc.
Iteration Ending Story Team Sub DRI Task
Friday, December 20th - 1 work day
  As a customer, I want feature that requires a lot of text to explain so I can benefit that also takes a lot of text to explain.
  Cloud UX JGruen This task requires an extraordinary deluge of purple text and yet still more and more text to describe. And when a task is done, we strikethrough the text.
  Android Eng MFinkle This task requires an extraordinary deluge of purple text and yet still more and more text to describe. And when a task is done, we strikethrough the text.
  As a customer, I want feature that requires a lot of text to explain so I can benefit that also takes a lot of text to explain.
  Cloud UX JGruen This task requires an extraordinary deluge of purple text and yet still more and more text to describe. And when a task is done, we strikethrough the text.
  Android Eng MFinkle This task requires an extraordinary deluge of purple text and yet still more and more text to describe. And when a task is done, we strikethrough the text.
Friday, January 3rd - 2 work days
Friday, January 10th - 5 work days
Friday, January 17th - 5 work days
Friday, January 24th - 5 work days
Wednesday, January 29 - 3 work days

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
    • [ENG] Demonstration build on elm
  • Fri, Jan 3
  • 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
  • Sync Storage server API needs to be final
  • Migration issues need to be sorted when nightly goes live

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
  • [AT RISK] Fri, Jan 3 - Define migration plan for Nightly/Aurora/Beta/Stable
  • [AT RISK] Fri, Jan 10 - Dev to hand off build using frozen auth and sync storage api
  • 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.
    • [ENG] Demonstration build on elm
  • 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.
    • [ENG] Demonstration build on elm
  • 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

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.

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. To quote Johnathan, "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.

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.allizom.org/index.php?title=User_Services/Sync/Relaunch&oldid=807981"