3 ms·
Nice at a high level but I have some gripes about the details: 1. It says "asynchronous communication" is categorically a cause of ineffective communication, b
by civilized 5y ago
Nice at a high level but I have some gripes about the details:
1. It says "asynchronous communication" is categorically a cause of ineffective communication, but only "inefficient" meetings are a cause of ineffective communication. Glaring old-fogey double standard.
2. I was curious what "backlog inversion" is and found a definition here: http://sedano.org/software-development-wastes/mismanaging-the-backlog.html http://sedano.org/software-development-wastes/mismanaging-th.... Apparently it's when you work on things that haven't been prioritized. No idea why they thought the name "backlog inversion", reminiscent of obscure OOP jargon, made sense, but real phenomenon no doubt.
- Jtsummers 5y agoHaven't been prioritized recently, not "not prioritized". A big difference. The inversion is (I think it's a strange use, but understand it) that people will work on something that looks like it's high priority (because it's marked that way) when it's low priority or deprecated.
- civilized 5y agoThanks, I get it now. I think "stale priorities" would be a lot clearer for about the same number of syllables and characters.