Sprint 007 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 006 review
- check out the sprint management dashboard and go over issues that were closed
Sprint 006 retrospective
- Screenshot burndown
- go over the burndowns
- check out the sprint management dashboard and go over issues that were not closed
Sprint 007 planning:
- Consult product owner notes below
- go over the sprint planning dashboard and move tasks into the sprint 007 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

We need to formulate a plan to address any potential retractions found during the MDC, e.g., G910434 and get these into an MR by the end of the sprint.
- Of note are also: G913075 and G919346
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 (this might be ongoing).
- More generally we need to get our ``operational review" on track.
Lets do a few more checks that gracedb uploads agree with our internal trigger / FAR records.
I am concerned about the GWAVE cluster transition to Vast and Rocky 8. Specifically, I am concerned about Sathya’s group. We need to do outreach to get people on board and help them through the transition.
I would like to pin down an actual configuration for the ICDS cluster that works well (we had a lot of discussion last week, but didn’t settle on a plan)

Issues of Note: