Develocity Case Studies

Develocity Case Study

Earn In

Introduction

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

“It’s a great tool.”

Challenges

The business challenges that led the profiled company to evaluate and ultimately select 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

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: Didn’t Move the Needle
Build & Test Failure Analytics (inc. Flaky Test Management Capabilities): Very Useful

Results

Payback period for their investment in Develocity was within the first 3 months.

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

Level of agreement with the following statements:

Develocity consistently exceeds our expectations for service and support and as a strategic technology partner: somewhat agree
Develocity is a mission-critical component of our developer productivity strategy: agree completely
Developer Productivity Engineering will become a de facto industry-standard software practice much like Agile and DevOps: somewhat agree
Develocity scales well and will meet the service-level expectations of any enterprise-wide deployment: somewhat agree
Develocity is an important enabling technology for our digital transformation strategy: agree completely

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

Build Cache: 50-75%
Test Distribution: 0-25%

Regarding their experience working for a Developer Productivity Engineering (DPE)-enabled organization:

DPE’s impact on their toolchain makes their job more enjoyable: Neither Agree nor Disagree
They would be unlikely to work for a company in the future that did not implement DPE practices: Somewhat Agree
DPE is helpful in recruiting and retaining top talent for their business: Somewhat Agree

Develocity Case Study

VMWare, Inc.

Introduction

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

“Super productive for large teams.”

Use Case

Has utilized Develocity for 1-2 Years.

They also have established a dedicated Developer Productivity Engineering team.

Experience

Experience with the following Develocity capabilities:

Build Scan™: Very Useful
Build Cache: Killer
Test Distribution: Killer

Results

Realized a return on their investment in Develocity was within the first 12 months.

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

Level of agreement with the following statements:

Develocity consistently exceeds our expectations for service and support and as a strategic technology partner: Somewhat Agree
Develocity is a mission-critical component of our developer productivity strategy: Agree Completely
Developer Productivity Engineering will become a de facto industry-standard software practice much like Agile and DevOps: Agree Completely
Develocity scales well and will meet the service-level expectations of any enterprise-wide deployment: Somewhat Agree
Develocity is an important enabling technology for our digital transformation strategy: Somewhat Agree

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

Build Cache: 50-75%
Test Distribution: 75-100%

Regarding their experience working for a Developer Productivity Engineering (DPE)-enabled organization:

DPE’s impact on their toolchain makes their job more enjoyable: Agree Completely
They would be unlikely to work for a company in the future that did not implement DPE practices: Agree Completely
DPE is helpful in recruiting and retaining top talent for their business: Agree Completely

Develocity Case Study

Delivery Hero Se

Introduction

This case study of Delivery Hero SE is based on a May 2023 survey of Develocity customers by TechValidate, a 3rd-party research service.

“The insights from the build scans are super useful. Being from DevX team it is very much helpful with debugging issues reported by the developers. Also, remote cache is extensively used in our day-to-day life.”

Challenges

The business challenges that led the profiled company to evaluate and ultimately select 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
Difficulty achieving success with DevOps initiatives due to existing friction in the development process

Use Case

They have been utilizing Develocity for 1-2 Years.

They have established a dedicated Developer Productivity Engineering team.

Experience with the following Develocity capabilities:

Build Scan™: Very Useful
Build Cache: Killer
Build & Test Failure Analytics (inc. Flaky Test Management Capabilities): Very Useful
Performance and Failure Trends Dashboards: Very Useful

Results

The surveyed company achieved the following results with Develocity:

The payback period for their investment in Develocity was *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.*
Develocity consistently exceeds our expectations for service and support and as a strategic technology partner
Develocity is an important enabling technology for our digital transformation strategy

Reduction in build and test cycle times after using the following Develocity tools:

Build Cache: 25-50%

Regarding their experience working for a Developer Productivity Engineering (DPE)-enabled organization:

DPE’s impact on their toolchain makes their job more enjoyable: Somewhat Agree
They would be unlikely to work for a company in the future that did not implement DPE practices: Somewhat Agree
DPE is helpful in recruiting and retaining top talent for their business: Agree Completely

Develocity Case Study

Applied Materials

Introduction

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

