Manifesto for Agile Software Development
Individuals and interactions over processes and tools
building the team is more important thant building the environment.
Working software over comprehensive documentation
Produce no document unless its need it immediate and significant.
Customer collaboration > contract negotiation
Successful projects involve customer feedback on a regular and frequent basis.
Responding to change > following a plan
detailed plans for the next week;rough plans for the next 3 months;extremely crude plans beyond that .
12 Principles
1.Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
2.Welcome changing requirements,even late in development.Agile processes harness change for the customers's competitive advantage.
3.Deliver working software frequently,from a couple of weeks to a couple of months,with a preference to the shorter time scale.
4.Businesspeople and developers must work together daily throughout the project.
5.Build projects around motivated individuals.Give them the environment and suport the need,and trust them to get the job done.
6.The most efficient and effective method of conveying information to and within a development team is face -to -face conversation.
7.Working software is the primary measure of progress.
8.Agile processes promote sustainable development.The sponsors,developers,and users should be able to maintain a constant pace indefinitely.
9.Continuous attention to technical excellence and good design enhances agility.
10.Simplicity - is essential
11Ghe best architectures,requirements,and desighs emerge from self-organizing teams.
12 At regular intervals,the team reflects on how to become more effective,then tunes and adjusts its behavior accordingly.
agile processes
SCRUM,
Crystal,
FDD,feature-driven development
ADP,adaptive software developement
XP Extreme Programming.
