I really wanted to agree with you, but your comment is mostly criticizing people doing agile without understanding it. And yet, you 3 points prove that you don

I really wanted to agree with you, but your comment is mostly criticizing people doing agile without understanding it. And yet, you 3 points prove that you don't understand agile either. If feels like a bad driver honking at other cars. All the points you cite are useful, but they are nowhere what agile is. The most important thing about agile is __the emphasis on communication and a short feedback loop__. You deliver things in small testable chunks because it's easier to ochestrate a team around that, and you get feedback sooner. You refine weekly based on how things went because you can thanks to the regular feedback you get. You let others know ASAP because you have regular communication. You are making the same mistake as everybody: thinking agile is about a process, and hence, rules. It's not. Agile is a set of principles, which then you use to implement whatever rules and so, process, you need for your current situation. SCRUM is one way, XP is another. Your agile and mine won't be the same. Mine today won't be the same as the one tomorrow. Because what matters is communication and short feedback loops, and there are many ways to get that. Sure, you can use proven tools and receipes. It's good. We all do it. But it's no more agile that using a good knife is cuisine.