Case Study Deskcasestudydesk.com
SoftwareSourced

Case Study: Duda improves cycle time 75% and lifts deployment frequency 20% with LinearB

Duda Case StudySourced & dated by Case Study Desk
Key facts · TL;DR
Company
Duda
Industry
Software
Challenge
Make dev-culture and CI/CD impact measurable
Headline result
Duda improved cycle time by 75% and grew deployment frequency 20% year over year, ranking in the top 5-10% of benchmarks

Key results

75%
Cycle time improvement
since adopting LinearB
20%
Deployment frequency increase
year over year
Top 5-10%
Benchmark ranking

The challenge

Duda wanted to make the impact of its engineering culture and CI/CD practices measurable rather than anecdotal. Leadership needed data to show that small changes and disciplined delivery were improving outcomes.

The solution

Duda adopted LinearB to measure cycle time and deployment frequency and to expose delivery data across the team. The visibility let engineering leaders connect cultural practices to concrete delivery metrics.

Dev Culture isn't something you can see or measure, but in our case, it is. You can preach about CI/CD and small changes, but in LinearB, you can actually see the data.

RS
Ronny Shapiro
VP of Engineering, Duda

The results, in context

Since adopting LinearB, Duda improved cycle time by 75% and increased deployment frequency by 20% year over year, placing it in the top 5-10% of benchmarks. The data made the team's dev-culture improvements visible and trackable.

Products used

LinearB Cycle time metricsLinearB Deployment frequency tracking