I was a big believer 15 years ago, then became heavily disillusioned, and now have a pretty pragmatic view of it. It can help, if you don't know what you're doi

I was a big believer 15 years ago, then became heavily disillusioned, and now have a pretty pragmatic view of it. It can help, if you don't know what you're doing at all it's a good framework to start. I feel like the Kanban approach where the team takes ownership of their process is a good one. There's a lot of great stuff in there about communicating as a team, and thinking about the customer. Too often though in practice it devolves into a kind of cargo cult and the apologists lean way too hard into the "if it isn't working, you must not have believed in it hard enough" defense which is a bit too easy in my opinion. It short circuits any actual reflection and learning. Basically, the agile manifesto is great.. the stuff agile coaches try to sell you is hot garbage. Everything else is somewhere in the middle, but Kanban is the closest because it preserves the "we are uncovering" part of the manifesto.