I can't grant you humility from the Agile community, or even necessarily from myself, but I can clarify what problems it works well for and doesn't, dangers, et

I can't grant you humility from the Agile community, or even necessarily from myself, but I can clarify what problems it works well for and doesn't, dangers, etc. Agile works well when organizational leaders are willing to invest in changing the constraints of their organization, and team members are similarly willing to work to customize the philosophy—'cause that's all it is, a way of thinking about software development—to their specific situation. Given those two things, I've yet to find a type of software development where Agile didn't work. People have used its ideas for web development, embedded systems development, back-end, front-end, Java, C++, JavaScript, etc. etc. But those two things can be really really hard, which is why I think cargo-cult Agile is so common. And trying to be Agile without them is dangerous, in that it can easily be worse than whatever it replaced. I talk about them more in chapters 4 and 5 of the book. You can find an excerpt of chapter 4, including a list of the investments needed, here: https://www.jamesshore.com/v2/books/aoad2/invest_in_agility https://www.jamesshore.com/v2/books/aoad2/invest_in_agility