Firefox/Iterative Hello Development: Difference between revisions

Revision as of 17:10, 8 January 2016

{{{{#invoke:Namespace detect|main}} | type = | image = | imageright = | class = | style = | textstyle = | text = THIS PAGE HAS BEEN DE-COMMISSIONED. ALL RELEVANT INFO ON TRIAGE IS UNDER https://wiki.mozilla.org/Loop | small = | smallimage = | smallimageright = | smalltext = | subst = {{subst:substcheck}} | date = | name = Notice }}

Product Backlog

Key Bugzilla Queries

Bugzilla Ranked list
- Add the "Rank" Column to your results and sort on Rank
  - The option to "Change columns" is at bottom of search results
- Search is based on bugs which have the Ranked field
Un-triaged bugs
Tech-debt bugs priority based on etherpad discussion - though if you want one that's lower priority but impacting you - grab it

The goals of the Prioritized Product Backlog and dynamic Planning are to:

Simplify prioritization & planning so the team is always working on the most important features.
Improve visibility to everyone to clear priorities - so we 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 Hello Management team to ensure new priorities are available for each Sprint Planning meeting.

Priorities: if you are filing a bug - based on your knowledge of the bug feel free to set a priority for consideration based on the following criteria:
- Priority 1 - Blocker, must-fix before shipping in the next release.
- 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: Not needed when filing a bug, set during weekly Triage meetings. 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 be set to 100

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 (if nothing set - assumed a "1" or very small). Most relevant if taking a bigger bug so we know when bugs are large bits of work.
"Iteration" should be updated when a bug is being worked on during a particular Sprint.

Filing a bug

- Open a bug under Product:"Loop" || Component: "General" or "Client"
- Hello team reviews for inclusion into a release backlog every 2 weeks, and will mark "firefox-blocking" accordingly
We triage weekly - it helps if there is a priority as a starting point and a reason why the priority was set.
- Before it can be given a Rank it should:
  - be in an actionable state
  - 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
  - has a difficulty/user-impact ratio low enough that we can reasonably expect to spend time fixing the bug within the next 6 months

Definition of Done

The Definition of Done ensures a potentially shippable product increment is released at the conclusion of a release cycle.

A potentially shippable product increment means compliance with the work's individual acceptance criteria and not the full story under development.

Contribute to Hello Development

Good First Bugs

These are tagged as [good first bug] in a bug's Whiteboard field. The challenge of a "good first bug" is only peripherally about the bug itself. The focus, for a new contributor, should be on getting your development environment set up and learning how to navigate Mozilla's contribution process. We are working on better documentation to help you get started with Hello (expect an update Q1 2015), and the #introduction IRC channel exists just to help people getting started as contributors.

Hello Backlog Good First Bugs - View in Bugzilla

Objectives

The Iterative Development Model implemented for Firefox Desktop aims to accomplish six key objectives:

Transparent - Who is working on what, when, and why.
Predictable and Repeatable - Know what to expect from the process.
Inclusive - Include all key participants (Eng, UX, QA, Security, Product) and stakeholders in the process.
Clear Direction and Decision Making - Know what we should do and who makes the call.
Clear and Stable Priorities - Be clear on what is most important for each iterative cycle.
Innovative - Provide flexibility to engage in experimental and original projects.

Development Iterations (Sprints)

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

Firefox 40 Release

Iteration 40.1: Tuesday March 31 - Monday April 13
Iteration 40.2: Tuesday April 14 - Monday April 27
Iteration 40.3: Tuesday April 28 - Monday May 11

Firefox 41 Release

Iteration 41.1: Tuesday May 12 - Monday May 25
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, these are areas being discussed. This is not a commitment to the next projects - just our scratch area.

finishing Context work (large change: server API changes, FxA and encryption design, client end UX and storage components, server storage/retrieval components, UX change across areas)
market work

Things we want to do - but parking lot until the highest priorities are done:

in-conversation chat bug 1108893
Shareplane adjustments bug 1155603
Moving faster: mark-up extraction
Prevent Link-clickers from clicking on themselves bug 1154251
Metrics bug 1148381
e10s readiness for e10s patches (e10s in Beta in 41, releases in 42 - so MUST be in for 42)
Starting Visual Refresh bug 8587058
Android experience improvements
Link-Clicker gets desktop UI bug 1066019
Continue quality focus
WebRTC permission prompt optimization

Risks

List out risks that we are working on or on our radar