Skip to main content

Calculate the hard cost of your un-merged pull requests

Nov 2, 2017 by DROdio

Finding Velocity is our blog series for executives where we share strategies to deliver software to users faster and more confidently (and why creating this deep competency in software matters strategically).

 

We were just onsite with Kieran Lal, Senior Director of API Design products at Mulesoft. He said to us:

What a great way to describe the cost of low deployment velocity in a way that resonates with product leaders, and not just engineering leaders.

Want to calculate that cost at your company? Here’s how:

To calculate hard costs using man-hours: (# of open PRs [1]) x (man-hours of engineering time required for each PR) x (avg. eng. employee hourly rate)

To calculate hard costs using JIRA story points: (# of open PRs [1]) x (story points for each PR) x (avg. eng. dollar cost per story point)

To calculate opportunity & innovation costs to the business:

  1. Figure out how much revenue each employee at your company is responsible for driving. For example, if your company makes $1Bn in annual revenue, and it has 2,000 employees, then each employee is responsible for contributing $500,000 in revenue to the business — but only if their work is getting out the door!
  2. Assuming each employee works 2,000 hours per year, that would mean that each employee’s hourly revenue contribution is $250.
  3. Then calculate (# of open PRs [1]) x (man hours of engineering time required for each PR) x (revenue contribution/hr -- i.e., $250).

[1] Here’s the actual query you can run in your Github repo(s) to find the number of un-merged PRs: org:[your-org-name] is:open is:pr is:private

These numbers will add up quickly and show the true cost of low deployment velocity. Luckily, Armory is here to help. Our entire mission is to accelerate deployment velocity through automation and safety. Your developers’ code should be flowing continuously, and safely, to production, without being held up in a virtualized inventory state.

Learn More:


How Companies Go Digital: We highly recommend O’Reilly’s free PDF e-Book about migrating toward cloud-native technologies and practices by shifting from monolithic onsite architectures to applications designed solely to operate on cloud computing platforms. Get the highlights here.

Recently Published Posts

Welcoming 2022: Reflecting and looking forward

Dec 22, 2021
|
by Jim Douglas

Nearly all cultures globally have some form of celebration marking the Winter Solstice. Common threads found in most observances of the annual event are celebration of family and friends (living and past), reflection of the past year, and some form of giving thanks for continued health and sustenance. Exiting 2021, said celebrations would seem especially […]

Read more

Resiliency and Load distribution

Dec 16, 2021
|
by Daniel Gonzalez

Introduction When scaling a network service, there are always two concerns: resiliency and load distribution, to understand these concepts let us first understand the broader term “Redundancy”. Redundancy is the duplication of a component to increase reliability of the system, usually in the form of a backup, fail-safe, or to improve actual system performance. Resiliency […]

Read more

CVE-2021-44228 – log4j (Log4Shell) – an analysis

Dec 10, 2021
|
by Jason McIntosh

Today marked a 0-day disclosure of a rather nasty vulnerability in one of the most commonly used frameworks for logging – log4j.  This one is nasty on multiple levels.  Note that Armory Enterprise is NOT affected by this vulnerability.  The impact on this vulnerability is likely huge and is already being exploited.  Additionally it can […]

Read more