VSD - [FE] Adding "DORA Performers score" panel

Release notes

Title: New organization's level DevOps performance view with industry benchmarks based on DORA Scores.

We added a new "DORA Performers score" panel to the Value Streams Dashboard to visualize the status of the organization's DevOps performance levels across different projects. The new view contains an interactive bar chart that displays the scores of DORA performers in three categories - High, Medium, and Low. With DORA scores, software executives can make data-driven decisions, allocate resources effectively, and drive initiatives that enhance the organization's ability to deliver high-quality software faster, with improved stability and reliability. These metrics enable executives to identify areas for improvement, set strategic goals, and measure progress over time. This could also assist to detecting patterns, for example in the chart below you can see that this org sacrificing the software delivery quality for speed (velocity): Over-time behavior of the 4 DORA metrics on the same chart can quickly tell the story of the overall SDLC DevOps performance. Identifying correlations and patterns between multiple metrics trends helps managers understand whether the organization is in the right direction (or not).

Because DORA metrics provide a high-level view of a team’s performance, they can be beneficial for organizations trying to modernize—DORA metrics can help identify exactly where and how to improve. Over time, teams can measure where they have grown and which areas have stagnated.

The DORA scores enable organizations to compare their DevOps performance against industry benchmarks or peers. This benchmarking helps organizations understand where they stand in relation to others and identify best practices or areas where they may be lagging behind. The DORA scores help organizations set specific goals and targets for their DevOps initiative show your team compares to others in the industry.

Problem

The Exec need to understand the organization DORA health top to bottom.

Proposal

1. Add a new widget - "DORA Performers score"
2. Add Bar chart with breakdown per the DORA score category - High, Medium, Low. (Design)
3. The bars will display sum of total projects per score. There will not be an aggregation and the group/sub-group level.
4. Calculate the DORA score monthly, no need for real-time results.
5. In the panel title show the total project count - i.e. Total projects (92) by DORA performers score.
6. Each bar should have a popover with Gitlab's score definition. The details are in this table.
7. For this MVC, this new panel won't be displayed with the default VSD configuration, only via the VSD config file. Release the panel itself as part of the default VSD config but behind a default disabled feature flag. Scope the feature flag to the actual component so that the flag behaviour is consistent across our version of VSD and for customers who add the panel to their config. The feature flag should be scoped to a group level.
8. The position of the new panel should be below the comparison tables.

2022 DORA performers score approach:

GitLab DORA Performers score definition ( backend formula):

1. For DF: when DF < 1 then "Low", when DF >= 30 then "High", else "Medium".
2. For LT4C: when LT4C > 30 days then "Low", when LT4C <= 7 days then "High", else "Medium".
3. For TtRS: when TtRS > 7 days then "Low", when TtRS <= 1 day then "High", else "Medium".
4. For CFR: when CFR > 45% then "Low", when CFR <= 15% then "High", else "Medium".

Popover copy

See example: #386843 (closed)DORA_-Total_projects-tooltips__high.png

Deployment frequency (Velocity)

High	Medium	Low
Have 30 or more deploys to production per day.	Have between 1 to 29 deploys to production per day.	Have less than 1 deploy to production per day.

Lead time for changes (Velocity)

High	Medium	Low
Took 7 days or less to go from code committed to code successfully running in production.	Took between 8 to 29 days to go from code committed to code successfully running in production.	Took more than 30 days to go from code committed to code successfully running in production.

Time to restore service (Quality)

High	Medium	Low
Took 1 day or less to restore service when a service incident or a defect that impacts users occurs.	Took between 2 to 6 days to restore service when a service incident or a defect that impacts users occurs.	Took more than 7 days to restore service when a service incident or a defect that impacts users occurs.

Change failure rate (Quality)

High	Medium	Low
Made 15% or less changes to production resulted in degraded service.	Made between 16% to 44% of changes to production resulted in degraded service.	Made more than 45% of changes to production resulted in degraded service.

Design source

❖ Figma project →

Next iterations

1. Adding filters to the "DORA Performers score" panel.
2. Adding the "DORA Performers score table", with sorting.