Bootstrapping an SRE Team:
summary
Combines two separate DevOps teams for Vets.gov and Caseflow into one shared SRE org that standardizes tooling (Prometheus and Grafana, Sentry, Travis/Jenkins, Terraform + Ansible, Kubernetes, GitHub, AWS GovCloud) and on-call rotations, cuts downtime to about 2 minutes per week, runs roughly 40 prod deploys/month (≈600 across environments), and has already processed 327,923 veterans through a rebuilt health-care flow; describes rolling rotations, blameless postmortems, packaged playbooks, and face‑to‑face migrations for hundreds of VA apps.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:28Digital Service to Start
- 4:58Where are we now
- 5:50What do we do
- 6:34DevOps
- 7:16SRE Team
- 8:42Goals
- 11:37The VA
- 15:34Lessons Learned
- 24:20Digital Service Values
- 24:49Create Momentum
- 26:19Hire Empower Great People
- 28:32Find the Truth to Tell the Truth
- 30:24Going Where the Work is
- 32:03Why Care
- 33:14Conclusion
- 34:14QA
related talks
23mSite Reliability Evangelism: Practice Start-up within an Established...
18mSRE Engagement Model Transition in Building and Expanding SRE Team
20m5 Agile practices every SRE team should adopt
21mMove to Integrated SRE Ops at a Retail organization
30mThe Path to SRE
38mThe Smallest Possible SRE Team
27mMean Time To SRE: A DevOps story from adidas
42mDemystifying SRE and DevOps