docs: streamline formatting and proofreading

This commit is contained in:
Stefan Rotsch
2023-10-16 12:22:46 +02:00
committed by Stefan Rotsch
parent 2c541dfbea
commit 94ac286c34
43 changed files with 177 additions and 257 deletions

View File

@@ -5,25 +5,24 @@ quadrant: methods-and-patterns
tags: [devops, documentation, agile]
---
A primary goal of software development organizations is to improve the performance of software delivery and operations.
A primary goal of software development organizations is to enhance the performance of software delivery and operations.
There are a lot of best practices and also different opinions on how to do "devops the right way".
We have learned that IT organizations and software delivery are complex issues. This means that most of the time there are no "easy" answers: Instead, contextual continuous improvement is a critical element.
There are numerous best practices and differing opinions on how to approach "DevOps the right way." We've learned that IT organizations and software delivery are complex issues, which means that most of the time there are no "easy" answers. Instead, continuous improvement within a contextual framework is a critical element.
To bring more objectivity and some form of verifiability into this, we like to use the four key metrics suggested by "The state of devops" and "DORA". These four key metrics are
To introduce more objectivity and a measure of verifiability, we like to use the four key metrics suggested by "The State of DevOps" and "DORA." These four key metrics are:
**To evaluate velocity:**
- Deployment Frequency (How often a team successfully deploys to production, e.g. daily, weekly, monthly, yearly)
- Deployment Frequency (How often a team successfully deploys to production, e.g., daily, weekly, monthly, yearly)
- Lead time for changes (the average time it takes to deploy a commit to production)
**To evaluate stability:**
- Time to Restore Services (For a failure, the median time between the deployment that caused the failure and the remediation)
- Change Failure Rate (The number of failures per number of deployments)
## About DORA
The DevOps Research and Assessment (DORA) is the largest and longest-running research program of its kind, seeking to understand the capabilities driving software delivery and operations performance. Their report "The State of DevOps" regularly provides insights, observations, and relationships of IT organizations deemed "high performing".
### About DORA
The DevOps Research and Assessment (DORA) is the largest and longest-running research program of its kind, aiming to understand the capabilities driving software delivery and operations performance. Their report, "The State of DevOps," regularly provides insights, observations, and insights into high-performing IT organizations.
## Additional Information
- https://medium.com/@jezhumble/doras-journey-an-exploration-4c6bfc41e667
- https://dora.dev/
- https://github.com/dora-team/fourkeys
### Additional Information
- [DORA Website](https://dora.dev/)
- [DORA's Journey: An Exploration](https://medium.com/@jezhumble/doras-journey-an-exploration-4c6bfc41e667)
- [DORA GitHub Repository](https://github.com/dora-team/fourkeys)