Comparing VSM analytics across teams/entities.

https://gitlab.com/gitlab-org/gitlab-ee/issues/6323 is about surfacing analytics for a particular "team" over time. That "team" could be a single engineering team. It could be a department with multiple smaller crews/squads. Or it can even be the entire organization. What is important is that in that issue, the concern is tracking how well you perform over time, and quickly triaging, and identifying how you can improve, based on learnings of yourself.

This issue deals with when you have separate entities in your organization, and they are independent. As a result, you'd expect each entity to have differing results of VSM analytics. So in an organization, it is useful to compare these results across entities.

For example, if the iOS engineering team is having problems in the QA stage, but the Android engineering team is having optimal QA with super automated tests, then a senior engineering manager who oversees both teams would want to know that. That engineering manager wants to identify why one team is excelling in that one area and why another team is not. The manger can then identify problems, identify why the Android team is doing well, help facilitate best practices. So GitLab needs to make this super easy for that manager.

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.