This page describes the Four Keys analysis.
Table of Contents
- What are Four Keys?
- How to use Four Keys
- How to use the Four Keys feature in Offers MGR
- How to use Four Keys in a team
- External communication as a material for technical publicity
- Criteria for each Four Keys indicator
What are Four Keys?
DevOps Research and Assessment (DORA) has proposed a framework called FourKeys to assess the maturity of DevOps in software development.
The following is an overview of each indicator.
- Lead Time: Lead time refers to the period of time between the submission of an idea or requirement and the actual production release. By reducing this metric, companies can respond to market needs and deliver business value faster.
- Deployment Frequency: Deployment Frequency indicates the number of deployments released per unit of time. By increasing this metric, companies can make changes, such as adding features or fixing bugs, more quickly and deliver value to users.
- Change Failure Rate: The Change Failure Rate indicates the failure rate of changes in the production environment. By keeping this metric low, companies can deliver quality products and services and improve reliability.
- Mean Time to Restore: Mean Time to Restore indicates the time it takes to recover from a system failure or problem. By reducing this metric, companies can minimize the impact of failures and improve the user experience.
By improving these metrics, companies can provide faster, more reliable products and services and gain a competitive advantage.
How to use Four Keys
The analysis results obtained by Four Keys in a development organization can be used in the following ways
- Problem identification and improvement: Using Four Keys, development teams can identify problems and make improvements to solve them. For example, if deployment frequency is low, deployment speed can be increased by improving the CI/CD pipeline and introducing automation.
- Prioritization: Based on each aspect of the Four Keys, you can determine the order in which to prioritize improvements. For example, if the lead time for a change is too long, you can prioritize it for improvement to deliver business value faster.
- Evaluate Results: Using Four Keys, development teams can track how improvement actions impact ITSM performance. Through these assessments, development teams can see the impact of their improvements and ensure continuous improvement.
- Goal Setting: Four Keys can be used as a metric for development teams to set goals. Development teams can aim for higher deployment frequency, shorter change lead times, lower change failure rates, and shorter mean time to repair
How to use the Four Keys feature in Offers MGR
Basic Usage Flow
- Connect GitHub to your project
- Access Offers MGR's FourKeys analysis feature page
- https://offers-mgr.com/performance/four-keys/
- Click the "FourKeys Analysis Settings" button at the arrow to go to the settings page.
Branch Configuration
- Deployment Frequency
- Branch
- If you are not using release tagging, use this option. ex: set main or master
- If you are operating with the release tag off, the following will be used.
- Release tag
- If you are using release tagging, use this if you are using release-yyyymmdd or something similar.
- Branch
- Change Failure Rate
- Branches
- Set up branch names such as hotfix, fix, etc.
- Branches
- After setting up the aggregation, data aggregation for Four Keys will be completed in about 30 minutes to 1 hour.
Screen after setting
- Score Trends, Data Source tab
- The Score Trends tab shows the trends of the indicator over a period of time.
- The Data Sources tab shows the evolution of the definitions that make up the indicator over a period of time.
- Mouse hover over the label to see the criteria. Detailed information on the detailed criteria is provided at the bottom of the page.
How to use Four Keys in a team
- Review Four Keys metrics and definitions in retrospectives (periodic development reviews), monthly product-wide review opportunities, etc., and implement KPT
- Evaluate results through periodic bi-weekly or monthly check-ins
- Use as a quantitative value to track the team's MBOs and OKRs
External communication as a material for technical publicity
Because it is a common global definition, it can be used to demonstrate the health and transparency of your development organization.
Criteria for each Four Keys indicator
It is also implemented in OffersMGR based on standards published by Google on GitHub.
Reference: https://github.com/dora-team/fourkeys#color-coding
Deployment frequency
| Definition |
Measurement Overview | Metrics |
| Elite | Multiple times a day | More than 1.0 |
| High | Once a day or once a week | 0.2 or more~less than 1.0 |
| Medium | Once a month to more than once every six months | 0.04 or more~less than 0.2 |
| Low | Less than once every six months | less than 0.04 |
Change Lead Time
| Definition |
Measurement Overview | Metrics |
| Elite | Less than 1 day | Less than 24h |
| High | More than 1 day ~ Less than 1 week | More than 24h but less than 168.0h |
| Medium | More than 1 week ~ less than 1 month | More than 168.0h~Less than 720.0h |
| Low | More than 1 month | 720.0h or more |
Change Failure Rate
| Definition | Metrics |
| Elite | 0% - less than 15 |
| High | 15% - Less than 30 |
| Medium | 30% - less than 45 |
| Low | More than 45 |
MTTR
| Definition |
Measurement Overview | Metrics |
| Elite | Less than 1 day | Less than 1h |
| High | More than 1 hour ~ less than 1 day | More than 1h but less than 24.0h |
| Medium | More than 1 day ~ less than 1 week | More than 24.0h but less than 168.0h |
| Low | More than 1 week | 168.0h or more |
Comments
0 comments
Please sign in to leave a comment.