Agile Manifesto
Uncovering better ways of developing software by doing it and helping others to do it. To achieve:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Principles
· Highest priority is to satisfy the customer through early and continuous delivery of valuable software.
· Welcoming changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
· Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to shorter time scales.
· Business people and developers must work together daily throughout the project.
· Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
· The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Working software is the primary measure of progress.
· Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
· Continuous attention to technical excellence and good design enhances agility.
· Simplicity – the art of maximizing the amount of work not done- is essential.
· The best architectures, requirements, and designs emerge from selforganized teams.
· At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Agile Methods
The number of methods that claim to align the Agile Manifesto will continue to grow with the popularity of the agile software methodologies. The early initial methodologies include:
1. Extreme Programming
2. SCRUM
3. Crystal
4. Feature Driven Development
5. Lean Development
6. Adaptive Software Development
7. DSDM
