DevTools/Planning/Status: Difference between revisions
| (7 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
For individual team status pages, please refer to the following pages: | For individual team status pages, please refer to the following pages: | ||
Paris (Paul Rouget's team): | * Paris (Paul Rouget's team): [[DevTools/Planning/Status/Paris]] | ||
London: (Joe Walker's team): | * London: (Joe Walker's team): [[DevTools/Planning/Status/London]] | ||
Toronto: (Rob Campbell's team): | * Toronto: (Rob Campbell's team): [[DevTools/Planning/Status/Toronto]] | ||
Los Angeles: (Dave Townsend's team): | * Los Angeles: (Dave Townsend's team): [[DevTools/Planning/Status/LosAngeles]] | ||
===Bucket Statuses=== | ===Bucket Statuses=== | ||
Whiteboard tags represent the following: | Whiteboard tags represent the following: | ||
* [status:backlog] = this is in the backlog as an idea | * [status:backlog] = this is in the backlog as an idea being considered to add to the pipeline of work. | ||
* [status:planned] = planning to work on this within the next | * [status:planned] = planning to work on this within the next 90 days, requirements and design still being refined. | ||
* [status:inflight] = this feature is in flight and being worked on. | * [status:inflight] = this feature is in flight and being worked on. | ||
* [status:landedoff] = this feature has landed in nightly with pref off. | * [status:landedoff] = this feature has landed in nightly with pref off. | ||
| Line 21: | Line 21: | ||
* [status:shipped] = this feature is completed and shipping. | * [status:shipped] = this feature is completed and shipping. | ||
* [status:onhold] = work has been put on hold because of other higher priorities. | * [status:onhold] = work has been put on hold because of other higher priorities. | ||
===Backlog=== | ===Backlog=== | ||
| Line 28: | Line 27: | ||
{ | { | ||
"product": "Firefox", | "product": "Firefox", | ||
"whiteboard": "[status:backlog]", | "whiteboard": "[status:backlog]", | ||
"include_fields": "id, | "include_fields": "id, component, summary, status, assigned_to", | ||
"order": "bug_id" | "order": "bug_id" | ||
} | } | ||
| Line 40: | Line 38: | ||
{ | { | ||
"product": "Firefox", | "product": "Firefox", | ||
"whiteboard": "[status:planned]", | "whiteboard": "[status:planned]", | ||
"include_fields": "id, | "include_fields": "id, component, summary, status, assigned_to", | ||
"order": "bug_id" | "order": "bug_id" | ||
} | } | ||
| Line 52: | Line 49: | ||
{ | { | ||
"product": "Firefox", | "product": "Firefox", | ||
"whiteboard": "[status:inflight]", | "whiteboard": "[status:inflight]", | ||
"include_fields": "id, | "include_fields": "id, component, summary, status, assigned_to", | ||
"order": "bug_id" | "order": "bug_id" | ||
} | } | ||
| Line 63: | Line 59: | ||
{ | { | ||
"product": "Firefox", | "product": "Firefox", | ||
"whiteboard": "[status:landedoff]", | "whiteboard": "[status:landedoff]", | ||
"include_fields": "id, | "include_fields": "id, component, summary, status, assigned_to", | ||
"order": "bug_id" | "order": "bug_id" | ||
} | } | ||
| Line 74: | Line 69: | ||
{ | { | ||
"product": "Firefox", | "product": "Firefox", | ||
"whiteboard": "[status:landedon]", | "whiteboard": "[status:landedon]", | ||
"include_fields": "id, | "include_fields": "id, component, summary, status, assigned_to", | ||
"order": "bug_id" | "order": "bug_id" | ||
} | } | ||
Latest revision as of 16:12, 13 August 2014
Global Team Status Overview
All work in DevTools should be tied to feature tracking bugs and assigned the right whiteboard flags to reflect the status of each feature bucket. Development managers are responsible to create the dependencies (blocks) 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 and mutable over time.
For individual team status pages, please refer to the following pages:
- Paris (Paul Rouget's team): DevTools/Planning/Status/Paris
- London: (Joe Walker's team): DevTools/Planning/Status/London
- Toronto: (Rob Campbell's team): DevTools/Planning/Status/Toronto
- Los Angeles: (Dave Townsend's team): DevTools/Planning/Status/LosAngeles
Bucket Statuses
Whiteboard tags represent the following:
- [status:backlog] = this is in the backlog as an idea being considered to add to the pipeline of work.
- [status:planned] = planning to work on this within the next 90 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%);