Technical Program Management in the SRE world
summary
Argues that Technical Program Managers make SREs deliverable by owning prioritization, risk and metrics, not just meeting notes. Provides concrete data to collect — incident count and severity, on‑call handoffs, planned versus unplanned work, capacity projections — and uses health checks, user surveys and a five‑step fast feedback loop to turn blind spots into tracked actions. Claims TPM-led roadmaps reduce toil, expose tech debt, and raise on‑call quality when teams supply the data.
AI-written summary · about
chapters (9)
- 0:00SRE origins
- 3:58SRE team principles
- 6:03The role of technical program managers in SRE
- 9:34TPMs: what when how
- 12:00TPMs metrics in SRE
- 14:08Blind spots in SRE
- 15:11Feedback loops in SRE
- 16:15SREs with TPMs
- 17:39Planning in SRE
related talks
31mConfessions of an SRE Manager
30mSRE & Product Management: How to Level up Your Team (and Career!) by Thinking like a Product Manager
31mTech Leadership in SRE
28mEvolution of SRE and Rising Need of SRE Catalyzers
13mDifference Between Project & Program Management
25mCapabilities for Building High-performing Technology Teams
35mCare and Feeding of SRE
45mClearing the Way for SRE in the Enterprise