Sprint 003 agenda - February 8, 2023

• Strategy check in (to be completed by product owner prior to meeting)
  • Look in on recent issue activity
  • look over the epic list and the road map to make sure we are still happy with the big picture
  • Add last minute issues to epics
• Sprint 002 review
  • check out the sprint management dashboard and go over issues that were closed
• Sprint 002 retrospective
  • Screenshot burndown
  • go over the burndowns
  • check out the sprint management dashboard and go over issues that were not closed
• Sprint 003 planning:
  • Consult product owner notes below
  • go over the sprint planning dashboard and move tasks into the sprint 003 board.
    • At Risk Issues
    • Needs attention Issues
    • On track
    • unprioritized The Scrum Master should work with the team to assign a health for these in the coming sprint
  • go around the room and assign tasks
    • Does everyone have a task?
    • Does everyone’s hours add up to what is reasonable?
  • choose a scrum master

Personnel

• Product Owner: Chad Hanna
• Scrum master: TBD
• Stakeholders?: TBD

Minutes

Attendance

Chad, Becca, Divya, Rachael, Prathamesh, Shio, Cort, Victoria, Yun-Jing, Shomik, Jim, Leo

Strategy check in and product owner notes (done pre meeting by Chad)

I continue to be concerned that we need to be on track for a perfect MDC 11 to serve as the operational review driven by the performance paper. We have 10 days to wrap everything up. I would like everyone this week and next to work on making that happen. This is the final push for dev. After that, it has to be bug fixes only, and quality of life improvements, e.g., monitoring. One exception would be things related to DQ which won’t be available until later. Based on this, here is my asssessment of what is important. It is my opinion that people should put less critical things on pause for the next 10 days until a perfect MDC 11 is underway.

NOTE: If we are going to make MDC 11 our performance review Jacob must also be stable and in production configuration

Tier 1 things:

• Plan operation review This is quite related to outlining the performance paper.
• Triage retractions There must be no retractions in MDC 11.
• FIX MEMORY LEAK
• Add job uptime metrics I think we will want to report the uptime in the performance paper.

Tier 2 things:

• Generally try to make current deployments more reproducible and even easier to deploy - this could potentially be addressed through making a container for each analysis but I am open to suggestions. I think there are generally conversations we should have around containers, so lets have them. Related to [this issue](Move online analyses to production containers in cvmfs)
• We should probably be ready to try a rerank of MDC 11 data. This is a needed feature for O4 and would let us test further non-invasive LR changes e.g., snr threshold in p of instruments and snr threshold used for dt dphi covariance matrix after the fact.