Towards Operational Excellence
summary
Defines Operational Excellence as three concrete pillars—culture, tools, processes—and shows what changed at Amazon: teams become Two Pizza Team owners who build, deploy and operate; build system Brazil, deployer Apollo and workflow Pipeline cut a 16‑day checkin‑to‑prod time and one pilot achieves a 90% reduction; by 2018 the org ships hundreds of millions of deployments a year; mechanisms include an Andon cord style customer‑service stop, a Correction of Errors process and a Policy Engine that codifies fixes and enforces continuous improvement.
AI-written summary · about
chapters (37)
- 0:00Introduction
- 0:30Operational Excellence
- 1:01Early Amazon Systems
- 2:02Service Oriented Architecture
- 3:01Operational Excellence Definition
- 4:20What does a technology organization
- 4:40Culture
- 6:58Innovation
- 7:38Customer Feedback
- 8:35Ownership
- 10:41DevOps Tools
- 11:16Amazon
- 13:40Microservice
- 14:21Conways Law
- 15:16Leadership Principles
- 17:15Running Build Comments
- 17:51Apollo
- 19:06Pipeline
- 22:35AWS Codestar
- 22:58Processes
- 25:37Good Intention
- 26:14Mechanism
- 26:32Toyota
- 28:03Un undone cord
- 29:32The critical part
- 30:06The scratch table story
- 30:31Stop the line
- 30:46Amazon Automatic
- 31:37Where to go
- 32:08Mechanisms
- 32:57Corrections of Errors
- 35:04COE Leadership Principles
- 36:09Continuous Inspection
- 37:05Service Metric
- 37:31CoE Process
- 38:10Policy Engine
- 39:32Conclusion
related talks
44mThe Amazon Software Development Process
21mDevOps Culture at Amazon
43mThe Amazon Software Development Process
17mBeyond DevOps – Holistic transformations in uncertain times
51mSelling DevOps
47mWhy We Need DevOps Now: A Fourteen Year Study Of High Performing IT Organizations
31mDevOps in the Cloud: Case Studies of Amazon.com teams and their resilient architectures
27mDevOps in the Cloud
