Calculate Incredibuild’s value for your team

The following questions will help create a report of estimated impact of Incredibuild acceleration on your existing development pipelines. Please fill out all fields to your best current estimation - you will be able to refine these details later.

Basic assessment
Extended assessment

*Please fill out all fields to your best current estimation

Your Team

How many C++ Developers are on your team?
Devs *Required field - please fill out
We use this as a baseline to calculate the time dev acceleration saves your developers.
Which operating system do you use?
  *Required field - please fill out
Which industry does your team work in?
  *Required field - please fill out

Productivity

How long does an average full developer build take today?
Minutes *Required field - please fill out
Include builds of different types and lengths together by averaging them out.
On average, how many full builds does a developer run per day?
Builds *Required field - please fill out
You should include two often overlooked full builds:new branch creation triggers a full rebuild. Performing a "getlatest" at the start of the day triggers a near full build.
How long does an average centralized (CI) build take today?
Minutes *Required field - please fill out
This tells us the rate of CI builds. Several build types with different lengths is okay. Get them all and calculate the average time to completion.
How many centralized (CI) builds are run per day?
Builds *Required field - please fill out
This tells us how long your team waits for main builds to complete. Include the average for all builds during weekends and night builds.

Broken Build Resolution

Estimate the average percent of full centralized (CI) builds that break out of all CI builds that you run
  *Required field - please fill out
What is the rate of builds that get critical errors and fail to complete? Out of all builds in an average month (in the local and ci build questions), what percentage of these break?
What percentage of your team participates in finding and resolving a broken build issue?
  *Required field - please fill out
What is the average time per developer to find and resolve a broken full Centralized/ CI build?
Minutes *Required field - please fill out

Quality & Bug Fixes

How many defects (bugs) in production do you experience annually?
Defects *Required field - please fill out
From the total of annual defects (from the previous question), how many are critical bugs?
Bugs *Required field - please fill out
Forrester estimates $10k avarge in quality related study
What percentage of the time saved by acceleration would you use to increase testing coverage?
  *Required field - please fill out

Speed and Time to Market

How many releases do you currently launch per year?
Releases *Required field - please fill out
Please include both major and minor releases.
Generalize the cost to the business of a 24-hour delay of a release, or alternately the time it takes to resolve a critical bug?
$ *Required field - please fill out
Some examples may include: Costs of downtime of SaaS product, cost of idle processes waiting for issue to resolve, churn because of time to resolve, cost of customer support about these critical issues.

On-prem and Cloud infrastructure

Estimate your annual on-prem costs of your build infrastructure for the team?
$ *Required field - please fill out
Include all HW purchase, maintenance costs, and space costs, for servers and desktops executing build workload, as well as unique software license costs for each machine.
What is your total annual software development cloud cost?
$ *Required field - please fill out
We will assume 50% of your compute spend here is related to builds.

ROI Highlights

  • Assumes 75% Acceleration
  • Does not include Build Cache
(Actual results may vary)

0

Annual developer time saved due to faster builds

*

Resolving broken builds Faster (annual hours)