Deploy or
die

— Scroll to explore

Engineering culture
lies upstream of agility

In short

Reduce risks, validate assumptions and increase value by deploying as early and as often as you can.

In short

Reduce risks, validate assumptions and increase value by deploying as early and as often as you can.

Agility

The seminal book "Accelerate" analyzes IT practices to see how they relate to business performance. The author's conclusions may seem counterintuitive for those who haven't seen it in action: speed and quality can go
hand in hand.

Deploy frequency
Agility

Deploy
frequency

This is a proxy metric for batch size. Shipping in small batches correlates with a high frequency of interacting with users and the market. It also decreases the risk associated with a release.

Cycle time
Deploy frequency

Cycle time

The time it takes between the start of development and the availability of this change to an end-user. Shorter cycle times enable faster feedback loops.

Mean time to restore
Cycle time

Mean time
to restore

Failures are a given in complex systems (i.e. where all modern software products live). The best teams are not the ones that avoid failure but the ones that can quickly recover from problems.

Change failure rate
Mean time to restore

Change
failure rate

This measures how many changes to production result
in degraded service or require fixing (patch, rollback, hotfix,…). This criterium is intuitive: the lower the failure rate, the better.

The ITP Way
of working

Gain full insight in how we organise us, as a company, to build better digital products
for bigger futures.

Download

Stay ahead
of the game

Sign up for our newsletter and stay updated on trends, events and inspiring cases.