Sprint 006 agenda - March 1, 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 005 review
- check out the sprint management dashboard and go over issues that were closed
Sprint 005 retrospective
- Screenshot burndown
- go over the burndowns
- check out the sprint management dashboard and go over issues that were not closed
Sprint 006 planning:
- Consult product owner notes below
- go over the sprint planning dashboard and move tasks into the sprint 006 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
  - Assign ROTA members
  - 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, Surabhi

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

Last week’s MDC was a bit rougher than hoped although not as grim as feared (at least for Edward / Jacob). Here is a summary from my (Chad’s) perspective

There was one event in the MDC, G910434 that is retraction worthy (an L1 single). The good news is that it is really only barely above the previous OPA threshold at 1.6 per year and - assuming it is the only retraction worthy event this MDC, its overall FAP will be O(10%) by the time the MDC is done. Certainly not a disaster, but we need to investigate it thoroughly
The ranking stat PDF looks noisy and we need to see if something has gone wrong with sampling
I gather we are still having stability issues. That needs to end this week. Period.
We should continue to make sure we have monitored what we need to monitor.
I would like the more senior members specifically (Becca, Leo, Rachael, Divya, Prathamesh, Shio) have plenty of time to work on papers this week and for the junior members (Jim, Cort, Yun-Jing, Shomik, Victoria) to take over their roles on various projects to keep things moving and to transfer knowledge
I am still eager to improve dev/ops specifically around configuration and deployment, but we probably don’t have time this week to actually do any work. HOWEVER, we should have a meeting to iron things out.
We need a response to the LL MDC presentation today.

Issues of Note: