MANIFESTO
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.
Principle 1
OUR HIGHEST PRIORITY IS TO SATISFY OUR CUSTOMER THROUGH EARLY AND CONTINUOUS DELIVERY
Principle 2
WELCOME CHANGING REQUIREMENTS, EVEN LATE IN DEVELOPMENT. AGILE PROCESSES HARNESS CHANGE FOR CUSTOMER’S COMPETITIVE ADVANTAGE
Principle 3
DELIVER WORKING SOFTWARE FREQUENTLY, FROM A COUPLE OF WEEKS TO A COUPLE OF MONTHS, WITH A PREFERENCE TO THE SHORTER TIMESCALE
Principle 4
BUSINESS PEOPLE AND DEVELOPERS MUST WORK TOGETHER DAILY THROUGHOUT THE PROJECT
Principle 5
BUILD PROJECTS AROUND MOTIVATED INDIVIDUALS. GIVE THEM THE ENVIRONMENT AND SUPPORT THEY NEED, AND TRUST THEM TO GET THE JOB DONE
Principle 6
THE MOST EFFICIENT WAY AND EFFECTIVE METHOD OF CONVEYING INFORMATION TO AND WITHIN A DEVELOPMENT TEAM IS FACE-TO-FACE CONVERSATION
Principle 7
WORKING SOFTWARE IS A PRIMARY MEASURE OF PROGRESS
Principle 8
AGILE PROCESSES PROMOTE SUSTAINABLE DEVELOPMENT. THE SPONSORS, DEVELOPERS, AND USERS SHOULD BE ABLE TO MAINTAIN A CONSTANT PACE INDEFINETELY
Principle 9
CONTINUOUS ATTENTION TO TECHNICAL EXCELLENCE AND GOOD DESIGN ENHANCES AGILITY
Principle 10
SIMPLICITY -THE ART OF MAXIMIZING THE AMOUNT OF WORK NOT DONE- IS ESSENTIAL
Principle 11
THE BEST ARCHITECTURES, REQUIREMENTS, AND DESIGNS EMERGE FROM SELF-ORGANIZING TEAMS
Principle 12
AT REGULAR INTERVALS, THE TEAM REFLECTS ON HOW TO BECOME MORE EFFECTIVE, THEN TUNES AND ADJUSTS ITS BEHAVIOR ACCORDINGLY
