A main tenet of DevOps is bridging the gap between the Dev team and the Ops team. One way to accomplish this is to include devs in the on-call rotation. While this may sound difficult, it’s not impossible to do…as our guide demonstrates. We profile four companies that have successfully transitioned their dev team to being on-call and their stories can provide examples for how you too can do it.

Take a sneak peak of the report below.

According to Ernest Mueller, one of the authors of the Agile Admin:

DevOps is the practice of operations and development engineers participating together in the entire service lifecycle, from design through the development process to production support. DevOps means breaking down the traditional silos that have existed between Ops and Devs. DevOps Practices -Specific techniques used as part of implementing the above concepts and processes.

p4-icon-gear Continuous integration and continuous deployment
p4-icon-pager “Give your developers a pager and put them on-call”
p4-icon-triangles Using Configuration management, metrics and monitoring schemes
p4-icon-cloud Using virtualization and cloud computing to accelerate change


At Etsy…
“If you are writing code, you are on-call.”

p6-clock Etsy has devs on-call to address the problem of IT Operations asking,
“Why should I be the only person waking up at 3am?”

They empower developers with responsibility:
let them deploy, have them on-call, no passwords, etc.

On-Call Schedules

Dev On-Call


“Make sure that developers stick around to ensure that their deploy worked.”



How to get started

What if you’re not Etsy and you want to get buy-in from your devs… is there a way to make it easier for devs to be included in the on-call process?

Download the PDF to see how these 4 companies did it…