Sprint 005 agenda - February 22, 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 004 review
- check out the sprint management dashboard and go over issues that were closed
Sprint 004 retrospective
- Screenshot burndown
- go over the burndowns
- check out the sprint management dashboard and go over issues that were not closed
Sprint 005 planning:
- Consult product owner notes below
- go over the sprint planning dashboard and move tasks into the sprint 005 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: Becca Ewing
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 think we did well in getting last minute developments done in time for MDC11. Although there were several bumps along the way in launching the MDC, we eventually got everything smoothed out and are in a somewhat stable state. This week we should prioritize the MDC monitoring and minimize any changes to the ecosystem (eg last week moving to gstlal headnode caused us trouble). We will start to get gravitational waves in the MDC this week so event follow up (and retraction follow up) needs to be a high priority. Other than this I think we should focus on writing our papers, hardening our dev/ops strategy, and improving our dashboards and visibility. Below I listed some issues that I think we should prioritize towards the above goals.