Agile software development approach.
Agile software development is a set of software development methodologies based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams.
There is no owner of Agile as such. The Agile Manifesto is owned by the authors. They are mentioned on the agilemanifesto.org site.
Incremental software development methods have been traced back to 1957. ”Lightweight’ software development methods evolved in the mid-1990s as a reaction against ‘heavyweight’ methods, which were characterized by their critics as a heavily regulated, regimented, micromanaged, waterfall model of development. Supporters of lightweight methods (and now agile methods) contend that they are a return to earlier practices in software development.
Early implementations of lightweight methods include Scrum (1993), Crystal Clear, Extreme Programming (1996), Adaptive Software Development, Feature Driven Development, and Dynamic Systems Development Method (1995). These are now typically referred to as Agile methodologies, after the Agile Manifesto.
The Agile Manifesto was written in February 2001, at a summit of independent-minded practitioners of several programming methodologies.
Manifesto for Agile Software Development
We are uncovering better ways of developing
Individuals and interactions over processes and tools
That is, while there is value in the items on
Anyone involved in an Agile software development project team; including analysts, architects, developers, testers and business customer/users; anyone supporting or managing an Agile project team who requires a detailed understanding of the practices and benefits of Agile software development. The Agile alliance is an independent organization that supports individuals and organizations that explore and apply Agile principles and practices.
There are many Agile User Groups, Forums and Discussion Threads. The best way to explore them is to start at the Agile alliance “Community Groups” page.
There is no official publisher for Agile. If you are looking for publications you can check the “Books” on the Agile Alliance site. Member-submitted reviews of various publications can be found there, including links to book shops.
There are no officially endorsed certification programs for Agile. The Agile alliance has published a statement on certification on their site. The following excerpt is the introduction to the statement.
|Agile Certification: A Position Statement A Position Statement from the Agile Alliance Board on Agile Certification Portland, Oregon, April 6, 2010 — Now that Agile software development is becoming a mainstream practice, more and more employers need to staff teams that will perform it well. How can they know if a particular person will be an asset? One way might be to favor employees who are vouched for by some certification body. It is the position of the board of the Agile Alliance that employers should have confidence only in certifications that are skill-based and difficult to achieve. (source agilealliance.org)|
|Official Sites||The Agile Alliance home page|
|User groups and communities||Agile Alliance community-groups|
|Publications||Agile Alliance resources|
|Accreditations and Qualifications||Agile certification position statement|
|Other useful links||the Agile manifesto|
|FREE IBPI documents||Whitepapers|