Doubling Engineering Productivity at eBay Through DevOps • Randy Shoup • YOW! 2022

Interesting. speech Randy ShoupVP of Engineering and Chief Architect at Ebay, which is responsible for platform teams. Randy talks about how 2 During the year, the Ebay engineering team, which consists of 4K engineers, learned to work twice as efficiently. To summarize, there were no secret components to this transformation:

• The company was in ~~well her~~ It's a bad development situation and Randy's here to change it.
• They drew a product lifecyle. (plan -> development -> delivery -> post-release iteration) We focused on the parts about deployment and delivery, trying to speed up the changes and reduce their cost. Next, they started measuring DORA metrics for every important service. (lead time, release frequency, mttr after unsuccessful releases, rate of unsuccessful releases). Here the author recalls the book "Accelerate". (I have a review of it in three parts: 1, 2, 3) It provides data on how the average situation for DORA metrics in eBay and compared to the industry benchmark.
• Then they conducted a survey of product developers in the style of "If you had to release conditionally daily, what would interfere with such a frequency of releases" - this set of problems became a backlog for platform teams. Here the author recalls the book "Team Topologies". (Teams as means of Delivery, Team Topologies that work for flow, Evolving team interactions for innovation and rapid delivery.) Next, the author explains what the transformation looked like and what product and platform teams did to double productivity. (How to focus on pilot teams and systems so as not to blur the focus, how to divide the results little by little, but to improve the overall situation, improve the development processes and redesign critical parts of the systems) Next, the author talks about the joint cooperative tracks of the platform teams movement (measuring velocity, improving builds, local tests, CI, staging, mirroring traffic, automation deployment, trainings and workshops for engineers), as well as product teams (The author shows how teams from different domains were involved in the transformation.)

Interestingly, the guys chased the acceleration of development, and as a result received higher productivity of development teams and better reliability of services. This is in line with what the Accelerate authors argued — they pointed out that unlike the old development approach, where you had to choose between stability and speed, in a new approach with increased adoption of good practices, you get both bundled.

#Engineering #Software #SoftwareEngineering #Architecture #CI #Derlivery #Management #Leadership #Devops