Firefox/searchandaddon

Firefox Search

problem statement or why we do this project and the scope of work focused on - intro for someone brand new.

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. Likely completed by Kev/Dave with EPM help as needed.
    • Here's an example of the overview from Platform team for webRTC
• 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.

Meetings & Communications

Meeting	Day of week	Pacific Time	Eastern Time	Central European Time	Vidyo Room	Notes
Planning	bi-weekly at the start of the iteration on ___	0:00AM - 0:30AM	0:00AM - 0:30PM	0:00PM - 0:30PM	team vidyo room	etherpad
Stand-up	Team decides	0:00AM - 0:30AM	0:00AM - 0:30PM	0:00PM - 0:30PM	Team vidyo room	etherpad
Triage	Team decides	0:00AM - 0:30AM	0:00AM - 0:30PM	0:00PM - 0:30PM	Team vidyo room	Bugzilla queries, etherpad
Retrospective	Team decides	0:00AM - 0:00AM	0:00AM - 0:00PM	0:00PM - 0:00PM	team vidyo room	etherpad

Development

Schedule

• Firefox main release schedule is the master location for the dates when each Firefox version goes to Aurora, Beta, & Release.

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

The Iteration Backlog is a collection of priority work the team has selected to work on in a two-week iteration.

Current

Iteration - 41.1 April 28 - May 11

• Iteration Backlog: View In Bugzilla

Past

Iteration - 40.3 April 27

• Normally there would be a summary of features worked on / progress / blockers
• Normally list of bugs closed like this one

Themes

As we plan what's coming next, these are areas being discussed. This is not a commitment to the next projects - just our scratch area, but it is in order of relative priority - including the work we've pulled for the sprints.

• Unified Autocomplete: Necessary maintenance work to make the awesomebar easier to improve
• Search Hijacking: Keep users on the search engine that they want
  • Add-on Signing
• Search Suggestions: Adding search suggestions to the awesomebar
• Search UI: basically how our search access points work/look
• Partner Engine: issues relating to the integration of our partner's search engines

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.

Risks

• Risk ex: Dependency on a service that is not established/planned for from another team. Need help prioritizing if we should delay the feature in this project or raise the priority in the other team based on their existing backlog

Product Backlog

All work related to the ongoing development and maintenance of the Firefox Desktop Product 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)

Key Bugzilla Queries

• Team Product Backlog: Bugs marked Firefox-backlog+ and [fxsearch]
  • Add the "Rank" Column to your results and sort on Rank (option to "Change columns" is at bottom of search results)
• Bugs Pulled Current Iteration:Bugs in the Backlog with a current iteration tag
  • for Assignee: dtownsend@mozilla.com, dao@mozilla.com, mak77@bonardo.net, mjaritz@mozilla.com, shorlander@mozilla.com
• Untriaged Bugs marked Firefox-backlog+: Bugs marked Firefox-backlog+ without [fxsearch] in the Whiteboard under Search
• Untriaged Bugs:Bugs NOT marked Firefox-backlog+ without [fxsearch] in whiteboard under Search

Triage Guidelines

The Product Backlog is continually maintained by the Hello Management 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

• (get central location for graphics from Erin)

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).