Confirmed users
1,094
edits
Loop: Difference between revisions
Jump to navigation
Jump to search
m
added Triage stuff - killing iteration page
(→Documentation: Add a new library upgrades page) |
Sescalante (talk | contribs) m (added Triage stuff - killing iteration page) |
||
| Line 98: | Line 98: | ||
==[https://wiki.mozilla.org/Loop/wiki Links to current info]== | ==[https://wiki.mozilla.org/Loop/wiki Links to current info]== | ||
[https://wiki.mozilla.org/Loop/wiki Loop/wiki] page is the central location for current focus, Roadmap, Metrics, UX, Marketing, and more. | [https://wiki.mozilla.org/Loop/wiki Loop/wiki] page is the central location for current focus, Roadmap, Metrics, UX, Marketing, and more. | ||
=Triage= | |||
<p> </p> | |||
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).<p> </p> | |||
==Key Bugzilla Queries== | |||
* [http://mzl.la/1Q1c3W4 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 | |||
* [http://mzl.la/1JBkwev Un-triaged bugs] | |||
* [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&list_id=12373638&columnlist=cf_fx_iteration%2Ccf_fx_points%2Cassigned_to%2Cbug_status%2Cstatus_whiteboard%2Cshort_desc%2Cchangeddate%2Cpriority%2Cbug_severity%2Cresolution%2Ccomponent%2Creporter&o1=anywordssubstr&resolution=---&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=tech-debt&component=Client&component=General&product=Hello%20%28Loop%29 Tech-debt bugs] | |||
==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 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 - use default | |||
** P1 Rank options=1-10, '''default 5''' | |||
** P2 Rank options=11-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 | |||
<p> </p> | |||
*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:"(Hello)Loop" || Component: "General" or "Client" | |||
**We triage weekly - it helps if there is a priority as a starting point and a reason | |||
<p> </p> | |||
===Definition of Done=== | |||
<p> </p> | |||
* The [https://etherpad.mozilla.org/HsVyzOogAr Definition of Done] ensures a potentially shippable product increment is released at the conclusion of a release cycle. | |||
<p> </p> | |||
* A potentially shippable product increment means compliance with the work's individual acceptance criteria and not the full story under development. | |||
<p> </p> | |||