Why is it important to measure operability? What should the trailing indicators and leading indicators of operability? In this article Steve Smith looks at system-level measures of operability that can be aligned with organisational goals This is part 2 of the Build Operability In series Introduction In How To Measure Anything, Douglas Hubbard states organisations…
What is operability, how does it promote resilience, and how does building operability into your services drive Continuous Delivery adoption?
In this series, Steve Smith explains what operability is, how to design Service Level Objectives, how to measure leading and trailing indicators of operability, and why Build It Run It matters so much to Continuous Delivery as well as operability
How can Multi-Demand Operations eliminate handoffs and adhere to ITIL?
In this article, Steve Smith explains why Service Transition, Change Management, and Production Support phases are inimical to Continuous Delivery, and how such Policy Rules can be turned into ITIL-compliant Policy Guidelines that increase flow
How can Multi-Demand Architecture accelerate reliability and delivery flow?
In this article, Steve Smith explains why Policy Rules should be based on Continuous Delivery predictors, the importance of a loosely-coupled architecture, and how architectural Policy Rules can benefit Continuous Delivery and reliability
Why does optimising for MTBF leave organisations in a state of Discontinuous Delivery, and vulnerable to failure? How does optimising for MTTR improve reliability, and how can it encourage the adoption of Continuous Delivery?
In this article Steve Smith explains why Discontinuous Delivery is part of the tradition of optimising for robustness in IT, and how optimising for resilience can power Continuous Delivery adoption.
What does it mean to optimise for resilience? Why is resilience so valuable to an organisation, and how can operability contribute towards it?
In this article Steve Smith explains what optimising for resilience is, and why it is so valuable to IT delivery.
Why is it wrong to assume failures are preventable in IT? Why does optimising for robustness leave organisations ill-equipped to deal with failure, and what are the usual outcomes?
In this article Steve Smith explains why a production environment is always in a state of failure, why optimising for robustness results in a brittle failure response process, and why Dual Value Streams are a common countermeasure to failure.
Why do so many organisations optimise their delivery of IT services for robustness? What risk management practices are normally involved, and do their risk reduction capabilities outweigh their costs?
In this article Steve Smith explains what optimising for robustness is, and why it is inadequate for IT service delivery. This is part of the Resilience As A Continuous Delivery Enabler series.
The DevOps Handbook describes an admirable DevOps As A Philosophy based on flow, feedback, continual learning and experimentation. However, a near-decade of naivety, confusion, and profiteering surrounding DevOps has left the IT industry with DevOps As A Cult and the benefits of Operability are all too often overlooked.
In this article Steve Smith explains why DevOps As A Philosophy is a laudable ideal, why DevOps As A Cult is the unpleasant reality, and why organisations should instead focus on Operability as an enabler of Continuous Delivery.