Effective DevOps for Organizations
summary
Explains that DevOps succeeds when teams focus on measurable outcomes not just CI/CD — high performers deploy ~2,500× more often, have far fewer change failures and recover ~7× faster. Recommends feature flags for gradual rollouts (example: new GitHub Projects used by large customers for months behind flags), insists on self-sufficient cross-functional feature teams, developers on call, hypothesis-driven development, and blameless retrospectives; warns that automation often gets harder before it gets reliably faster.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:35Damian Brady Introduction
- 2:58DevOps Definition
- 9:23DevOps Diagram
- 11:53CICD
- 16:29DevOps Fundamentals
- 17:13Dr Nicole Forsgren
- 17:57DevOps literature
- 20:44Locality and simplicity
- 26:26Crossfunctional feature teams
- 30:29Avoiding Silos
- 32:19Customer Focus
- 34:39Customer Success
- 35:02Feedback
- 42:03Psychological Safety
- 45:14Blameless retrospectives
related talks
34mDevOps: Next
27mDevOps Next
47mWhy We Need DevOps Now: A Fourteen Year Study Of High Performing IT Organizations
47mOvercoming Obstacles to DevOps
45mDevOps: The Key to IT Performance
01h 02mWe have DevOps. No one was fired. But what to do?!
01h 00mDevOps – Value at Speed
31mThe Data Behind DevOps: What Does It Take To...
