Doubling Engineering Productivity at eBay Through DevOps
summary
Claims that doubled engineering productivity for initial pilot teams (holding team size constant) and scales from ~10% to 50% of development work. Uses a Velocity initiative with platform tracks, embedded experts, and the Four Key Metrics (Accelerate/DORA) to measure outcomes. Delivers concrete changes: deployment frequency 5x, lead time 5x, time-to-restore 3x, flow velocity doubling, plus platform work on build/startup times, CI/CD, staging, traffic mirroring, and weekly mobile releases — and reports these changes working in production.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:46Problem statement
- 1:18Why are we here?
- 2:07Assessment
- 6:22Measuring software delivery
- 9:54Measuring eBay
- 12:11Velocity initiative
- 35:05Future
- 36:11Outro
related talks
29mWe doubled engineering productivity at eBay, but couldn't change culture
45mImproving eBay's Development Velocity
51mImproving Ebay's Development Velocity
20mTransforming Software Development and Engineering Velocity at EBay With AI/ML in C...
42mBuilding a Strong Engineering Culture – Stacy Devino
10mAchieving engineering velocity by optimising developer experience
35m"DevOps Reframed: Embracing the Path to Developer Productivity Engineering"
45m"Moving Fast at Scale"