Agile Excuses - Introduction
In a recent post, I mentioned that South African companies are reluctant to adopt Agile Software Development practices and methodologies, their reasons often entertaining.
I have stumbled across an article entitled The Agile Method and Other Fairy Tales. In an upcoming blog series, I'm going to rebut some of the arguments that the author puts forward in this paper, amongst some other arguments that I've heard.
To stimulate your appetite a bit, here is the conclusion of The Agile Method and Other Fairy Tales. I hope that it entertains.
Agile proponents believe software development is unique from all other industries. They believe there is nothing to be learned from other disciplines like music, library science, medicine or architecture. Like most individuals in a crunch they default back to a position of comfort. For software developers this is coding. It is not about the code it is about creating products that customers can use.
Agile proponents argue against structured methods because it enforces accountability. Too many software developers want to be left alone so they can code. They want to run free and not be under any rule. They avoid accountability, management, or the idea of reining in costs.
Agile proponents discourage documentation. The software industry does not have reputation of being great communicators or organizers. Instead of trying to improve communication skills, they abandon the idea of communication. It is not possible for large groups of individuals to communicate without structured documentation. Agile proponents discourage a division of labor and argue all software roles are interchangeable.
Agile proponents are the leaders of a dysfunctional industry. They honestly believe no other industry or person can provide good requirements. They also believe nothing can be learned from other industries. It is not the software industry that needs to change, but everyone else.
Related posts: