Speaking about Run Book Collaboration – DevOps Summit, Amsterdam

I will be speaking about Run Book Collaboration at the DevOps Summit in Amsterdam in November 2013:

Practical steps for larger organisations to try in order to improve Dev and Ops collaboration, especially via the System Operation Manual (or “Run Book”).

DevOps Summit Amsterdam - logo

Early Bird ticket prices for the event end on October 14th – book with Unicom to secure your place.

Advertisements

Who Owns My Operability?

Operability is not something which can be ‘bolted on’ or retrofitted to software after it goes live; we need to design and build our software with operability as a first-class concern. You don’t build a bridge, then try to add load-bearing capabilities at the end of the project — but most software projects try to do exactly that, typically with costly results.

Ultimately, the product owner should be responsible for ensuring that operational requirements are prioritized alongside end-user features. If you are responsible for the software product or service, there is only one answer to the question

Who Owns My Operability?

Who Owns My Operability?

Update: the site now shows selected recommended reading on each page load.

(With a nod to whoownsmyavailability.com)