Couples Therapy for DevOps and ITIL
summary
Argues that ITIL processes remain essential but must be aligned with DevOps: build a common taxonomy, break monolithic processes into micro processes for microservices, and use models to gate rigor by risk. Recommends making change management agile — auto-populate CMDBs from CI/CD, use code as change record, and accept peer approvals. Notes tool realities (GitHub, ServiceNow, JIRA, Puppet/Chef/Ansible) and cites examples like pipelines with ~90 APIs; claims automation often improves governance and that SREs split time 50/50 SRE time between ops and engineering.
AI-written summary · about
chapters (6)
- 0:00Start
- 3:06The Tech World Has Changed since the last ITIL Update
- 9:04So Where's The Disconnect?
- 14:42Cut Down on Over Processing
- 22:33Share Your Toys
- 29:32Remember: We Are All Part of the Same Ecosystem
related talks
45mMarried to DevOps
37mDevOps and Its Integration with ITSM
29mITIL and DevOps Can Be Friends
26mNew paradigms: Calibrating the migration from ITIL to DevOps
29mAn Unlikely Happy Couple - DevOps and IT Audit?
15mDevOps - Future of IT
34mDevOps Transformation from the C-Level point of view
20mDevOps and ITSM
