I've said before but I'll repeat: Agile™ was born from web development consultancies as a defensive process for managing bad clients. A lot of the process wil

I've said before but I'll repeat: Agile™ was born from web development consultancies as a defensive process for managing bad clients. A lot of the process will make sense if you think about it in terms of business stakeholders eventually suing you. You want to make sure every decision is documented, never commit to a firm timeline, produce artifacts of work at a super granular cadence, and make sure to give stakeholders the illusion of control. It's not a good way to make software but it is a consistent way to make software. This makes it attractive to large non-tech businesses because it means that they can effectively reason about and plan software development at a high level. They'll never be super fast in delivering that product but for most of these companies that doesn't matter. Their moat isn't their technology - it's something else and they just need the software to work well enough to facilitate the actual business processes that are their moat.