You are signed in. Close

You are signed out. Close

Thank you. Your subscription has started. Close

Thank you. You will get an email when a new comic comes out. Close

We could not confirm your payment. If you paid, use the link "Sign in" at the bottom of the page. Close

Something went wrong on our side. Please try again in a moment. Close

Previous episode Rollback: how to undo a bad deploy in minutes

How CI/CD works: why releasing code every day is safer than once a month

DORA metrics: why teams that deploy more often break less

Many people believe that a software team which deploys more often must break things more often. More than ten years of research, with tens of thousands of people in software teams, found the opposite. What the researchers measured, and why deploying often and breaking little go together.

  1. 1 Rono's worry is an old idea: a team must choose between speed and safety, so more deploys must mean more broken deploys.Ronospeedsafety

    Rono's worry is an old idea: a team must choose between speed and safety, so more deploys must mean more broken deploys.

  2. 2 Since 2014, a research group called DORA has asked people in software teams, almost every year, how they work and what happens to their changes.DORAa researchersurveys2014 totoday

    Since 2014, a research group called DORA has asked people in software teams, almost every year, how they work and what happens to their changes.

The rest of this episode is for subscribers

Subscribe to read every premium episode. You can cancel when you want.

Paid yearly: $99 instead of $119.88

You finished the comic Back to the comic

Share this comic

More comics