Leading Changes in DevOps Organizations
summary
Practical, concrete outcomes: a legacy rollout that required two people working six months every 2–3 years becomes manageable by one person in half an hour after adopting Docker and microservices; the target cadence moves toward one deployment per day; security objections get answered with kernel/feature-level explanations and measurable risk estimates; start with tiny wins like compress images for a tenfold speedup, show saved hours and dollars, and build a cross-functional group that actually implements and maintains the changes.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:53Scrum Meetings
- 5:50Grouping
- 9:27Vision
- 11:18Obstacles
- 15:00Changes
- 21:22Generating quick wins
- 26:20Dont change your changes
related talks
34mYou only have to change one thing to do the DevOps
54mEffective DevOps for Organizations
49m5 Steps to a DevOps Transformation
34mDevOps: Next
30mAdopting DevOps? You are aiming at the wrong target!
01h 01mEnterprise Adoption of DevOps
18mScaling DevOps in Complex Environments: Challenges, Failures, and Successes
17mBeyond DevOps – Holistic transformations in uncertain times