Scheduling issue for the 12.4 release
Current OKRs
- FY20-Q3 Distribution OKR: Increase monthly throughput
- FY20-Q3 Distribution OKR: Increase throughput visibility through accurate labelling
- FY20-Q3 Distribution OKR: Improve product deliverable alignment
Team Availability
- 800% - 8 backend engineers total
- -200% for other currently booked time off
Total 600% of backend engineer availability
Priority and Severity boards
Priority Boards categorize the importance of all open issues, regardless of milestone. They are useful when looking for issue to consider for scheduling.
Scheduling boards
Scheduling boards are a work board used specifically during the scheduling process to give an overview of the candidates, and used to get an idea of the next release before assigning the milestone to the issues.
Status
-
Collect initial candidate issues -
Issues added to the scheduling boards -
Scheduling boards sorted/arranged by importance -
Scheduling boards contain candidates from both Engineering and Product -
Scheduling boards scoped to a reasonable amount of work for the release -
Managers schedule the agreed issues for the release
12.4 candidates
Work in progress that should be continued in 12.4 (team members should feel free to add to this list
- Automate license spreadsheet for GCP Marketplace (This work started in 12.3 but there is more work to be done. It contributes to reducing the manual effort required to maintain our marketplace offerings.)
- Container hardening
- Operators? - operator tickets are currently scheduled in 12.3 and will roll over if necessary.
- Configurator tool
- Adding Grafana to Gitlab chart - follow up issue to add default dashboards for the Helm charts to Grafana. Need to create a ticket for this if one doesn't exist already
Time-sensitive work
- Helm 2 > Helm 3
Customer impact work
- Improvements in backup and restore
Edited by Steven Wilson