Let's phrase it differently: agile causes two teams to desync. If for whatever reason to teams become siloed and are agile: if their sprints don't line up, the

Let's phrase it differently: agile causes two teams to desync. If for whatever reason to teams become siloed and are agile: if their sprints don't line up, then requirement thrashing causes agile hell. A needs Y B is working on X Given timelines: B must quickly switch to Y or A must implement it without support from B. The biggest problem I have with software development is coordinating 100 TEAMs to operate on the same page (I own a library of interesting and old functionality at my company). This happens on occasion, without someone to reign in affected parties: things rot faster from be features than can be managed