"It's a false dichotomy typically imagined by those who have never worked on medium to large-sized products" In my experience it's not necessarily false, espec

"It's a false dichotomy typically imagined by those who have never worked on medium to large-sized products" In my experience it's not necessarily false, especially when the test cycle has a weak regression suite. One project I worked on was an embedded system with tight resource management requirements. The teams were split into features and stability/performance scrums. Each new feature would have the performance people crying out loud at the new overheads introduced. A performance/stability-minded code reviewer on each team alongside a strong performance regression test cycle might have seen the project succeed but the pace imposed by a fast agile dev cycle precluded this sort of discipline. Marketing wanted features and wanted them now - The demo is Friday, chop chop! Not a false dichotomy but a manufactured one, perhaps.