How Adobe Scaled DevOps in the Enterprise
summary
Adobe and PwC describe how Adobe restructured its operating model to support a shift from boxed products to subscription digital services, focusing on adopting DevOps across a large enterprise. They cover concrete strategies and tactics for enabling faster, higher-quality delivery—addressing leadership, organizational design, culture change, and metrics—presented through case examples and a panel discussion.
AI-written summary · about
chapters (31)
- 0:00Introduction
- 0:30Agenda
- 4:45How to drive time to market
- 5:53Not a one size fits all model
- 6:29Tony Vanwinkle
- 8:00About Adobe
- 9:31Adobes SaaS transition
- 11:46Midlife crisis
- 21:18How does your team interact with the broader Adobe
- 21:46How do you expose your teams charters
- 23:55Learning from failures
- 24:33Blameless postmortem
- 25:24Changing mindset
- 26:35Blameless model
- 28:53Service management principles
- 30:53Lean it out
- 31:22DevOps vs Enterprise Applications
- 33:27Key architectural principles
- 35:16Quality security compliance
- 35:37Quality at the source
- 36:41Salesforce integration
- 37:31Convergence of trends
- 37:55Measuring success
- 38:14Investments in DevOps
- 40:29Leadership and DevOps
- 41:25Organizational Change Management
- 41:35Investment in Organizational Change
- 45:06Key to Success
- 45:56Technical Debt
- 47:58Language
- 48:58Challenges
related talks
13mKeynote: Adobe’s Internal Developer Platform Journey and Lessons
40mFrom Debt to Wealth: Transforming Observability at Adobe
51mBuilding an Enterprise-scale DevSecOps Infrastructure: Lessons Learned
37mLeading the Transformation (Applying Agile & DevOps Principles at Scale)
30mHow did we create a culture of ownership and accountability at Adobe?
17mBeyond DevOps – Holistic transformations in uncertain times
18mScaling DevOps in Complex Environments: Challenges, Failures, and Successes
30mDiscover How to Improve Productivity by Going DevOps and SAFe