DevTools/Planning/Status: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 28: Line 28:
</bugzilla>
</bugzilla>


==="To be Scrubbed" Stack===  
===Planned===  
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.
Here are the items that are being planned:
<bugzilla>
{
      "product": "Firefox",
    "component": "Developer Tools: User Stories",
    "whiteboard": "[status:planned]",
"include_fields": "id, priority, summary, status, assigned_to",
        "order": "bug_id"
}
</bugzilla>


===In Flight===
This stuff is being worked on
<bugzilla>
<bugzilla>
{
{
        "blocks": "936563",
      "product": "Firefox",
        "status": "NEW",
    "component": "Developer Tools: User Stories",
        "product": "Firefox",
    "whiteboard": "[status:inflight]",
      "component": "Developer Tools: User Stories",
      "f1": "flagtypes.name",
      "o1": "substring",
      "v1": "pm-scrub?",
"include_fields": "id, priority, summary, status, assigned_to",
"include_fields": "id, priority, summary, status, assigned_to",
         "order": "bug_id"
         "order": "bug_id"
Line 45: Line 52:
</bugzilla>
</bugzilla>


==="Ready to implement" Stack===  
===Landed with Pref=off===  
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>
<bugzilla>
{
{
        "blocks": "936563",
      "product": "Firefox",
        "status": "NEW",
    "component": "Developer Tools: User Stories",
     "whiteboard": "[User Story]",
     "whiteboard": "[status:landedoff]",
      "f1": "flagtypes.name",
      "o1": "substring",
      "v1": "pm-scrub+",
"include_fields": "id, priority, summary, status, assigned_to",
"include_fields": "id, priority, summary, status, assigned_to",
         "order": "bug_id"
         "order": "bug_id"
Line 60: Line 63:
</bugzilla>
</bugzilla>


==="In Progress" Stack===  
===Landed with Pref=on===  
User stories currently being implemented. Bugzilla: status=ASSIGNED.
 
<bugzilla>
<bugzilla>
{
{
    "blocks": "936563",
      "product": "Firefox",
     "status": "ASSIGNED",
    "component": "Developer Tools: User Stories",
    "include_fields": "id, priority, summary, status, assigned_to",
     "whiteboard": "[status:landedon]",
    "order": "bug_id"
"include_fields": "id, priority, summary, status, assigned_to",
        "order": "bug_id"
}
}
</bugzilla>
</bugzilla>


==="Landed" Stack===  
===Shipped===  
User stories that have landed.
<bugzilla>
<bugzilla>
{
{
    "blocks": "936563",
      "product": "Firefox",
     "resolution": "FIXED",
    "component": "Developer Tools: User Stories",
    "include_fields": "id, priority, summary, status, assigned_to",
     "whiteboard": "[status:shipped]",
    "order": "bug_id"
"include_fields": "id, priority, summary, status, assigned_to",
        "order": "bug_id"
}
}
</bugzilla>
</bugzilla>

Revision as of 23:51, 18 July 2014

Project Status Overview

We are using the developer tools :: User Stories component to track buckets of features that are being worked on. All work should be tied to bugs in this component and assigned the right whiteboard flags to reflect the status of that particular bucket. Development managers are responsible to create the dependencies (block) for all bugs that tie to a particular feature bucket. We are not following any "user story" methodology for requirements, but we do want to track what the requirements are in the user story field. Even a vague summary is fine. This field is editable over time.

Bucket Statuses

Whiteboard tags represent the following:

  • [status:backlog] = this is in the backlog as an idea and isn't being worked on.
  • [status:planned] = planning to work on this within the next 30 days, requirements and design still being refined
  • [status:inflight] = this feature is in flight and being worked on.
  • [status:landedoff] = this feature has landed in nightly with pref off.
  • [status:landedon] = this feature has landed in nightly with pref on.
  • [status:shipped] = this feature is completed and shipping.
  • [status:onhold] = work has been put on hold because of other higher priorities.


Backlog

The backlog contains all the incoming artifacts that haven't been looked at.

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Planned

Here are the items that are being planned:

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


In Flight

This stuff is being worked on

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Landed with Pref=off

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Landed with Pref=on

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Shipped

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);