Print PDF

How much can you improve your developer productivity?

Annual R&D Cost Recapture

$7,581,600

Annual Developer Hours Saved

81,600hours/year

Each Developer Saves per Week

5.7hours/week

This calculator is a model that we have developed by working with hundreds of build teams to quantify the impact of your build on developer productivity. Set the input fields to drive the calculator results above.

Size Your Team and Build

How many developers are on your team?

Cost per developer per year

The ‘fully loaded’ cost per engineering year, including salary and benefits.

Annual
Work Weeks

Developer Cost
per Minute

The ‘fully loaded’ cost per engineering minutes, taking the annual engineering cost and dividing by the minutes in the number of working weeks per year.

Approximate Developer builds per day

The approximate number of times a typical developer performs a local software build every day. (not including CI builds).

Local BuildsWeek

This number is calculated by taking the “Approximate Developer builds per day” from above and multiplying by the total number of developers and assuming 5 days per work week.

CI BuildsWeek

Edit this field to specify your approximate number of Continuous Integration (CI) builds per week.

Speed up Slow Builds

Develocity gives you the data and infrastructure services to speed up builds, including a remote build cache that shares unchanged artifacts across the entire team.

Speed Up Local Builds

Number of Local builds per week (calculated from above)

Average Local build minutes (without data or cache)

Input your approximate total build time for a developer local build.

Percentage of build wait time reduced

Use the slider to estimate a percentage of the local build time that can be eliminated by using data to optimize the Develocity remote build cache, as well as increasing build avoidance, parallelism, and other build optimizations.
In our experience the typical build time is reduced by at least 50% and sometimes up to 90%.

Average Local build minutes (with data and cache)

The new build time estimate - calculated by applying the “Percentage of build wait time reduced” to the “Average Local build minutes (without data or cache)”

Saved Developer minutes with data and cache

The build time eliminated by applying the “Percentage of build wait time reduced” to the “Average Local build minutes (without data or cache)”

Saved Developer hours per week (all developers)

The number of total developer hours saved each week across the team due to faster local builds, based on the team size estimate and time saved per local developer build.

Saved Developer hours per week (each developer)

The number of total developer hours saved each week by each developer due to faster local builds, based on the team size estimate and time saved per local developer build.

Annual R&D Recaptured (all developers)

This is the total value of the R&D time saved by all developers each year just due to faster local builds - based on the team size and annual cost per developer above.

Speed Up Continuous Integration Builds

Number of CI builds per week (calculated from above)

Average CI build minutes (without data or cache)

Input your approximate total build time for a typical Continuous Integration (CI) process build.

Percentage of build wait time reduced

Use the slider to estimate a percentage of the CI build time that can be eliminated by using data to optimize the Develocity remote build cache, as well as increasing build avoidance, parallelism, and other build optimizations.
In our experience the typical build time is reduced by at least 50% and sometimes up to 90%.

Percentage of CI builds where developers are waiting

Use the slider to estimate the percentage of CI builds that create waiting time for developers. In our experience, this number is typically around 20%.

Average CI build minutes (with data and cache)

The new build time estimate - calculated by applying the “Percentage of build wait time reduced” to the “Average CI build minutes (without data or cache)”

Saved Developer minutes with data and cache

The build time eliminated by applying the “Percentage of build wait time reduced” to the “Average CI build minutes (without data or cache)”

Saved Developer hours per week (all developers)

The number of total developer hours saved each week across your entire team, based on the team size estimate and time saved per CI build.

Saved Developer hours per week (each developer)

The number of total developer hours saved each week for every developer, based on the team size estimate and time saved per CI build.

Annual R&D Recaptured (all developers)

This is the total value of the R&D time saved by all developers each year just by reducing the wait time for CI builds - based on the team size and annual cost per developer above.

Maintain Build Speed Over Time

Builds won't stay fast without continued maintenance. Build Scans give you a wealth of data on each build so that you can optimize performance every day. These benefits include configuration, network effects, JVM performance, and other issues in addition to output caching.

Percent slowdown annually
without ongoing optimization

Without continuous optimization, all builds become more complex and slow down over time. Use the slider to estimate how much slower your build becomes over the course of a year if you do not use data to prevent build regressions. In our experience, this value is typically at least 15%.

Annual R&D
Recapture

This is the total value of the R&D time saved each year by using data to continually prevent build regressions.

Accelerate Debugging

Develocity gives developers the visibility to fix code-related build issues without having to ask the build team to rerun broken builds to reproduce and debug the problem.

Percentage of Local builds that fail

Use the slider to estimate percentage of local developer builds that fail due to code errors or problems with the build itself. In our experience, this is typically about 20%.

Percentage of CI builds that fail

Use the slider to estimate percentage of CI builds that fail due to code errors or problems with the build itself. In our experience, this is typically about 10%.

Local failures needing investigation

Use the slider to estimate the percentage of local build failures that require and investigation by the build team, usually due to a problem with either the developer code or the build itself. In our experience, this is typically about 5%.

CI failures needing investigation

Use the slider to estimate the percentage of CI build failures that require and investigation by the build team, usually due to a problem with either the developer code or the build itself. In our experience, this is typically about 20%.

Time saved per local investigation (min)

Estimate the approximate time required for each investigation into the cause of a local build failure. This figure will be used as input into the calculation of the total time savings.

Time saved per CI investigation (min)

Estimate the approximate time required for each investigation into the cause of a CI build failure. This figure will be used as input into the calculation of the total time savings.

Saved Developer hours per week

The weekly hours saved across the entire team due to faster debugging of build failures.