14.1 Optimize Planning
%14.1 Planning for groupoptimize
Capacity notes
- Larissa out w/c 7 June
- Nick out 14-25 June
- Ezekiel: Public holiday June 14, F&F day June 25
Objectives
- Refactor VSA to support the use case of identifying and resolving workflow bottlenecks
- Current Items FE work for VSA? - Depending on gitlab-org/gitlab#331309 (comment 591545904)
- Add security scan features to the DevOps Adoption table so Ultimate customers can more easily track adoption and report on compliance with security scanning requirements
Plan
- BE work to add dependency scanning, fuzz testing, and vulnerability management to DevOps Adoption
- FE work to add SAST/DAST to adoption table
- FE work to create an adoption overview section
- 2 tech debt issues for DevOps Adoption - gitlab-org/gitlab#326196 (closed) and gitlab-org/gitlab#326195 (closed)
Defining Success
To-Do
-
Define an approximate scope for the coming release. - Apply appropriate labels to issues:
-
Priority -
Department -
Pricing Tier
-
-
Review the proposed scope with Engineering. -
Review design objectives with UX. -
Get feedback and estimates from Engineering, confirming scope for the release. -
Final verification of issues scheduled for the release. -
Present selected issues in the Manage Kickoff on the 17th!
Edited by Larissa Lane