Agile Manifest was formed in 2001 in snowbird utah resort by 17 Agile Enthusiast who were experimenting with Software Engineering - and Developments practices: Kent BeckMike BeedleArie van BennekumAlistair CockburnWard CunninghamMartin FowlerJames GrenningJim HighsmithAndrew HuntRon JeffriesJon KernBrian MarickRobert C. MartinSteve MellorKen SchwaberJeff SutherlandDave ThomasAgile Manifesto Authors Above authors and many agile enthusiast singed Agile Manifesto Values and Principals that are guiding us since than: We are uncovering better ways of developingsoftware by doing it and helping others do it.Through this work we have come to value: Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan That is, while there is value in the items onthe right, we value the items on the left more Principles behind the Agile Manifesto We follow these principles: Our highest priority is to satisfy the customerthrough early and continuous deliveryof valuable software. Welcome changing requirements, even late indevelopment. Agile processes harness change forthe customer's competitive advantage. Deliver working software frequently, from acouple of weeks to a couple of months, with apreference to the shorter timescale. Business people and developers must worktogether 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 ofconveying information to and within a developmentteam 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 ableto maintain a constant pace indefinitely. Continuous attention to technical excellenceand good design enhances agility. Simplicity--the art of maximizing the amountof work not done--is essential. The best architectures, requirements, and designsemerge from self-organizing teams. At regular intervals, the team reflects on howto become more effective, then tunes and adjustsits behavior accordingly.