docs: upgrade dora benchmarks to 2023 version #712
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Startrekzky
requested changes
Feb 5, 2024
docs/Metrics/CFR.md
Outdated
|
|
||
| | Groups | Benchmarks | DevLake Benchmarks | | ||
| | ----------------- | ---------- | ------------------ | | ||
| | Elite performers | 5% | 0%-5% | |
There was a problem hiding this comment.
I suggest updating the the DevLake Benchmarks to a preciser manner, which is:
(0, 5%]
(5%, 10%]
...
docs/Metrics/MTTR.md
Outdated
| | Groups | Benchmarks | DevLake Benchmarks | | ||
| | ----------------- | ---------------------------- | ---------------------------- | | ||
| | Elite performers | Less than one hour | Less than one hour | | ||
| | High performers | Less one day | Less than one day | |
docs/Metrics/CFR.md
Outdated
| @@ -25,7 +25,17 @@ The number of deployments affected by incidents/total number of deployments. For | |||
|
|
|||
| When there are multiple deployments triggered by one pipeline, tools like GitLab and BitBucket will generate more than one deployment. In these cases, DevLake will consider these deployments as ONE deployment and use the last deployment's finished date as the deployment finished date. | |||
|
|
|||
| Below are the benchmarks for different development teams from Google's report. However, it's difficult to tell which group a team falls into when the team's change failure rate is `18%` or `40%`. Therefore, DevLake provides its own benchmarks to address this problem: | |||
| Below are the 2023 DORA benchmarks for different development teams from Google's report. However, it's difficult to tell which group a team falls into when the team's change failure rate is `13%` or `30%`. Therefore, DevLake provides its own benchmarks to address this problem: | |||
There was a problem hiding this comment.
The correct expression should be:
However, it's difficult to tell which group a team falls into when the team's change failure rate is between 15% and 64%. Therefore, DevLake provides its own benchmarks to address this problem:
docs/Metrics/DeploymentFrequency.md
Outdated
| @@ -25,7 +25,20 @@ Deployment frequency is calculated based on the number of `deployment days`, not | |||
|
|
|||
| When there are multiple deployments triggered by one pipeline, tools like GitLab and BitBucket will generate more than one deployment. In these cases, DevLake will consider these deployments as ONE deployment and use the last deployment's finished date as the deployment finished date. | |||
|
|
|||
| Below are the benchmarks for different development teams from Google's report. DevLake uses the same benchmarks. | |||
| Below are the 2023 DORA benchmarks for different development teams from Google's report. DevLake uses the same benchmarks. | |||
There was a problem hiding this comment.
The correct expression should be:
... from Google's report. However, it's difficult to tell which group a team falls into when the team's deployment frequency is `between once per week and once per month`. Therefore, DevLake provides its own benchmarks to address this problem:
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
npm run buildandnpm run servelocally before submitting this PRSummary
docs: upgrade dora benchmarks to 2023 version
Does this close any open issues?
Related to apache/incubator-devlake#6794
Screenshots
Other Information
Any other information that is important to this PR.