I guess my main problem with a dependency injection framework would be, why do you need a framework besides a class system and import statements to do dependency injection?
PSA it's not actually cool to seek out safety in numbers. If all of your opinions heavily factor in "what is it safe to think in public," then you are an NPC. You are less cool than people who aren't born to follow.
Agile projects can still fail obviously, but when they do they tend to fail in smaller ways (eg 4 weeks late instead of 6 months late, or almost hit the requirements instead of completely missed). That's a massive win.
And in the process, you burn out your devs, and have constant churn. How late are things happening in the long term, because teams prioritize the Agile rituals over cultivating long term technical excellence, craftsmanship, and team satisfaction? The way many teams practice Agile has a huge opportunity cost that's very difficult to measure, but still real.