“Good impact on performance.”

Challenges

Challenges experienced prior to implementing Develocity:

Insufficient observability of analytics on build and test performance and regressions, failure trends, and productivity bottlenecks
Cost impacts from an inefficient build and test process and tooling infrastructure

Use Case

Has utilized Develocity for more than 2 Years.

They have established a dedicated Developer Productivity Engineering team.

Experience with the following Develocity capabilities:

Build Scan™: Killer
Build Cache: Killer
Performance and Failure Trends Dashboards: Very Useful

Results

The surveyed company achieved the following results with Develocity:

Agreement with the statement below:
- “Since integrating Develocity into our development process, the time savings we experienced on build and test cycle times have dramatically improved developer productivity.”: Somewhat Agree

Level of agreement with the following statements:

Develocity is a mission-critical component of our developer productivity strategy: agree completely
Developer Productivity Engineering will become a de facto industry-standard software practice much like Agile and DevOps: agree completely
Develocity scales well and will meet the service-level expectations of any enterprise-wide deployment: agree completely
Develocity is an important enabling technology for our digital transformation strategy: agree completely

After using the following Develocity tools, reduction in build and test cycle times:
- Build Cache: 25-50%

Develocity Case Study

Large Enterprise Professional Services Company

Introduction

This case study of a large enterprise professional services company is based on a May 2023 survey of Develocity customers by TechValidate, a 3rd-party research service. The profiled company asked to have their name blinded to protect their confidentiality.

“Very useful for tracking test executions across builds.”

Challenges

Challenges experienced prior to implementing Develocity:

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

Use Case

Has utilized Develocity for 6-12 Months.

Experience with the following Develocity capabilities:

Build Cache: Very Useful
Build & Test Failure Analytics (inc. Flaky Test Management Capabilities): Killer
Performance and Failure Trends Dashboards: Very Useful

Results

The surveyed company achieved the following results with Develocity:

Payback period for their investment in Gradle Enterprise was immediate.

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.”

Level of agreement with the following statements:

Develocity consistently exceeds our expectations for service and support and as a strategic technology partner: agree completely
Develocity is a mission-critical component of our developer productivity strategy: somewhat agree
Developer Productivity Engineering will become a de facto industry-standard software practice much like Agile and DevOps: somewhat agree
Develocity scales well and will meet the service-level expectations of any enterprise-wide deployment: somewhat agree
Develocity is an important enabling technology for our digital transformation strategy: somewhat agree

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

Build Cache: 25-50%
Test Distribution: 0-25%

Regarding their experience working for a Developer Productivity Engineering (DPE)-enabled organization:

DPE’s impact on their toolchain makes their job more enjoyable: Agree Completely
They would be unlikely to work for a company in the future that did not implement DPE practices: Somewhat Agree
DPE is helpful in recruiting and retaining top talent for their business: Somewhat Agree

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 Case Study

Hinge

Introduction

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

“Develocity has been great and it’s working very nicely.”

“Using Develocity has been great. We’ve seen a reduction in build times and it’s great to be able to keep an eye on any performance regressions.
I would (and have) recommend it!”

Challenges

Challenges experienced prior to implementing Develocity:

Too much time spent waiting on build and test feedback either locally or during CI
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
Difficulty achieving success with DevOps initiatives due to existing friction in the development process

Use Case

Has utilized Develocity for 0-6 Months.

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): Don’t Know/Haven’t Tried It
Performance and Failure Trends Dashboards: Didn’t Move the Needle

Results

The surveyed company achieved the following results with Develocity:

Payback period for their investment in Develocity was realized immediately.

Level of agreement with the following statements:

Develocity consistently exceeds our expectations for service and support and as a strategic technology partner: agree completely
Develocity is a mission-critical component of our developer productivity strategy: agree completely
Developer Productivity Engineering will become a de facto industry-standard software practice much like Agile and DevOps: agree completely
Develocity scales well and will meet the service-level expectations of any enterprise-wide deployment: agree completely

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

Build Cache: 25-50%

Develocity Case Study

PicPay Sees Payback within 3 Months by Deploying Build Scan™ and Build Cache

Introduction

