Multiple Value Streams Per Group: Design exploration
Problem to Solve
We would like more feedback from internal users of GitLab; however, with most of our code in a single project, product teams must share the same configuration. While filtering was a good first step, allowing each team to configure a value stream in way that best models the specific problems they seek to troubleshoot would also allow us to better understand the issues we need to resolve with VSA calculations and configurability for the feature to gain broader adoption.
Intended users
The personas we most expect to use VSA include:
User experience goal
We do not want to erode the simplicity or time-to-value of the current VSA feature by introducing new required configuration or navigation. Instead we wish the option to create additional Value Streams within a group to be available for those that need it but unobtrusive for those that do not.
We expect that any most Value Stream users will ordinarily use only one Value Stream or possibly several even if a single group has many. For this reason, the last selected Value Stream viewed by a given user should be remembered so that in subsequent visits it is not necessary to select it.
While an executive may like to browse a list of Value Streams and quickly scan to better understand similarities and differences with various teams, this experience is out-of-scope for the current story. Such an experience is not needed only for VSA but for Analytics broadly and will be addressed in with a new product category and experience in the future.
Visual: Editing Value Stream
The default Value Stream name should be set to the name of the group.
Permissions and Security
Permissions for creating new Value Streams is the same as those for configuring them generally.
Feature Flag
We will initially make this feature available to the gitlab-org group on gitlab.com and make this available more broadly after we have feedback from internal users and addressed any concerns we have about scale.
What does success look like, and how can we measure that?
Once launched, we will work with Manage group teams to adopt and configure. We will follow-up by reaching out to other GitLab project teams. If adding this feature allows us to identify issues without existing VSA calculations and provides us with additional feedback about regarding the value of VSA, missing features and configuration options, opportunities to improve the user experience, etc. it will have been a success.
What is the type of buyer?
This feature will be made available in Ultimate.