📈 15.0 Optimize planning

Summary

groupoptimize

  • Milestone dates: 2022-04-18 to 2022-05-17
  • Build board

Removals and Deprecations

https://docs.gitlab.com/ee/update/deprecations.html#value-stream-analytics-filtering-calculation-change

Capacity / OOO

  • 1.5 BE
  • 1 FE
  • 0.5 UX

Planned OOO (Please order by From date):

Person From To Days
Haim 18 21 4
Pavel 18 26 6
Ezekiel 25/04 - 1

Objectives (WIP)

  1. Completion of the DORA 4 Metrics APIs 🏆
  2. VSA backend date range rebuild
  3. VSA usability improvements 😍 🏆

Themes

  • 🏎 Performance
  • 🔒 Security
  • 😍 Usability
  • 📈 Customer Requests
  • 🏆 OKR
  • 🐛 Bug

GitLab Product Themes

Optimize FY23-Q1 Shared OKR

OKRs 🏆 in Ally:

Title Weight Theme Priority
[VSA] Prepare the aggregated backend for release (gitlab-org/gitlab#351440 - closed) 3 BE 🏆 1
[VSA] Hide the create/end event filter (gitlab-org/gitlab#357513 - closed) 2 FE 🏆 1
Split VSA metrics into 2 rows (gitlab-org/gitlab#359060 - closed) 2 FE 🏆 😍 2
Add tile to VSA for Time to restore service (gitlab-org/gitlab#355304 - closed) 2 FE 🏆 2
Add tile to VSA for DORA Change Failure Rate (gitlab-org/gitlab#357071 - closed) 2 FE 🏆 2
Rename instance_statistics_measurements in Grap... (gitlab-org/gitlab#332323 - closed) 1 BE 🏆 2
[VSA][FE] Move the stage navigation below the f... (gitlab-org/gitlab#349550 - closed) 1 FE 🏆 😍 3
Backfill data for the new DORA Time to restore ... (gitlab-org/gitlab#356377 - closed) 3 BE 🏆 3
Backfill data for the new DORA Change failure r... (gitlab-org/gitlab#357954 - closed) 3 BE 🏆 3
Project level MR analytics not visible to admins (gitlab-org/gitlab#347339 - closed) 1 BE 🐛 3
VSA: Add end event timestamp to table (gitlab-org/gitlab#353554 - closed) 1 BE 🏆 😍 3
Auditor cannot see project Merge request Analytics (gitlab-org/gitlab#357336 - closed) 1 BE 🐛 3
VSA - Change unit for deployment frequency to "... (gitlab-org/gitlab#329629 - closed) 1 BE 🏆 😍 4
VSA: VSA table - rename the Time column to 'Dur... (gitlab-org/gitlab#357824 - closed) 1 FE (CC?) 🏆 😍 4

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!

Previous 14.10 <= => 15.1

Edited by Haim Snir