How to make an ops team get along with N development teams
summary
A Web department at 2GIS supporting five development teams and 20+ projects faced daily releases and constant changes, which initially made operations a bottleneck of overworked sysadmins. The talk explains how they transformed that situation into an infrastructure-engineering team that provides services to development teams, describing the differences between the two models, the steps taken to reach the new model, and why it reduced stress.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 8:39Team collaboration issues
- 17:58Process standardization
- 27:16Technical review process
- 35:09Results and outcomes
related talks
32mDevOps at Ordnance Survey: Turning the Dinosaur Into a Unicorn
24mWar Stories About the Ops in DevOps
25mHow to Be an Ops in a Dev Team Without Drowning?
58mDevOps Counseling: 10 ways to help your Dev and Ops people love each other
19mDev/Ops relationships, status: It's Complicated
31mDevOps in Infrastructure — When It's Mostly Ops...
40mHow did our DevOps team become another silo?
36mDevOpsSup - Extended DevOps approach
