Systems Analysis| Agile Methodology | A Short Story| Dan Burns 1/23/2010 | 1/23/2010 Agile Methodology The Paper Basically what I have been able to relate too is that Agile Methodology is a process of small groups of people (teams) that are located in the same place working together. They communicate either through e-mail, voice mail, or direct contact. There is little documentation because of the closeness of the team, it’s easier to communicate because of the in your face communication-though, in an agile project, documentation and other artifacts rank equally with a working product.
This way of communicating gets projects moving along a lot faster. Their due dates are in a matter of weeks, because their packages of product are small, so they have usable product faster and results are faster in shorter amounts of time. They also have the flexibility of change a lot easier because of the small packages of product. Team composition in an agile project is usually cross-functional and self-organizing without consideration for any existing corporate hierarchy or the corporate roles of team members. Team members normally take responsibility for tasks that deliver the functionality an iteration requires.
They decide individually how to meet iteration’s requirements. Suitability of Agile There is little if any consensus on what types of software projects are best suited for the agile approach. Many large organizations have difficulty bridging the gap between the traditional waterfall method and an agile one. Large scale agile software development remains an active research area. History The modern definition of agile software development evolved in the mid-1990s as part of a reaction against “heavyweight” methods, perceived to be typified by a heavily regulated, regimented, micro-managed use of the waterfall model of development.
The processes originating from this use of the waterfall model were seen as bureaucratic, slow, demeaning, and inconsistent with the ways that software developers actually perform effective work. A case can be made that agile and iterative development methods mark a return to development practice from early in the history of software development. Initially, agile methods were called “lightweight methods. ” Agile methods include Scrum (1995), Crystal Clear, Extreme Programming (1996), Adaptive Software Development, Feature Driven Development, and Dynamic Systems Development Method (DSDM) (1995).
These are now typically referred to as Agile Methodologies, after the Agile Manifesto published in 2001. An adaptive software development process was introduced in a paper by Edmonds (1974). Notable early In 2001, 17 prominent figures in the field of agile development (then called “light-weight methods”) came together at the Snowbird ski resort in Utah to discuss ways of creating software in a lighter, faster, more people-centric way.
They coined the terms “Agile Software Development” and “agile methods”, and they created the Agile Manifesto, widely regarded as the canonical definition of agile development and accompanying agile principles. Later, some of these people formed The Agile Alliance, a non-profit organization that promotes agile development. Principles Agile methods are a family of development processes, not a single approach to software development. The Agile Manifesto states: We are uncovering better ways of developing software by doing it and helping others do it.
Through this work we have come to value: * Individuals and interactions over processes and tools * Working software over comprehensive documentation * Customer collaboration over contract negotiation * Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. Some of the principles behind the Agile Manifesto are: * Customer satisfaction by rapid, continuous delivery of useful software * Working software is delivered frequently (weeks rather than months) * Working software is the principal measure of progress Even late changes in requirements are welcomed * Close, daily cooperation between business people and developers * Face-to-face conversation is the best form of communication (co-location) * Projects are built around motivated individuals, who should be trusted * Continuous attention to technical excellence and good design * Simplicity * Self-organizing teams * Regular adaptation to changing circumstances The manifesto spawned a movement in the software industry known as agile software development. Criticism
From what I understand, the big thing that is disliked is the lack of documentation for projects. Another belief is that you need very good programmers, analysts, managers to get great results. The last thing is that some think that huge projects that could span over many areas or countries might lose integrity because of not being close together or in the same place, being that the face to face concept would be lost. In Conclusion I know this has been brief, I find that for me it seems vague the concept of developing software as it is explained in the articles I read.
I’m a hands on kind of person; I need to see the process in action so I have something to relate to. I’m sure you will help with this process. I kind of get this approach; I also kind of understand the Waterfall approach, so there is hope for me. This is all new to me I worked in a shop in my own little world for years not ever looking out in the great wide open of the computer world. I look forward to learning. Cited Page http://en. wikipedia. org/wiki/Agile_software_development http://pm. versionone. com/AgilePoster. html http://www. versionone. com/products_V1Enterprise_Overview. asp