Improving Ebay's Development Velocity – Randy Shoup

Automation

Here is the rewritten meta description: "Improve development velocity at eBay through collaboration, instrumentation, and automating workflows. Learn how the company achieved faster builds, more frequent releases, and reduced lead times."

Key takeaways

Improving development velocity requires collaboration and focus on reducing impediments.
Value stream mapping was used to assess the development process and identify opportunities for improvement.
Instrumenting the process and providing data-driven insights helped teams focus on making improvements.
The importance of communication was emphasized, with daily leadership stand-ups and regular meetings.
A focus on upgrading dependencies and automating workflows was key to improving development velocity.
Improvements in build time, release frequency, and lead time were made through the program, with the program’s most skeptical members eventually embracing the changes.
Collaboration with other teams was crucial, with a focus on removing impediments and improving instrumentation.
Key metrics included deployment frequency, lead time, and change failure rate, with efforts to reduce manual testing and improve code reviews.
The importance of celebrating successes and recognizing the efforts of individual teams was emphasized.
Some applications were manually tested, while others used automation.
The company’s 27 years of experience and 4500 applications meant that not all were fully instrumented or automated.
Improvements in deployment frequency and lead time were achieved, with weekly mobile releases and increased iteration speed.
Automating deployments and streamlining the testing process were key to improving velocity.
Cross-functional leadership was crucial in driving improvements.
The company’s size and age meant that some applications were not fully automated, but still improved in terms of velocity.
Improvements in build time, deployment frequency, and lead time were made, with a focus on reducing manual testing and improving code reviews.
The importance of collaboration and instrumentation was emphasized, with a focus on removing impediments and improving development velocity.
Regular team demos and sharing of tools and learnings were encouraged.
Some teams had manual code review policies, while others automated testing and code reviews.
The importance of experimentation and learning was emphasized, with a focus on driving improvements in development velocity.
Bi-weekly releases and weekly mobile releases were achieved, with increased iteration speed and improved velocity.
Automating deployments and streamlining the testing process were key to improving velocity.
Improvements in lead time and change failure rate were made, with a focus on reducing manual testing and improving code reviews.
A focus on upgrading dependencies and automating workflows was key to improving development velocity.
Quarterly goals were set, with a focus on improving development velocity and reducing impediments.
A focus on making improvements and building tools was essential, with a focus on driving fun and motivation.
Cross-functional leadership was crucial in driving improvements.
A focus on criticizing and addressing areas for improvement was crucial, with a focus on driving improvements in development velocity.
Improvements in deployment frequency, lead time, and change failure rate were made, with a focus on reducing manual testing and improving code reviews.
The importance of instrumentation and collaboration was emphasized, with a focus on removing impediments and improving development velocity.
Quarterly benchmarks were set, with a focus on improving development velocity and reducing impediments.
The importance of celebrating successes and recognizing the efforts of individual teams was emphasized.
Improvements in deployment frequency and lead time were made, with a focus on reducing manual testing and improving code reviews.
The company’s 27 years of experience and 4500 applications meant that not all were fully instrumented or automated.
Improvements in build time and deployment frequency were made, with a focus on reducing manual testing and improving code reviews.
Automation of deployments and streamlining of the testing process were key to improving velocity.
Regular team demos and sharing of tools and learnings were encouraged.
A focus on making improvements and building tools was essential, with a focus on driving fun and motivation.
Core topic areas for improvement included: • Improving development velocity • Reducing impediments • Improving instrumentation and collaboration • Reducing manual testing and improving code reviews • Automating deployments and streamlining the testing process

Improving Ebay's Development Velocity – Randy Shoup

More talks