.svg)
2021 SURVEY
Hyperdrive:
A Continuous Delivery Report
A look at the motivations, processes, and psychological
impact of adopting continuous delivery
impact of adopting continuous delivery
How often are teams releasing software?
Sleuth and LaunchDarkly joined forces to ask 203 software development professionals about their approach to shipping and the impact of their process.
Why are teams adopting
Continuous Delivery?
We wanted to understand the rationale behind adoption of continuous delivery, and the metrics teams use to measure progress towards that goal.
Top 5 Reasons For Adoption
Increased speed of feature delivery
Shortened development cycles
Increased release frequency
Improved developer/team flow/productivity
Reduced complexity of development cycle
Top 5 Release Metrics
Deployment frequency
Production downtime
Lead Time
Change failure rate
MTTR
How often are teams deploying vs. how often they’d like to deploy?
It turns out that very few software professionals think they are deploying too fast. This suggests that, in the grand scheme of things, and in proportion to software professionals’ good judgment, software should be delivered more rapidly—i.e. delivery ought to be more continuous.
11%
Deploys multiple times per day
25%
Would like to deploy multiple times per day
30%
Deploys multiple times per month
15%
Would like to deploy multiple times a month
How do feature flags impact deployments?
Since feature flags facilitate a more aggressive release pipeline via both feature-addition and risk-reduction, we supposed that the use of feature flags would correlate positively with other continuous delivery maturity indicators. This turned out to strongly be the case across a wide range of objective and subjective metrics. Discover more findings in the report.
What are the most common tests run before a deployment?
We wanted to understand the rationale behind CD adoption, and the metrics teams use to measure progress towards that goal.
Are development teams experiencing deployment anxiety?
Anybody that has been involved in software releases knows that deployments cause stress and anxiety. The worry over whether things will go smoothly or if people will be pulled away from dinner, sleep, or vacations is real, and certain types of process make it worse.
What's inside
How teams think their development process compares with others
Biggest blockers to automating production deployments
Why there’s more room for automation
Actual vs desired deployment frequency
The impact of feature flags on deployments
Potential causes of deployment anxiety and more
Download the full report for free
About 2021 State of CD
The 2021 State of Continuous Delivery survey is the first in the industry to assess real world progress and challenges to adopting continuous delivery. This report is the result of a collaboration between LaunchDarkly and Sleuth.
More resources
A practical guide for replicating the journey of elite teams towards CD across three phases, from zero to one hundred deploys a day.