Skip to content

Optimize priorities

Problem

As of %14.2, a substantial part of the Optimize backend team is working on ~"group::access" security issues. During this time Optimize frontend was helping with backend work (i.e., security issues) and working on UX improvements and tech debt for VSA and DevOps adoption. The security backlog burn down effort is likely to be prolonged as per this proposal. Moreover, groupoptimize will soon be lacking permanent UX support since Nick will transition to ~"group::workspace". frontend is likely to run out of UX improvements and tech debt issues (related to VSA and DevOps Adoption) soon and needs perspective.

We have a filled backlog for frontend that contains a good mix of feature work, UX improvements and tech debt related to other Optimize features but we need clear priorities should make a decision on which areas the team should focus on next (beginning of %14.5 / %14.6)

Depending on the decision being made in https://gitlab.com/gitlab-org/gitlab/-/issues/341883, there's two scenarios that I can think of:

  • (Part of) backend will resume work on Optimize features soon
  • frontend won't have backend support for a longer period of time

Open questions

  • Should we should plan accordingly for both scenarios ☝ ?
  • It looks like VSA will remain a top priority for Optimize?
  • What about DevOps adoption? Do we need more usage data before we decide on its future?
  • What other features (Issue Analytics, Repository Analytics, ...) should we focus on?
  • Will there be some sort of UX support that we can count on?

Proposal

Optimize Feature Dashboard

https://app.periscopedata.com/app/gitlab/779829/Manage:Optimize-Feature-Usage

/cc @djensen @ogolowinski @npost @m_gill What do you all think?

Edited by Orit Golowinski