Agile Software Concepts

Fitting the process to the product, rather than obeying protocols to the letter. Focusing not on strict methodology and but of the needs of the overall work ecosystem. Adopting a "chaordic perspective" that accepts the increasing levels of unpredictability in a turbulent and capitalist-driven software marketplace. Adopting collaborative values and principles when creating software, rather than proceeding in a linear fashion. Showing pride when having a "barely sufficient methodology" at the beginning of a project -- after all, one never knows where a project may lead. All of these are principles of Agile Software development. (Highsmith, 2002)

At the heart of these principles, is the idea of a focus on individuality during development rather than predictable steps and end results. "While goals are achievable, project details are often unpredictable." Approaches that focus purely on repeatable processes, rather than individual needs is often unrealistic, suggest Agile developers. (Highsmith, 2002) The mutual collaboration at the heart of Agile organizations focuses "on building individual skills and on fostering a high degree of interaction among team members and the project's customers. Agilists believe that with today's complex projects, understanding comes more from face-to-face interaction than from documentation. Agilists do not believe that a reliance on heavy processes makes up for lack of skill, talent, and knowledge. Strict methodology is often not useful as organizations will have different answers for different stages in their evolution and for different projects in their portfolio." (Highsmith, 2002)

This stress upon teamwork, adoption, and agile adaptation are often harmonious with current corporate values and stress upon team and work projects. It is a people pleasing or manager pleasing systems of working. However, the downside is, with insufficient adherence to detail in the methodology, costs can override concerns such as systems security, that do not seem important in the 'process' of the moment, but can be costly later on to both company, developer, and employees in terms of time and money.

Work Cited

Highsmith, Jim. (Oct 2002) "What is Agile Software Development?" Crosstalk. Retrieved 24 Feb 2005 at http://www.stsc.hill.af.mil/crosstalk/2002/10/highsmith.html