How can You Build It You Run It At Scale be implemented? How can support costs be balanced with operational incentives, to ensure multiple teams can benefit from Continuous Delivery and operability at scale?
In this article Steve Smith looks at why mixing You Build It You Run It with You Build It Ops Run It is ineffective, and offers a production support model that minimises support costs while maximising operational incentives and Continuous Delivery potential
Why does Operations production support become less effective as Delivery teams and applications increase in scale? How can You Build It You Run It be applied to 10+ teams and applications without an overwhelming support cost? How can operability incentives be preserved for so many teams?
In this article Steve Smith looks at why You Build It Ops Run It At Scale struggles so badly, and how You Build It You Run It At Scale can be designed to balance operability incentives with support costs
Why is it important to measure operability? What should be the trailing indicators and leading indicators of operability?
In this article Steve Smith explains what an availability target it is, and how to use Cost Of Delay to prioritise availability targets with a balance between product needs and operational features
Why do disparate Delivery and Operations teams result in long-term Discontinuous Delivery of inoperable applications? Why is it important to balance support cost effectiveness with operability incentives? What is You Build It You Run It, and why does it have such a positive impact on operability?
In this article Steve Smith looks at the traditional support model of You Build It Ops Run It, and how its modern equivalent You Build It You Run It powers Continuous Delivery and application operability
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 3 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.