"Why would anyone do out-of-hours support for free?"

A288fb976fc633cde90a2bc19bf2b5a6?s=47 Sarah Wells
September 19, 2016

"Why would anyone do out-of-hours support for free?"

To successfully move to DevOps, you will need to change your company's culture in a lot of ways. If you have people in very distinct operations and development teams, how do you convince them about the benefits of closer collaboration and blurring of lines?

Why would operations let developers have production access? If it resulted in better monitored, better documented, more stable and resilient systems, maybe they'll accept the perceived extra risk.

Why would a developer accept being woken up at 2 am for no more money? If it means having the power to make more decisions about the tools, processes and software to use, maybe they'll be fine with that.

Over the last few years at the Financial Times, we've gone through this culture change, and I'm happy to share some of the problems we've faced and the solutions we've tried.


Sarah Wells

September 19, 2016


  1. 1.

    "Why would anyone do out- of-hours support for free?" Sarah

    Wells Principal Engineer, Financial Times @sarahjwells
  2. 8.
  3. 20.
  4. 26.
  5. 30.
  6. 37.
  7. 38.
  8. 47.
  9. 51.
  10. 52.
  11. 55.
  12. 56.
  13. 66.

    @sarahjwells –http://matt.chadburn.co.uk/notes/teams-as-services.html “the choice to decide who is going to

    provide a service is typically around ease of use (for the team), readiness, and self-sufficiency, rather than the being too concerned about the politics of vertical integration across the company”
  14. 68.
  15. 75.
  16. 86.
  17. 87.
  18. 88.