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.
Deploy multiple times per day
Would like to deploy multiple times per day
Deploy multiple times per month
Would like to deploy multiple times a month
Sleuth and LaunchDarkly joined forces to ask 203 software development professionals about their approach to shipping and the impact of their software release processes.
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.
We wanted to understand the rationale behind CD adoption, and the metrics teams use to measure progress towards that goal.
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.
We wanted to understand the rationale that’s driving software developers to adopt continuous delivery. And since it’s been said that executives love continuous delivery more than developers, we broke down the reasoning by job role, which you can find in the report.
A look at the motivations, processes, and psychological impact of adopting continuous delivery.
2021 SURVEY
By completing this form you consent to our Privacy Policy, and receive product updates and announcements. Unsubscribe anytime.