Edition 2 - Going Beyond Test Coverage

Hi ,
Test coverage of 100% across all segments - functions, branches, statements, and lines, doesn’t ensure a 100% uptime SLA. As technology leaders, the rest of the organization looks to us to ensure that the product always works as intended and is performant.

It’s only practical to have a process to evaluate Product Delivery using the same metrics. This is where the DORA metric “Change Failure Rate” helps. It calculates the rate of failure per release. If Release 1 contains 10 tickets and results in 1 bug you’ve got a failure rate of 10%. That’s not good. 

For effective measurement of failure rates, and to combat it we need to

• Identify the failure rate at each stage

  • Measure and reduce the failure rate in each environment - dev, staging, and production. Use automation to report this.

• Derive insights from failure

  • Categorize failures into buckets

  • Create Root Cause Analysis (RCA) Documents

• Not only save for an instance, but the genre of failures

  • Basis the RCA and the bucket use the right type of automation to prevent this genre of failure in the future

Evaluate the impact of the above by quantifying the increase in deployment frequency. Use the table below to evaluate the sprint-on-sprint outcome.

Success Measurement

Here’s a sneak peek into what this looked like for a customer in the healthcare space and the associated business impact.

Improving Stability and Performance in Healthcare

A business in the healthcare space was encountering disruptions in its digital workflow within patient care management, causing delays in treatments and dissatisfaction among patients and healthcare providers.

A combination of static code analysis, unit, integration, e2e, penetration, and load tests were used to reduce the failure rate to a commendable 1.4%, leading to increased stability and performance. The improvements not only streamlined operations but also drove a 14% increase in revenue compared to the last quarter and a 36% jump compared to the same quarter last year.

The transformation from day 0 to day 90

Process

• Github → Jira integration to create an automated formal reporting structure.

• Categorize in pre-defined failure buckets, RCA documents, and tests

In the next edition of LeadReads, we deep-dive into each of the 3 steps and give you the playbook to improve the efficiency of your teams and products.

In the next edition of LeadReads, we deep-dive into each of the 3 steps and give you the playbook to improve the efficiency of the teams and products.

Until next time, stay curious and keep building better.

Best,

Mac.

Want to reduce Go-Live anxiety? Application Modernisation is the answer.

If you want to reduce downtime to Zero with an easy rollback mechanism

OR Increase visibility into system performance, bottlenecks, user journeys & patterns

OR Reduce the impact of unknowns, holler back to this email today to embark on a worry-free Go Live journey!