Warning: Illegal string offset 'title' in /usr/www/users/playsn/pibold/wp-content/plugins/table-of-content/plugin.php on line 48
Warning: Cannot assign an empty string to a string offset in /usr/www/users/playsn/pibold/wp-content/plugins/table-of-content/plugin.php on line 48
Warning: Illegal string offset 'title-tag' in /usr/www/users/playsn/pibold/wp-content/plugins/table-of-content/plugin.php on line 50
Warning: Illegal string offset 'title-tag' in /usr/www/users/playsn/pibold/wp-content/plugins/table-of-content/plugin.php on line 52
The Agile Manifesto was published in 2001 by Kent Beck, Alistair Cockburn, Ward Cunningham, Martin Fowler and others. Within 4 values and 12 principles it charters the fundamental values of agile software development.
The four Values
[Top]
- Individuals and interactions over processes and tools.
- Working software over comprehensive documentation.
- Customer collaboration over contract negotiation.
- Responding to change over following a plan.
The twelve Principles
[Top]
- “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.”
- “Welcome 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 the shorter timescale.”
- “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 doneis essential..”
- “The best architectures, requirements, and designs emerge from self organizing teams.”
- “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.”
Further Readings
[Top]
- http://www.agilemanifesto.org/
Leave a Reply