This case study of PicPay is based on an October 2021 survey of Develocity customers by TechValidate, a 3rd-party research service.

Challenges

PicPay experienced the following challenges 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
Issues with recruiting/retention related to the developer experience (e.g. Unreliable build and test toolchain)
Difficulty communicating build details between teams and collaborating when troubleshooting failures
Managing the growth of build and test cycles as the codebase grows

Use Case

PicPay has utilized Develocity for 6-12 Months.
They found the Build Scan™ and Build Cache to be “Killer” features
Additionally, they found the Performance and Failure Trends Dashboard to be very useful.

Results

PicPay’s payback period for their investment in Develocity was within the first 3 months.
In addition, PicPay agreed with the following statements:
- “Develocity consistently exceeds our expectations for service and support and as a strategic technology partner.”
- “Developer Productivity Engineering will become a de facto industry-standard software practice much like Agile and DevOps.”
- “Develocity scales well and will meet the service-level expectations of any enterprise-wide deployment.”
Additionally, PicPay’s experience to date adapting and implementing DPE practices has led the Android Engineering Manager to conclude that DPE’s impact on their toolchain makes their job more enjoyable and that DPE is helpful in recruiting and retaining top talent for their business.

Develocity Case Study

Paxos Views Develocity as Mission-Critical to their Developer Productivity Strategy

Introduction

This case study of Paxos is based on an October 2021 survey of Develocity customers by TechValidate, a 3rd-party research service.

Challenges

Prior to implementing Develocity, Paxos 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

Use Case

Paxos has utilized Develocity for less than six months.
Paxos found the Build Cache to be a “killer” feature and describe the Build Scan™, Build & Test Failure Analytics, and Performance and Failure Trends Dashboards as very useful features.

Results

Paxos experienced an immediate payback period for their investment in Develocity.
Regarding Paxos’s experience with Develocity, they indicated agreement 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.”
Additionally, Paxos’s experience to date adapting and implementing DPE practices has led the respondent, a Senior Software Engineer, to conclude that DPE’s impact on their toolchain makes their job more enjoyable.

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 Case Study

Develocity Exceeds Aetna’s Expectations for Scalability, Service and Support

Introduction

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

Challenges

Aetna was experiencing the following pains which led them to evaluate and ultimately select Develocity:

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

Use Case

Aetna has been utilizing Develocity for 6-12 months.
In that time, they have established a dedicated Developer Productivity Engineering team.
Aetna rated the Build Scan, Build Cache, and Performance and Failure Trends Dashboards as “killer” features, and the Flaky Test Management functionality as “very useful.”

Results

Aetna experienced an immediate payback period on their investment.
Aetna indicated complete agreement 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.”
Additionally, Aetna’s experience to date adapting and implementing DPE practices has led the case study subject, a Staff Engineer, to conclude that DPE’s impact on their toolchain makes their job more enjoyable and that DPE is helpful in recruiting and retaining top talent for their business.

TechValidate Research on Develocity

11 Case Studies

Earn In

Introduction

Challenges

Use Case

Results

Company Profile

About Develocity

VMWare, Inc.

Introduction

Use Case

Experience

Results

Company Profile

About Develocity

Delivery Hero Se

Introduction

Challenges

Use Case

Results

Company Profile

About Develocity

Applied Materials

Introduction

Challenges

Use Case

Results

Company Profile

About Develocity

Large Enterprise Professional Services Company

Introduction

Challenges

Use Case

Results

Company Profile

About Develocity

Revolut

Introduction

Challenges

Use Case

Results

Company Profile

About Develocity

Hinge

Introduction

Challenges

Use Case

Results

Company Profile

About Develocity

PicPay Sees Payback within 3 Months by Deploying Build Scan™ and Build Cache

Introduction

Challenges

Use Case

Results

Company Profile

About Develocity

Paxos Views Develocity as Mission-Critical to their Developer Productivity Strategy

Introduction

Challenges

Use Case

Results

Company Profile

About Develocity

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

Introduction

Challenges

Use Case

Results

Company Profile

About Develocity

Develocity Exceeds Aetna’s Expectations for Scalability, Service and Support

Introduction

Challenges

Use Case

Results

Company Profile

About Develocity