Original Research on Develocity

Develocity Case Study

Revolut

Introduction

This case study of Revolut is based on a June 2023 survey of Develocity customers by TechValidate, a 3rd-party research service.

“Develocity is an amazing tool that helps us a lot.”

Challenges

Challenges experienced prior to implementing Develocity:

Too much time spent waiting on build and test feedback either locally or during CI
Inability to easily troubleshoot and determine the root cause of build, test, and CI failures including flaky tests
Insufficient observability of analytics on build and test performance and regressions, failure trends, and productivity bottlenecks
Managing the growth of build and test cycles as the codebase grows
Time-to-market impacts from an inefficient build and test process and tooling infrastructure

Use Case

Has utilized Develocity for 1-2 Years.

They have not established a dedicated Developer Productivity Engineering team.

Experience with the following Develocity capabilities:

Build Scan™: Very Useful
Build Cache: Killer
Test Distribution: Don’t Know/Haven’t Tried It
Build & Test Failure Analytics (inc. Flaky Test Management Capabilities): Didn’t Move the Needle
Performance and Failure Trends Dashboards: Didn’t Move the Needle

Results

The surveyed company achieved the following results with Develocity:

Experienced a payback period for their investment in Develocity within the first 3 months.

Agreed completely that “Since integrating Develocity into our development process, the time savings we experienced on build and test cycle times have dramatically improved developer productivity.”

After using the following Develocity tools, reduction in build and test cycle times:

Build Cache: 75-100%
Test Distribution: N/A

Develocity Customer Statistic

Builds and Tests are Slow!

84% of surveyed IT organizations experienced challenges with too much time spent waiting on build and test feedback either locally or during CI prior to implementing DPE.

84%

Develocity Customer Research

Development Pains are Widespread

Which of the following challenges or pain points did your organization experience prior to implementing Developer Productivity Engineering?

Too much time spent waiting on build and test feedback either locally or during CI	84%
Inability to easily troubleshoot and determine the root cause of build, test and CI failures including flaky tests	65%
Insufficient observability of analytics on build and test performance and regressions, failure trends, and productivity bottlenecks	59%

Develocity Customer Research

Developer Pain Points Without DPE

Which of the following challenges or pain points did your organization experience prior to implementing Developer Productivity Engineering?

Too much time spent waiting on build and test feedback either locally or during CI	90%
Insufficient observability of analytics on build and test performance and regressions, failure trends, and productivity bottlenecks	70%
Inability to easily troubleshoot and determine the root cause of build, test and CI failures including flaky tests	65%
Managing the growth of build and test cycles as the codebase grows	55%
Difficulty communicating build details between teams and collaborating when troubleshooting failures	45%
Cost impacts from an inefficient build and test process and tooling infrastructure	35%
Time-to-market impacts from an inefficient build and test process and tooling infrastructure	20%
Difficulty achieving success with DevOps initiatives due to existing friction in the development process	15%
Issues with recruiting/retention related to the developer experience (e.g. Unreliable build and test toolchain)	10%

Develocity Case Study

Spotify Realizes Build Feedback Cycle Time Improvements of up to 75% with Develocity

Introduction

This case study of Spotify Ltd. is based on a September 2021 survey of Develocity customers by TechValidate, a 3rd-party research service.

Challenges

Prior to implementing Develocity, Spotify was experiencing the following challenges:

Too much time spent waiting on build and test feedback either locally or during CI
Inability to easily troubleshoot and determine the root cause of build, test, and CI failures including flaky tests
Insufficient observability of analytics on build and test performance and regressions, failure trends, and productivity bottlenecks
Difficulty communicating build details between teams and collaborating when troubleshooting failures
Managing the growth of build and test cycles as the codebase grows
Difficulty achieving success with DevOps initiatives due to existing friction in the development process

Use Case

Spotify has been utilizing Develocity for more than 2 years.
During that time, they have established a dedicated Developer Productivity Engineering team.
Spotify found the Build Scan™ and Build Cache to be “killer” features, and described the Performance and Failure Trends Dashboard as a very useful feature.

Results

Spotify realized payback on their investment in Develocity within the first 3 months.
Spotify “completely agrees” with the following statements:
- “Since integrating Develocity into our development process, the time savings we experienced on build and test cycle times have dramatically improved developer productivity.”
- “Develocity consistently exceeds our expectations for service and support and as a strategic technology partner.”
- “Develocity is a mission-critical component of our developer productivity strategy.”
- “Develocity scales well and will meet the service-level expectations of any enterprise-wide deployment.”
- “Develocity is an important enabling technology for our digital transformation strategy.”
Spotify saw a 50-75% reduction in build feedback cycle times as a result of using the Build Cache.
Additionally, Spotify’s experience to date adapting and implementing DPE practices has led a Build/Release Engineer to conclude that they would be unlikely to work for a company in the future that did not implement DPE practices.

Develocity Customer Statistic

The Build Cache is a Killer Feature

Two-thirds of surveyed IT organizations rated GE’s Build Cache as ‘Killer’.

TechValidate Research on Develocity

These pages present data that TechValidate has sourced via direct research with verified customers and users of Develocity. TechValidate stands behind the authenticity of all published data. Learn more »

About TechValidate Research

Selected Research Highlights

Revolut

Introduction

Challenges

Use Case

Results

Company Profile

About Develocity

Builds and Tests are Slow!

Development Pains are Widespread

Developer Pain Points Without DPE

Spotify Realizes Build Feedback Cycle Time Improvements of up to 75% with Develocity

Introduction

Challenges

Use Case

Results

Company Profile

About Develocity

The Build Cache is a Killer Feature

More to Explore

About Develocity

Develocity speeds up your builds and tests, makes troubleshooting more efficient, and increases toolchain reliability, giving your developers back at least one day each week in lost productivity. Now supporting Maven, Bazel, sbt, and Gradle build systems.