Blind Agile

I want to propose a new term - "Blind Agile" - when only one side (business or dev) is practicing Agile, but the other side is not delivering their part, but the project keeps going until they hit eventual disaster.

Agile should be practiced with eyes wide open. If at each iteration, you see that the other side is not keeping its commitments, time to disengage.

Or switch to a more document-heavy, signoff-heavy approach, such that when the blame game starts, the side doing their part has the evidence to show that the other side wasn't.

I'd like to emphasize that either side can be to blame for the failure of an Agile project - either the dev team isn't able to deliver potentially shippable increments at every sprint, or the business people aren't spending the time and energy to drive the project.