The 2023 Accelerate State of DevOps Survey is now open! Take the survey now

Your software delivery performance

You're performing better than    % of 2019 State of DevOps Survey respondents. 

Take the Quick Check from other research years: 2019  2021  2022

Key DevOps capabilities for unknown performers

When we analyzed the responses of other unknown performers, we found that working on these three capabilities had the most impact on improving their software delivery performance.

Rank your responses to a series of 3-12 questions for each of these three capabilities, to determine how you perform and which to consider focusing on first.

Key DevOps capabilities recommended for you

Based on your performance profile, we think you should work on the three capabilities listed below. Based on your responses to the capabilities assessment, we recommend you focus on first. How was this calculated?

Capability A Key focus area

Capability A description

View solution

Capability B

Capability B description

View solution

Capability C

Capability C description

View solution

How your performance compares

Based on your quick check answers, see how you compare to the 2019 State of DevOps respondents overall, and to people within the same industry as you.

unknown performance profile breakdown

Based on your performance, you are classified as a unknown performer. Here is how the performance profiles compare. Note that your answers to the five questions asked in Step 1 of the quick check may not match the descriptions in the table below. The performance profiles in this table are based on statistical analysis of the aggregated responses to the 2019 State of DevOps survey. For more on this analysis, read the “Methodology” section of the State of DevOps Report.

Aspect of software delivery performance Low Medium High Elite

Deployment frequency

For the primary application or service you work on, how often does your organization deploy code to production or release it to users?

Low: Between once per month and once every six months Medium: Between once per week and once per month High: Between once per day and once per week Elite: On demand (multiple deploys per day)

Lead time for changes

For the primary application or service you work on, what is your lead time for changes (that is, how long does it take to go from code committed to code successfully running in production)?

Low: Between one month and six months Medium: Between one week and one month High: Between one day and one week Elite: Less than one day

Time to restore service

For the primary application or service you work on, how long does it generally take to restore service when a service incident or a defect that impacts users occurs (for example, unplanned outage or service impairment)?

Low: Between one week and one month Medium: Less than one day High: Less than one day Elite: Less than one hour

Change fail rate

For the primary application or service you work on, what percentage of changes to production or released to users result in degraded service (for example, lead to service impairment or service outage) and subsequently require remediation (for example, require a hotfix, rollback, fix forward, patch)?

Low: 46-60% Medium: 0-15% High: 0-15% Elite: 0-15%