View source for DevTools/Planning/Performance

{{ForceRefreshButton}}

===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.

To track the pile of user stories related to performance management, we created the tracking bug 928571, also known by the alias "perf-kanban". To put a user story on the board, just create a "bug" that contains a user story or requirement, and make it block "perf-kanban". At that point, it's in what we call "the backlog". To get it going into the flow, just set the pm-scrub flag to "?" and now it goes into the pile of work for product management to look at. When PM has done the required work of scrubbing the user story (making sure there are no duplicates, that it has mockups, and that it fits into the "product story line" and that it's appropriately prioritized) then the PM flag is set to + and any engineer can assign themselves to it and implement it. After that, it's business as usual.

Bottom line: ideally, you want to work on new features that block "perf-kanban" and have the pm-scrub flag set to "+".

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 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.

===All=== 
For now, this is an unfiltered query of all NEW bugs on the Kanban board. Ideally this should be the backlog, i.e. incoming user stories not yet assigned to PM to work on. In terms of Bugzilla, it means status = "NEW" and the PM-Scrub flag has not been set. However, the query is broken, BugZilla doesn't respond to a "not_contains" type query on the flag.

<bugzilla>
{
        "blocks": "928571",
"include_fields": "id, whiteboard, summary, status, assigned_to",
         "order": "bug_id"
}
</bugzilla>

==="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.
<bugzilla>
{
        "blocks": "928571",
        "status": "NEW",
    "whiteboard": "[User Story]",
      "f1": "flagtypes.name",
      "o1": "substring",
      "v1": "pm-scrub?",
"include_fields": "id, priority, summary, status, assigned_to",
         "order": "bug_id"
}
</bugzilla>

==="Ready to implement" Stack=== 
The ready to work stack contains all the user stories ready to be implemented. That means the stories have been flushed out, cleaned up and prioritized. In terms of Bugzilla, it means status = "NEW" and the PM-Scrubb has been set to +.
<bugzilla>
{
        "blocks": "928571",
        "status": "NEW",
    "whiteboard": "[User Story]",
      "f1": "flagtypes.name",
      "o1": "substring",
      "v1": "pm-scrub+",
"include_fields": "id, priority, summary, status, assigned_to",
         "order": "bug_id"
}
</bugzilla>

==="In Progress" Stack=== 
User stories currently being implemented. Bugzilla: status=ASSIGNED. 

<bugzilla>
{
    "blocks": "928571",
    "status": "ASSIGNED",
    "include_fields": "id, priority, summary, status, assigned_to",
    "order": "bug_id"
}
</bugzilla>

==="Landed" Stack=== 
User stories that have landed.
<bugzilla>
{
    "blocks": "928571",
    "resolution": "FIXED",
    "include_fields": "id, priority, summary, status, assigned_to",
    "order": "bug_id"
}
</bugzilla>