2 ms·
I regularly see companies work at full capacity and fall apart because of this. When an individual or team is at full capacity (overscheduled), they tend to do
by muzani 7y ago
I regularly see companies work at full capacity and fall apart because of this. When an individual or team is at full capacity (overscheduled), they tend to do things for the sake of buying time instead of actually trying to solve a problem.
For example, someone might send an API that has a minor bug or even purposely add a typo instead of a proper fix. A front end engineer would have to actually use the API, spend a few hours scratching their heads on why it isn't working and whether it's their fault, before contacting the API maintainer on it.
I liken it to traffic congestion. It works fine when you scale something up to around 50% capacity. But nearing 70% capacity, things start to slow down, and at about 90% capacity, you get total gridlock.
- kbouck 7y agoMartin Thompson talks about this in several of his talks. The same queuing theory that applies to software should also apply to dev teams - that service response time (or I guess delivery of features) slows down exponentially, not linearly, as utilization increases beyond a critical threshold (70% ?). He explains this at around 5m25s in this talk [1] - another point relevant to this thread at 9m30s. Some dev teams could be better at applying back pressure in their processes to avoid inundating themselves with too-high utilization and falling into exponential team slow down. [1] https://youtu.be/03GsLxVdVzU https://youtu.be/03GsLxVdVzU [2] https://mechanical-sympathy.blogspot.com/2012/05/apply-back-pressure-when-overloaded.html?m=1 https://mechanical-sympathy.blogspot.com/2012/05/apply-back-...