Enabling & practicing continuous integration & testing iv. Automating, enabling, and architecting for low-risk releases b. Integrating objectives of QA & Operations to improve outcomes 2. Ch. 9 – Create stability, and even higher job satisfaction and lower rates of burnout. 5. Ch. 12 Automate and Enable Low-Risk Releases a. Just like we reduce batch size and increase frequency of feedback during development State of DevOps Report – high performers had deployment lead times measured in minutes or hours; low performers had deployment lead times measured in months. g. DECOUPLE DEPLOYMENTS FROM RELEASES i

complicated processes.” iv. 2015 State of DevOps Report – high performers had MTTR 168x faster than low performers b. CREATE OUR CENTRALIZED TELEMETRY INFRASTRUCTURE i. Remove the silos of information due to testing failure – seems valid since better testing practices could have mitigated iii. In low-trust, command & control cultures, change control often results in worse outcomes d. POTENTIAL DANGERS

deployment pipeline demonstrates that changes can be low risk and pre-approved. ii. Use previous metrics to demonstrate high success rates and low MTTR iii. Link and provide traceability from planning

The Third Way: The Principles of Continual Learning and Experimentation 37 i. culture of fear and low trust 1. workers who make mistakes are punished 2. those who make suggestions or point out problems

the code can be developed in a user-centric way and match the enterprise’s needs precisely. Risk is low, because the team is constantly adjusting.  Option 2: Compare that to the risk of buying a vendor’s