Effective Eng & Product Teaming
summary
PagerDuty organizes teams own and operate code with shared charters, co‑located PM/UX/engineers, and staffing rules: never less than minimum five people (six preferred) so on‑call rotation is about one in six weeks. Engineering leads can stand in for PMs; PMs prioritize paying down operational load early, which increases velocity. Directors align scope into fungible “genus” groups so merging teams after attrition happens without exec firefights. Executive alignment produces consistent cross-org messaging and enables safe outsourcing to accelerate delivery.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:50Hockey analogy
- 2:40Agile team
- 4:40Support redundancy
- 7:05Org structure
- 10:40Executive alignment
- 15:30Conclusion
related talks
27mScaling Engineering & Product Teams
18mAgents Don't Do Standups: Building the Post-Engineer Engineering Org
33mHow we went from Slipping to Shipping products
16mEngineering the Future with the Reliable Delivery Management
20mQ & A
22mBoosting Team Productivity Across Functions and Roles
34mAn Engineering Team Where Everyone is a Leader
23mManaging diverse engineers for high-impact deliveries