SOFTWARE DEVELOPEMENT IN THE NEW AGE
According to the Wikipedia article on Agile Software Development: Agile software development is a group of software development methods in which requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development, early
delivery, continuous improvement and encourages rapid and flexible
response to change.
The Agile Manifesto
In February 2001, 17 software developers met at the Snowbird resort in Utah to discuss lightweight development methods. They published the Manifesto for Agile Software Development.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
The meanings of the manifesto items on the left within the agile software development context are:
- Individuals and interactions: in agile development, self-organization and motivation are important, as are interactions like co-location and pair programming.
- Working software: working software will be more useful and welcome than just presenting documents to clients in meetings.
- Customer collaboration: requirements cannot be fully collected at the beginning of the software development cycle, therefore continuous customer or stakeholder involvement is very important.
- Responding to change: agile development is focused on quick responses to change and continuous development.[6]
The Agile movement is not anti-methodology, in fact many of us want to restore credibility to the word methodology.
- We want to restore a balance.
- We embrace modeling, but not in order to file some diagram in a dusty corporate repository.
- We embrace documentation, but not hundreds of pages of never-maintained and rarely-used tomes.
- We plan, but recognize the limits of planning in a turbulent environment.
- Those who
would brand proponents of XP or SCRUM or any of the other Agile
Methodologies as "hackers" are ignorant of both the methodologies and
the original definition of the term hacker.
Agile principles
The Agile Manifesto is based on 12 principles:
- Customer satisfaction by rapid delivery of useful software
- Welcome changing requirements, even late in development
- Working software is delivered frequently (weeks rather than months)
- Close, daily cooperation between business people and developers
- Projects are built around motivated individuals, who should be trusted
- Face-to-face conversation is the best form of communication (co-location)
- Working software is the principal measure of progress
- Sustainable development, able to maintain a constant pace
- Continuous attention to technical excellence and good design
- Simplicity—the art of maximizing the amount of work not done—is essential
- Self-organizing teams
- Regular adaptation to changing circumstances
Author: SkillzAlonge <Agiletechies>
