Confirmed users
14,525
edits
QA/Platform/Graphics/Features/Planning: Difference between revisions
QA/Platform/Graphics/Features/Planning (view source)
Revision as of 18:26, 22 July 2016
, 22 July 2016→Discussion Notes
(Created page with "== Summary == As part of Mozilla's Quantum initiative, the Graphics team is interested in developing a feature qualification process based on the model used by the Electrolysi...") |
|||
| Line 24: | Line 24: | ||
* Raise red flags early, often, and clearly | * Raise red flags early, often, and clearly | ||
* System addons can be used to both experiment on Beta and release to a specific sub-population | * System addons can be used to both experiment on Beta and release to a specific sub-population | ||
* Clearly define owners/approvers for each feature and quality area, e10s team used the [https://en.wikipedia.org/wiki/Responsibility_assignment_matrix RASCI Responsibility Matrix] | |||
* Clearly define and track metrics for users utilizing your feature and users still on the old path | |||
* Clearly define when a feature is good enough to ship to millions of users and how each bug gets you closer to that goal, not doing this can lead to developer stress/burnout | |||