Confirmed users
3,816
edits
QA/Team Meeting/QA-Team-09-03-2014: Difference between revisions
Jump to navigation
Jump to search
QA/Team Meeting/QA-Team-09-03-2014 (view source)
Revision as of 22:53, 5 September 2014
, 5 September 2014→Action Items and notes from the meeting
| Line 57: | Line 57: | ||
* We will take notes on [https://etherpad.mozilla.org/qa-team-meeting-notes this etherpad] | * We will take notes on [https://etherpad.mozilla.org/qa-team-meeting-notes this etherpad] | ||
What do goals look post reorg? To get to goals we need a common language to approach quality at Mozilla. @ https://etherpad.mozilla.org/QA-Quality-Foundations | What do goals look post reorg? To get to goals we need a common language to approach quality at Mozilla. @ https://etherpad.mozilla.org/QA-Quality-Foundations | ||
Delight - meets or exceeds the expectations of the user. Goal for this discussion is to name the buckets. | Delight - meets or exceeds the expectations of the user. Goal for this discussion is to name the buckets. | ||
| Line 62: | Line 63: | ||
-- (example: KaiRo's measure of whether we are "stable enough" | -- (example: KaiRo's measure of whether we are "stable enough" | ||
-- How/where do we record what the standards are that we're aiming for ? | -- How/where do we record what the standards are that we're aiming for ? | ||
Thresholds pass/fail criteria - need regular updating. | Thresholds pass/fail criteria - need regular updating. | ||
Quality is: you know it when you see it. Defining quality as a set metric is impossible. You can set ranges metrics should fall into. | Quality is: you know it when you see it. Defining quality as a set metric is impossible. You can set ranges metrics should fall into. | ||
We could track values for areas of bugzilla and create a total score for the area. This would give us insight into the health of the area. | We could track values for areas of bugzilla and create a total score for the area. This would give us insight into the health of the area. | ||
Do the 5 areas outline the framework that we can use discuss the goals? Are there any missing areas? Does the "Web Platform" section apply to quality metrics. Discussion about do we hold a release for not pushing the web platform forward? | Do the 5 areas outline the framework that we can use discuss the goals? Are there any missing areas? Does the "Web Platform" section apply to quality metrics. Discussion about do we hold a release for not pushing the web platform forward? | ||
Hard blockers. Having a team definition of quality (outside the quality team). Our team should be an example for external teams. We can represent and highlight our tools and processes as part of our civic presence in open source software and for other QA teams in other projects. | Hard blockers. Having a team definition of quality (outside the quality team). Our team should be an example for external teams. We can represent and highlight our tools and processes as part of our civic presence in open source software and for other QA teams in other projects. | ||
Convincing product/project/dev the value of the small bug, death of 1000 paper cuts. Mentor bugs is a way to move a chunk of these forward. UX can be an ally. Make a case to project that a sprint should be dedicated to cleaning up polish bugs. Can be useful for devs to knock off a larger number of bugs. | Convincing product/project/dev the value of the small bug, death of 1000 paper cuts. Mentor bugs is a way to move a chunk of these forward. UX can be an ally. Make a case to project that a sprint should be dedicated to cleaning up polish bugs. Can be useful for devs to knock off a larger number of bugs. | ||
Jobs with a rather different common vocab is going to be difficult. Especially with outside teams. | Jobs with a rather different common vocab is going to be difficult. Especially with outside teams. | ||
What language do we need to use to communicate the state of quality to external teams? Does talking about quality need a model? Should we start from scratch. Definitely need vocab and need to be persuasive. | What language do we need to use to communicate the state of quality to external teams? Does talking about quality need a model? Should we start from scratch. Definitely need vocab and need to be persuasive. | ||
Deliverables? | Deliverables? | ||
| Line 88: | Line 97: | ||
Articulating Quality Not Just Data/Metrics | Articulating Quality Not Just Data/Metrics | ||
* Not: "what are the right metrics" | * Not: "what are the right metrics" | ||
* we're making all these observations now | * we're making all these observations now (and can always improve upon...) | ||
Purpose of Common Language/Vocabulary | Purpose of Common Language/Vocabulary | ||
* Ability to articulate my user experience in a language anyone can understand | * Ability to articulate my user experience in a language anyone can understand | ||
* We're not the only ones observing quality & our jobs are all so different | * We're not the only ones observing quality & our jobs are all so different | ||
* Talking about quality using common themes or reference frame could enable us to make | * Talking about quality using common themes or reference frame could enable us to make a better case for things like polish (vs. just function). | ||
== Travel / PTO == | == Travel / PTO == | ||