|10 minutes||Status update|
Juniper Hot Fix #2
Kiwi release preparation
Lotus release GA date
|20 minutes||Circulation Performance Proposal|
|10 minutes (carried over from last meeting)||Plans for Zak|
Zak's last day as a community developer is September 24. Zak mentioned that he will spend part of his time doing community work. What will this entail?
Update: Zak will stay on team until December 31, 2021. Also, Holly will be part-time starting February 1, 2022.
|10 minutes (carried over from last meeting)||Prokopovych Team Capacity|
As of December 31, when Zak is no longer on the Prokopovych team, we will have the following capacity:
Given the volume of issues assigned to the team, and expectations by the project, we need more devs.
In order to manage expectations, please note that...
Prokopovych priorities between now and September 17 code freeze (see our Scrum Board)...
Update: Looking into adding 2 devs to our team. If that doesn't happen, we could reassign modules to another team.
|10 minutes (carried over from last meeting)||Institution Ranking|
We currently have 29 institutions with a Rank field in JIRA. Anya has requested that we add 33 more. The process we are using has become unwieldy. Our plan was to use the "points" to plan most work, but then use the "rankings" to determine what to do next when nothing is highly ranked for the team/epic. Perhaps the POs should work with the appropriate SIG to determine what to work on when nothing is highly pointed? Then we can eliminate the ranking process. Thoughts?
Update: We will use the pointing exercise to prioritize. If a PO doesn't have highly pointed features, that PO should go to the PO group to see if they can take on highly pointed features for another PO. If that doesn't resolve the issue, the PO should talk to the Capacity Planning Team.