24
edits
DevTools/Planning/Performance: Difference between revisions
Request to delete old information
(Request to delete old information) |
|||
| (12 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{delete|This information is very outdated, please see profiler.firefox.com for the current profiling infrastructure.|date=05/27/2020}} | |||
{{ForceRefreshButton}} | {{ForceRefreshButton}} | ||
Note: the performance product overview can be found here: [[DevTools/Planning/Performance/Details]]. | |||
===What the hell is this?=== | ===What the hell is this?=== | ||
This is a Kanban board. It's simply a way of managing the flow of work through engineering from writing down the requirement to finally landing the feature without some big heavy process or methodology. Please note that this is NOT SCRUM. Here we simply "stack" user stories into work piles that we process. Product management has a work pile of user stories they prepare for engineering to work on, and engineering has a work pile of user stories that are prioritized and ready to be implemented. | This is a Kanban board. It's simply a way of managing the flow of work through engineering from writing down the requirement to finally landing the feature without some big heavy process or methodology. Please note that this is NOT SCRUM. Here we simply "stack" user stories into work piles that we process. Product management has a work pile of user stories they prepare for engineering to work on, and engineering has a work pile of user stories that are prioritized and ready to be implemented. | ||
| Line 10: | Line 11: | ||
As a standard disclaimer: the process of preparing user stories for implementation isn't just a PM task, engineers and engineering managers at Mozilla should always be a part of the process of validating and refining any user story. | As a standard disclaimer: the process of preparing user stories for implementation isn't just a PM task, engineers and engineering managers at Mozilla should always be a part of the process of validating and refining any user story. | ||
Note that | Note that Bugzilla is the source of truth. The only thing this page contains are some convenient Bugzilla queries that you may as well do on Bugzilla if you prefer. | ||
===Backlog=== | |||
The backlog contains all the incoming artifacts that haven't been looked at. In terms of Bugzilla, it means status = "NEW" and the PM-Scrub flag has not been set. | |||
<bugzilla> | <bugzilla> | ||
{ | { | ||
"blocks": "928571", | "blocks": "928571", | ||
"include_fields": "id, | "status": "NEW", | ||
"f1": "flagtypes.name", | |||
"o1": "notsubstring", | |||
"v1": "pm-scrub", | |||
"include_fields": "id, priority, summary, status, assigned_to", | |||
"order": "bug_id" | "order": "bug_id" | ||
} | } | ||
| Line 25: | Line 29: | ||
==="To be Scrubbed" Stack=== | ==="To be Scrubbed" Stack=== | ||
The PM work stack contains all the user stories that need to be scrubbed, validated, worked on by UI and prioritized by PM and engineering. In terms of Bugzilla, it means status = "NEW" and the PM-Scrub flag has been set to ?. Usually, most of these need mockups from UI. | The PM work stack contains all the user stories that need to be scrubbed, validated, worked on by UI and prioritized by PM and engineering. In terms of Bugzilla, it means status = "NEW" and the PM-Scrub flag has been set to ?. Usually, most of these need mockups from UI. | ||
<bugzilla> | <bugzilla> | ||
{ | { | ||
"blocks": "928571", | "blocks": "928571", | ||
"status": "NEW", | "status": "NEW", | ||
"product": "Firefox", | |||
"component": "Developer Tools: User Stories", | |||
"f1": "flagtypes.name", | "f1": "flagtypes.name", | ||
"o1": "substring", | "o1": "substring", | ||