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

Develocity Case Study

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

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

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

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.

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.