Coordination
summary
Empirical work at Ohio State maps how continuous deployment, tool reliance (Slack/chatops), and third‑party dependencies create constant, hard‑to‑anticipate failures; the lab demos lightweight representations for post‑mortems and coordination breakdown analysis used to surface hidden constraints during outages. Practical coverage includes paging flows, vendor conference calls, and how teams rebuild predictability, maintain common ground, and enforce directability so that coordination repeatedly protects reliability rather than relying on heroic fixes.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 2:09Challenges in DevOps environments
- 8:01Myth of the fully functioning system
- 19:30Coordination in complex systems
- 22:51Coordination in DevOps teams
- 32:10Why coordination matters now
- 32:55Summary and Q&A
related talks
04mLoosing Control and Being OK With It
28mBuilding Resilient DevOps Pipelines: Strategies for Handling Unexpected Failures &...
02mOpening Remarks
01h 39mPostOps: A Non-Surgical Tale of Software, Fragility, and Reliability
49mDevOps Ten Years After: Review of a Failure with John Allspaw and Paul Hammond
50mDevOps Project Failures - Lessons Learned and Strategies for Recovery
26mMission Critical Mindset Building a Culture of Resilience in DevOps Teams
16mEngineering Failure-Resilient Systems