Transforming Traditional Enterprise Software Development Processes
summary
Claims concrete business impact: transforms firmware orgs to cut development cost from >$100M to $55M, raise innovation from 5% to 40% and support 140% more products, aiming for 2–3x development productivity. Implements versioned artifacts/snapshots, gated commits (auto‑revert), page‑object test design and service virtualization, running ~5,000 automated tests daily with a plan to scale to 100,000 automated tests/day. Builds orchestrated, environment‑descriptor deployments and focuses on making trunk production quality so releases stay releasable.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:10Executive resistance to transformation
- 2:32LaserJet firmware case study
- 4:16Executive-led change framework
- 6:45Why Agile fails at scale
- 8:07Macy's CD missteps
- 9:30Versioned artifacts in large systems
- 11:40Sustainable test automation
- 13:46Enterprise constraints as 'horse'
- 15:55Microservices versus tightly coupled architectures
- 17:21Localizing defects in teams
- 19:06Service virtualization for legacy
- 20:53Auto revert and gated commits
- 21:55CD orchestration at scale
- 23:20Database versioning challenges
- 24:45Isolating environment issues
- 25:27Trunk at production quality
- 26:09Executive engagement next steps
related talks
37mLeading the Transformation (Applying Agile & DevOps Principles at Scale)
22mA Healthier Software Development Life Cycle with DevOps
18mAchieving Innovation and Stability for Enterprises
51mSabotaging a Transformation
01h 02mThe Enterprise DevOps Challenge
01h 01mEnterprise Adoption of DevOps
43mAbout to Start Your Nth DevOps Transformation?
38mBuilding a high quality product