1. LSST Data Management System Science Team Meeting Mario Juric, University of Washington LSST Data Management Subsystem Scientist
Joint Technical Meeting 2017
March 6-8th, 2017

2. Please Interrupt for Questions and Clarifications!

3. DM System Science Team
Members of the SST work together to define, maintain, and communicate to the DM engineering team a coherent vision of the LSST DM system responsive to the overall LSST Project goals.
The SST also devises and undertakes initiatives to scientifically validate the DMS implementation.

4. What Does the (DM) Subsystem Scientist Do?
Communicate with the stakeholders (science community, advisory bodies) to understand stakeholder goals
Attend workshops and conferences on behalf of LSST, collect information and feedback
Be involved in science collaboration work
Define, maintain and communicate system vision and requirements; communicate these to the construction team
Maintain high-level vision and requirements documents
Investigate and assess scientific acceptability of proposed technical solutions to the project stakeholders (understand the performance of the system); potentially propose alternatives
Negotiate mutually acceptable solutions between the stakeholders and the development team
Collection and communication of required scientific inputs
Advise on the priority of DM construction activities
Provide advice on overall prioritization (backlog prioritization)
Validate the deliverables
Define the scientific content and coordinate execution of tests and data challenges
Convene design reviews (internal and external)
Codified in LDM-284 and soon in a top-level project document to be rolled out at the JTM.

5. DM System Science Team LSST Subsystem Scientist DM System Science Team
DM Project Manager
DM Subsystem Scientist (Mario Juric)
DM Science Pipelines Scientist (Robert Lupton)
DM Science Validation Scientist (Position Open)
Team Scientists
DM System Science Team
System Science Team Staff
DM SST Analyst (Melissa Graham)
Alert Production Scientist (Eric Bellm)
Data Release Production Scientist (Jim Bosch)
DM SST Analyst (Colin Slater)
SQuaRE Scientist (Michael Wood-Vasey; interim)
SUIT Scientist (David Ciardi)
Data Processing Scientist (Robert Gruendl)

6. DM System Science Team Responsibilities
Support the DM Subsystem Scientist in ensuring the DM System meets the LSST science objectives.
Communicate with the science community and internal internal stakeholders to understand their needs, identifying the aspects to be satisfied by the DM Subsystem.
Liaison with the science collaborations to understand and coordinate any concurrent science investigations relevant to the DM Subsystem.
Develop, maintain, and articulate the vision of DM products and services that is responsive to stakeholder needs, balanced across science areas, well motivated, and scientifically and technologically current.
Work with the DM Project Manager and DM Technical Managers to communicate and articulate the DM System vision and requirements to the DM construction team.
Identify, develop, and champion new scientific opportunities for the LSST DM System, as well as identify risks where possible.
Develop change proposals and/or evaluate the scientific impact of proposed changes to DM deliverables driven by schedule, budget, or other constraints.
Lead the Science Verification of the deliverables of the LSST DM System.

7. Responsibility flow/breakdown
DM SS responsibilities are delegated to the members of the DM System Science Team
Team Scientists: Product Owner roles for parts of the work breakdown structure (more in a second)
Pipeline Scientist: Algorithm choices and their impact on science
Also: SST Staff, Team Scientists
SST Staff: Understand the expected performance of the deliverable, investigate scientific acceptability of proposed solutions, devise and propose new solutions
DM SS: Communication with the community
Everyone on the SST
Science Validation Scientist: Validation of deliverables
Science Validation group

8. “Product Owners”: Plugging into Scrum
- The Scrum product owner is typically a project's key stakeholder. Part of the product owner responsibilities is to have a vision of what he or she wishes to build, and convey that vision to the scrum team.
- The product owner is commonly a lead user of the system or someone from marketing, product management or anyone with a solid understanding of users, the market place, the competition and of future trends for the domain or type of system being developed.
- This, of course, varies tremendously based on whether the team is developing commercial software, software for internal use, hardware or some other type of product. The key is that the person in the product owner role needs to have a vision for what is to be built.
DM SST Scientists are the Product Owners of their parts of the system
Responsibility delegated by the DM Subsystem Scientist
Participate in sprint planning (sprint goal, backlog prioritization, etc.)
Participate in sprint reviews (accept the results)

9. Communication tools Confluence home: Github home: Mailing list
(will soon be moved to a permanent location)
Github home:
Mailing list
Slack Channel
#dm-sst
Note: it's use is discouraged for anything other than messages not meant to be permanent (i.e., passing a link to someone, or communicating in real-time during meetings).
Meetings
Proposal: meet every two weeks

10. Tentative Agenda for Today
First 1.5hr block:
Starting the System Science Team (this talk)
Science platform definition
Outline a Minimum Viable System proposal
Organization of DM Science Validation
Report on & plan for future PDAC SV activities
Second 1.5hr block:
LDM-151 status and closure
Resource needs
Heterogeneous focal plane study update
Establishing meeting cadence
R2A2 for the SST
Upcoming meetings: UK, Lyon
We’ll continue much of this discussion online.

11. Summary
The mission of DM is to build operable services needed to produce LSST data products and enable LSST science.
Data Products
The LSST Science Platform Services
The mission of DM’s System Science Team is to ensure we understand what DM needs to build, and assure what DM has built is usable for science. We support and provide direction needed for the engineering effort to build the LSST. We are the Product Owners of externally visible deliverables.
Question for discussion: How do we best organize ourselves to fulfill our mission?