Bus Factor: What If You Could Calmly Get Hit by a Bus?
summary
Defines bus factor as the minimum number of people who must remain to keep a topic alive, shows how to measure it per topic using a simple competency matrix, and reports a practical experiment where experts step back for 2–3 days of shadowing to reveal undocumented steps. Recommends centralizing documentation, automating deployments, pairing and rotating roles, and short trainings to increase resilience, share accountability, and reduce single points of failure.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 3:53Bus factor defined
- 10:30Bus factor awareness
- 18:33Knowledge capitalization
- 25:11Skill sharing practices
- 33:35Summary
- 35:44Q&A
related talks
44mPressing questions in Product Management
21mProductivity Hacks for Busy Engineers
33mIt's Dangerous To Go Alone! Take This Team
12mTackling team dysfunctions with Mob programming -
40mThe Coaching Leader & Architect
50mSafe Landings: Self-care In A High Intensity Technological World
28mHow Bad Is Your Toil?: Measuring the Human Impact of Process
46mManaging the Burnout Burndown