Organising a fast growing DevOps team a real life use case
summary
Company grows 20→120 employees and DevOps expands 2→15 people; central platform team and offshore Ops are replaced by local hires and embedded DevOps per product team so each squad gets one full‑time DevOps. Infrastructure work standardizes on Terraform for production changes, introduces SRE, DB admin and security roles, and retires ad‑hoc prod credentials. Scrum rituals fail at scale so ticketing and weekly cross‑team demos replace daily all‑hands; outcome is fewer firefights and clearer ownership, but timezone handoffs remain unresolved.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:50Company growth context
- 3:57DevOps team evolution
- 6:28Emergency team organization
- 8:57Clear roles and boundaries
- 10:21Key DevOps roles
- 12:10Methodology challenges
- 14:19Site reliability engineer impact
- 15:43Bureaucracy bottlenecks
- 16:50Hybrid DevOps model
- 18:59Documentation strategy
- 20:43Conclusion and key takeaways
related talks
52mDevops @Scale
36mDevOpsSup - Extended DevOps approach
18mScaling DevOps in Complex Environments: Challenges, Failures, and Successes
48mDevops@Scale
58mDevOps @ Scale — Greek Tragedy in Three Acts
56m14 years of #devops, but what did we really learn
45mFrom 5 to 100 in Product Development team in just 5 years
28mDevOps in the Enterprise: A Transformation Journey