MozillaWiki

Firefox/Go Faster

< Firefox
Revision as of 20:21, 22 June 2015 by Lshapiro (talk | contribs) (removed weekly meeting section as we dont have one yet)

Go Faster

Go Faster is a plan to change the way we ship Firefox for Desktop, and potentially other products. The end goal is to reduce the time it takes to deliver value to the user. This focuses on getting features and fixes to the user on a reduced cycle time, but includes reductions in time to download updates and new versions, and reductions in build and release time.


Meetings & Communications

TBD

Development

Schedule

Firefox 41 Release

  • Iteration 41.2: Tuesday May 26 - Monday June 8
  • Iteration 41.3: Tuesday June 9 - Monday June 29
    • Note: IT 41.3 is a 3-week iteration.

Firefox 42 Release

  • Iteration 42.1: Tuesday June 30 - Monday July 13
  • Iteration 42.2: Tuesday July 14 - Monday July 27
  • Iteration 42.3: Tuesday July 28 - Monday August 10

Themes

As we plan what's coming next, we're focused on the themes outlined here. This is not a commitment to the next projects - just our scratch area, but it is in order of relative priority.

  • Ship features with service integrations as Add-ons: Decouple feature development of service integration features from 6 week Firefox software release train
  • Ship Localizations Separately From Product: Have the installer or updater pull a langpack from AMO during the install or update process, and decouple langpack builds from our releases.
  • Ship data separately from code: Pull data out and make it a separate download (transparent to the user) via the installer or updater.

Things we want to do - but not starting until higher priorities are done:

  • TBD - add as things come up

Other common Themes that will be mixed in the backlog as they come up:

  • UX: this tag is less a theme - more a marker so UX knows we need something from them on that bug- it often lives with other Themes and the UX comes off when we get the info. Unless it's a unique UX bug - then UX stays.
  • error: bug we've seen come in that we prioritize along side Theme work - often not Theme specific.
  • tech-debt: work to make development smoother (test harness, dev tools, documentation, etc.)
  • metrics: work specific to improving visibility into the product - but not required for a feature
  • investigation or watch: needs investigation or just watching to see if it's reproducible and get an idea of the impact / cause.

At this point we are wrapping up other project work, risk is that it will carry over beyond 40.3. Need to clarify/set expectations for Search Suggestion timelines/features.

Current

Iteration - 41.2, through June 8

User Story this iteration:

Details

Product Backlog

Work related to the ongoing development of Go Faster are collected and prioritized in the Product Backlog. The goals of the Product Backlog are to:

  • Improve work prioritization, so the team is always working on the most important features.
  • Simplify continual planning, so the plan matches reality.
  • Improve visibility so that the stakeholders make the best decisions about the direction of the product (call out risks early, relative priorities, trade-offs)

Triage Guidelines

The Product Backlog is continually maintained by the Go Faster team to ensure new priorities are available for each Sprint Planning meeting.

  • Priorities follow this Standard:
    • Priority 1 - Blocker, must-fix before shipping.
    • Priority 2 - Major impact, considering severity × probability. Not a blocker for shipping.
    • Priority 3 - Average Bug. definitely a problem, but doesn't stop someone from using the product.
    • Priority 4 - Minor or polish bugs that are real issues (especially in aggregate) and annoying.
    • Priority 5 - Low-impact. something we'd fix, but mostly only bothers the discerning user. Little impact on usability.

  • RANK: As priority buckets start to have a large amount of bugs in them, the Rank field can be used to call attention to higher or lower rank and provide a way to sort easily in bugzilla. To have some rhyme/reason to the order - Rank should relate to Priority. The "Ranking" number does not need to be unique. Unless there is a reason to for a bug to be considered before (or after) others in the Priority bucket - default to mid-range value.
    • P1 Rank options=1-19, default 15
    • P2 Rank options=20-29, default 25
    • P3 Rank options=30-39, default 35
    • P4 Rank options=40-49, default 45
    • P5 Rank options=50-59, default 55
    • any that we don't think we can get to in the next 6 months should go in "backlog-" area

  • The Firefox-backlog flag is used to track bugs that are approved for the Backlog "+" (or Backlog - to not be looked at for a while)
  • Add whiteboard tag to bugs [fxsearch] as bugs for this team may span Product:: Component areas.
  • QE-Verify is a flag that developers should be setting on bugs they are working on. This is used for QE to filter which bugs they check
    • "+" means that QE should look at the bug and it can be verified with human eyes
    • "-" means QE should not look at
      • Typically goes with in-testsuite set to "+", to show testing via another method.
  • Points should be set when known.
  • Iteration should be updated when a bug is being worked on during a particular Iteration.

Filing a bug

    • Open a bug under Product:"___" || Component: "___" or "_____"
    • Team reviews for inclusion in Backlog every 2 weeks
  • If there is a bug that should be considered for taking ASAP - you can mark "firefox-backlog"+ and set a Priority with a reason. This makes it simplest to triage those bugs quickly.
    • Before it can be given a Rank it should:
      • be in an actionable state (for the team taking it)
      • for defects, the problem is ready for Engineering or UX: diagnosis, measurement, design, or fixing
      • for feature requests or enhancements, it means that there's a clear problem statement or suggestion

Project Health

Include clear, executive level summary that will be included at the [mana page overall view level:

  • for company goal x, we are in _____ state because ______. Please consider ______(propose fix or adjustment of goal).
  • for release goal for ______ , we are in _____ state because ______. Please consider ______(propose fix or adjustment of goal).

Project Introduction

  • Team Mailing list: if applicable
  • Team IRC Channel: where does this team "hang-out"
  • Summary of our plans for this year
    • links back to main Firefox page - Marco to create a section on main page for team summaries.
    • Quick high-level plans for the year for Desktop management and contributors.
  • Dependencies: feature, partner, resource, etc. that impact this projects ability to succeed - put links to other project pages.

Links to Current info

The Links wiki page is the central location for current focus, Roadmap, Metrics, UX, Marketing, tech-architecture, and more.

Roles and Responsibilities

The Contacts Page has the Roles and Responsibilities for Firefox teams, partner teams, and external partners.

Retrieved from "https://wiki.allizom.org/index.php?title=Firefox/Go_Faster&oldid=1081201"