Correlations to create optimal value streams
- https://gitlab.com/gitlab-org/gitlab-ee/issues/6283 and https://gitlab.com/gitlab-org/gitlab-ee/issues/6273 will tell you about the benefits and costs of your value streams.
- Along with https://gitlab.com/gitlab-org/gitlab-ee/issues/6281, GitLab will tell you where within your value stream, things can be improved, or resources can be shuffled around.
- All this information can be combined and GitLab will tell you if you need to dedicate more time to a certain area/stage.
- For example, if you invest more time and resources in testing (hiring more QA engineers to do QA and writing automated tests), that may improve the quality of your features, but it ultimately makes shipping features slower, and means you are reacting less quickly to the market. You may instead choose to spend less time on QA, ship smaller features and have the market/users give you feedback more quickly. There is a tradeoff here. Based on the information collected and analyzed in the previous issues, GitLab will give you a range of possibilities and provide you some customized sense of optimality.
Edited by Victor Wu