We currently have the following teams defined in DM JIRA:
- Alert Production
- Data Access & Database
- Data Release Production
- DMLT / Management
- International Comms. and Base Site
- Process Middleware
- Project Science
- Science User Interface
- Site Infrastructure
These teams are a pretty mixed bunch – some of them correspond to third level WBS elements (AP, DRP, DAX, etc), some are lower levels of WBS (Process Middleware, Site Infrastructure), some are cross-cutting (DMLT, T/CAMs), and some are outside our scope altogether (External).
I suggest that the fundamental purpose of setting the team on the ticket is to identify the individual manager responsible for ensuring that the work be completed. As such, the team should generally be coupled to the third level of WBS (ie, 1.02C.NN). A couple of exceptions to this seem appropriate:
- It is useful to track some work for which no LSST manager is directly responsible (ie, contributors from outside DM). For that purpose, we should maintain the "External" team.
- The DM Architecture and Science teams are defined at the fourth level of WBS (1.02C.02.01 & 02). These are conceptually quite different groups, so it makes sense to track them separately.
I therefore propose that we adopt the following teams:
|Team Name||WBS||Responsible Manager|
|System Management||1.02C.01||Wil O'Mullane|
|DM Science||1.02C.02.01||Mario Juric|
|Alert Production||1.02C.03||John Swinbank|
|Data Release Production||1.02C.04||John Swinbank|
|Science User Interface & Tools||1.02C.05||Xiuqin Wu [X]|
|Data Archive and Application Services||1.02C.06||Fritz Mueller|
|Data Facility||1.02C.07||Margaret Gelman|
|International Communications and Base Site||1.02C.08||Jeff Kantor|
Mapping tickets assigned to the existing teams to the new teams is straightforward in most cases: many teams carry over directly, while "Process Middleware" and "Site Infrastructure" are both combined under the banner of "Data Facility". The DMLT, T/CAMs and Project Science teams are less straightforward: there are a couple of hundred tickets here which will need to be assigned to the correct team on a case-by-case basis.
There will continue to be groupings within DM which do not align with the WBS but which have an interest in particular tickets. These groups can track tickets of concern to them by using labels. I suggest that the following labels would be a good place to start:
- DM-SST (DM System Science Team)
- DMLT (DM Leadership Team)
- DM-SET (DM Systems Engineering Team)
More labels can be added as required.