Now That My Delivery Pipeline Is in Place, What About My Organization?
summary
The talk examines organizational changes needed after setting up an automated delivery pipeline, arguing that tools (IaC, automated provisioning and fast deployment) alone aren’t enough to sustain DevOps. It presents concrete organizational models observed or implemented in companies—how teams, roles and practices were restructured—to reduce delivery failures, ease tensions between developers and ops, and make DevOps transformation durable.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:34Delivery problems
- 9:59Frustration and glass ceiling
- 13:34Conway's law and org
- 22:26Experience models
- 36:48Product org model
- 46:51Summary
- 51:44Culture and strategy
- 53:08Q&A
related talks
41mThe Introduction of DevOps in Large-Scale Organizations
30m3 Practices for Effective DevOps Adoption
05mDelivery-Transformation DevOps-Pipeline
37mWant to do the DevOps? Change Everything
01h 02mWe have DevOps. No one was fired. But what to do?!
10mDevOps Pipeline - Automate Everything
15mDevOps - Future of IT
44mThe Pipeline Driven Organization|
