12 Basic Principles That Underlie The Agile Manifesto With Text From Original Manifesto

Here is the simplified 12 points version of Agile Manifesto for Software Development

  1. Customer satisfaction by rapid delivery of useful software
  2. Welcome changing requirements, even late in development
  3. Working software is delivered frequently (weeks rather than months)
  4. Working software is the principal measure of progress
  5. Sustainable development, able to maintain a constant pace
  6. Close, daily co-operation between business people and developers
  7. Face-to-face conversation is the best form of communication (co-location)
  8. Projects are built around motivated individuals, who should be trusted
  9. Continuous attention to technical excellence and good design
  10. Simplicity
  11. Self-organizing teams
  12. Regular adaptation to changing circumstances

(Source: Wikipedia/Creative Commons)

The Original Manifesto Text is listed below.

  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 customer’s competitive advantage.
  3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
  4. Business people and developers must work together daily throughout the project.
  5. Build projects around motivated individuals. Give them the environment and support they 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–the art of maximizing the amount of work not done–is essential.
  11. The best architectures, requirements, and designs 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.
  1. Pair Programming – A Comprehensive Guide To Get You Going
  2. Why The Idea Of Test Driven Development (TDD) Royally Upsets Me
  3. 12 Basic Principles That Underlie The Agile Manifesto With Text From Original Manifesto
  4. 12 Practices That Make Up Extreme Programming In Agile Software Development Methodology
  5. 15 Agile Best Practices – Are you following these in your team?
  6. What is the format for writing an agile story card?
  7. How the Agile Teams and Organizations Mature and Become Fluent
  8. N-Things You Can Do With Continuous Integration Tools Hudson and Jenkins
  9. List of some popular agile methodologies of software development practices
  10. The chicken and pig cartoon for Agile Project Management – high resolution version recreated
  11. Why is Fibonacci series numbers used in Agile Planning and Estimations?
  12. What Makes An Agile Story Good? It’s the INVESTment.
  13. Roles and Responsibilities of Business Product Owner in Agile Teams
  14. 100 Plus Agile Terms – A Comprehensive List
  15. 15 plus best practices for continuous integration of your software
  16. Iterative development benefits in the Agile software development
Tagged , , , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *