nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Measuring "Change Failure Rate"

Jeren Steffen

Looking for suggestions on how to measure/track "Change Failure Rate" (deploy failure rate). We use Jira Software, Jira Service Desk, Confluence, Bamboo, Bitbucket, and Octopus.

Accepted answers

All comments

Gonchik Tsymzhitov

Hi!

Sorry, use case is not clear. Could you clarify, please?

Cheers,

Gonchik Tsymzhitov

Phebe Brown

I just had a request for change failure rate reporting; in this case it would be

Change Failure Rate: the % of tickets in a sprint that are Production or Done that are later moved to the Reopened.

Phebe Brown

(This is for a given sprint)

Jeren Steffen

Sorry for the delayed response, I must have missed the notification of your reply.

We are attempting to follow the 4 kpi's from the book "Accelerate" and are having a difficult time figuring out an accurate (and preferably autonomous) method of tracking Change Failure Rate. This is defined as: The frequency a production deploy results in, and is the direct cause of, any failure requiring immediate repair.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence-server

bitbucket

bamboo

jira-software-server

jira-service-desk-server