Sometimes you get into a scenario where a software team is iterating quickly and delivering lots of software. Over time, failure to do housework and paying off technical debt leads to productivity going down.
They eventually approach a point where all the resources of team are used up in overcoming the accumulated cruft just to deliver simple changes.
This appears to be a tipping point in technical debt. An associate referred to it as the agile iterative cliff - but that doesn't register on Google.
My question is: What is the standard terminology for the scenario of the agile iterative cliff?