Agile #
I do not know what Agile is, on software development, I really do not know. Most of the times it seems a good idea, to me, which, unfortunately, was transformed in a buzzword that no one knows what it really means. Every time I talk with someone about Agile I feel we are talking about different things and no one is talking about the initial (or not) Agile Manifesto. For example, rarely I hear someone mentioning continuous integration and delivery, test driven development or refactoring disciplines, but I often hear about estimations, burn down charts, jiras, and so on.
The main frustration, for me, is when I hear someone using the Agile term as an excuse for chaos, when you show your frustration for the lack of vision in a project and someone jokes "tt is Agile" (I have been there, as well).
With that, I just wanted to write down, an interesting sentence I have just read at Software Architecture Elevator:
"...the method is called 'Agile,' not 'fast,' and for good reason. Agile methods are about hitting the right target through frequent recalibration and embracing change rather than trying to predict the environment and eliminating uncertainty. Firing from afar at a moving target is fast, but not Agile: you will likely miss. Agile methods allow course corrections along the way, more like a guided missile. Agile quickly gets you where you need to be. Running in the wrong direction faster is not a method, but foolishness."
Published