Danger: Agile Practices at Work

There’s a lot of activity and promotion of the Agile software methodologies that can be found on both the Internet and in books today. Its adherents are zealous in their commitment to the Agile principles codified in the principles behind the Agile Manifesto. I first became interested in the Agile development practices when the Extreme Programming practices began generating a lot of interest in the software community. My first reaction to this was to be turned off. The name conjured up images of chaos, cowboy programmers, and death march development projects — practices I am all too familiar with. I found the advocacy of pair programming to be unnatural and impractical.
After reading many articles published by Agile proponents, I remain steadfast in my beliefs that something is wrong, and rather than advancing the state of the art practices in Software Development, Agile proponents are setting us back, and in this world where jobs easily cross international boarders, especially easy in software, we need practices that demonstrate the value proposition for keeping teams here in the US: practices that deliver reliably and predictably on commitments and practices that can demonstrate improvements in productivity and quality.



