Ask HN: What is the bus factor at your company?

26 points by guessmyname ↗ HN

20 comments

[ 2.0 ms ] story [ 1148 ms ] thread
The what now?
The amount of people a bus would have to take out before a project/company etc can no longer get work done.
https://en.wikipedia.org/wiki/Bus_factor

"The bus factor is a measurement of the risk resulting from information and capabilities not being shared among team members. It is also known as the lottery factor, truck factor, bus/truck number or lorry factor".

Right? We called it the Mack Truck Factor back in the day.
We call it the lottery factor to try and put a more positive spin on it.
(comment deleted)
Disturbingly high for the size of the company. I can point to several locations where one person is pivotal to core business functions and causes issues when they go on vacation.
Wouldn't that be a disturbingly low bus factor?
Apparently yes, wasn't sure the scale :)
Same here, plenty of areas with a bus factor of one. Even worse, one of the critical persons is over 70 - incredibly sharp, healthy and keeps up to date, I hope to reach her age with those skills, but her age makes a health problem more likely.

That said, her irreplaceability is more due to stupid security setup (she's the only one that has all the necessary privileges), so I guess she could be replaced eventually after some hiccups (and at a big hit to productivity).

I've worked at maybe two companies with a bus factor > 1. Maybe.
I have a feeling people will be biased into thinking their bus factor is lower than it really is.

Day to day experience may make it seem like if John or Jane got hit by a bus, nothing can happen.

In reality businesses adapt and there are probably other people that can step in. Once they must, they will.

I'm sure the business could adapt to our low bus factor, but it would take months at least of nothing really happening, there is really only one person that knows some of the critical codebases and they're so spaghettified that I'm not sure if anyone else could learn it.
Probably 2 or higher at this point. We've made some real strides recently in getting everything documented somewhere.
3 and increasing as new technical team lead keeps optimising for short term results and his own career development. I am not voicing much criticism as part of me wants him to fail even if it ends up hurting the product but I suspect he will leave us before the shit hits the fan.