Transform the Invisible Wall
summary
A team resists lift‑and‑shift and defines a business goal instead, automates with Ansible, builds an automation roadmap (red/yellow/green) and adds nightly infrastructure regression tests; 8 upstream groups become 8 teams involved then consolidate into cross‑functional end‑to‑end teams through three reorganizations. Infrastructure provisioning drops from 4–6 weeks to 4 hours provisioning, 90% of deployments finish in under ten minutes, and chaos‑monkey style resilience and a devops skill matrix surface remaining blockers: root/access ownership, compliance and who owns VPCs.
AI-written summary · about
chapters (11)
- 0:00Start
- 3:41CONTEXT
- 4:54WHAT IS DEVOPS?
- 8:16WHY TO ADOPT DEVOPS??
- 9:11BUILD YOUR HOUSE OF DEVOPS IN FOUR STEPS
- 9:54The journey - Discover the business value
- 15:30Invisible - Foxed mindset vs. Growth Mindset
- 17:32DEVELOP ORGANIZATIONAL GROWTH MINDSET
- 20:33The journey-Pillar of Principle
- 28:08The journey-pillar of Practices
- 31:57THE JOURNEY - BUSINESS VALUE
related talks
13mNavigating the infrastructure skills gap for DevOps teams
01h 02mTools and Techniques for Infrastructure as Code
43mAbout to Start Your Nth DevOps Transformation?
31mDevOps in Infrastructure — When It's Mostly Ops...
27mCase Study: Re-Thinking Our Infrastructure Tooling
23mA Journey to Automated Infrastructure
05mReady, Set, DevOps Roadblock
17mBeyond DevOps – Holistic transformations in uncertain times