I think that battle is lost, unfortunately :( In every single team I've ever been a part of, Agile is used exclusively in the Scrumfall sense (I didn't come up

I think that battle is lost, unfortunately :( In every single team I've ever been a part of, Agile is used exclusively in the Scrumfall sense (I didn't come up with that second term either; it's just what the post-Agile blogosphere calls it). When I point out that, done this way, it goes against the entire philosophy of the original Agile Manifesto... I just get shrugs. People don't care what it used to mean; when they say it now, they mean the points and ceremonies and masters and the whole ugly shebang. It's not a battle I have the energy to fight. When a workflow isn't like that, but is just lean & simple on its own, they don't go out of their way to call it Agile or agile, uppercase or lowercase. It's just "a simple workflow" or something like that, or else some explicit other workflow (like Shape Up). I think a lot of folks have been burnt out by Scrumfall and try to practice alternatives. I've made a point to start asking potential employers how they handle project management. If they say Agile of any sort, I'll assume the worst and just walk away...