Suzanne Livingston at LeadDev West Coast 2023
summary
IBM’s Maximo product moves a 300‑developer org from long release cycles to continuous delivery by aligning 25 squads on a tight priority list, opening backlogs, and forcing joint ownership of stories. Engineers build CI/CD pipelines for on‑prem and SaaS, cutting issue lead time from ~25 to ~5 days, reducing toil by up to 50% and security findings by ~80%. Costs fall after fixing 80% infra overallocation. Key artifacts: Maximo, 25 squads, 40% keep‑the‑lights‑on.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:05Zero waste engineering
- 3:13IBM engineering history
- 5:22Maximo challenges
- 8:14Fixing release process
- 11:20Aligning product teams
- 13:49Improving requirements
- 16:57Automation to reduce waste
- 20:09Continuous engineering mindset
- 23:23Visibility and resources
- 25:11Cost and waste reduction
- 25:57Closing and Q&A
related talks
34mDevOps and Innovation at USAA and IBM
43mThe Road to DevOps
37mLeading the Transformation (Applying Agile & DevOps Principles at Scale)
01h 03mBeyond the innovator’s dilemma
30mHow a Business Exec Led Agile, Lead, CI/CD
23mBackbone of the Swiss Financial Center Goes DevOps
01h 02mSurviving the Innovators Dilemma
25mYou Can’t Stop the Music! Neither the Devops!