@juanpabloamorochod.752

I have so much to say about this... "agile fails" when an organization finds the status quo perfectly fine, think Kodak or Nokia."Agile fails" if an organization does not have the right people in sitting in the right place doing the right thing. "Agile fails" if an organization cannot navigate through uncertainty in the market, if it is not able to anticipate and react change, again think Kodak or Nokia. "Agile fails" because agile product development is hard, very hard, again without the right people, sitting in the right place, ... you get the point. But also "agile fails" because of bad luck. There, I should stop ranting.

@juanpabloamorochod.752

I can't say that I disagree with everything you said, but being a SWE and working for a sucessful organization that develops software in an agile way, I part ways with your argument. First, agile is not something, it is how to do something. It is not something one can buy like consulants and certifications, sure learning and getting help can help getting into that agile mindset, but boy does business gets the original manifesto wrong,  and that has created a lot of harm like in the BBC or FBI. Yes, of course trying to achieve working in an agile way fails because of Culture, because in business Culture is everything. I think "agile fails" because of business retries to replicate and scale. A parallel to this  "failure", it is a failure at all, is this: The motivition people have to start meditating, seek more awareness, less stress, healthier lifes, when actually Meditation is about recognizing that there is no concept of Self: That which we perceive as "I" is actually Conciousness. That's why "meditation fails". Agile software development is about delivering better sofware faster. As long as organizations do not recognize the nature and purpose of agile product development, they will fail to embrace it.