Agile Principles

The Agile Manifesto contains a set of 12 principles that explain agility and complement the Agile Manifesto.

What is Agile Principles

There are 12 principles behind the Agile Manifesto including:
  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.

Top related courses to Agile Principles

Related methods and techniques to Agile Principles

  • Customer Satisfaction

    1. Customer Satisfaction

    Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

  • Welcome change

    2. Welcome change

    Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage

  • Deliver frequently

    3. Deliver frequently

    Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

  • Working together

    4. Working together

    Business people and developers must work together daily throughout the project.

  • Motivated Team

    5. Motivated Team

    Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

  • Face-to-face conversation

    6. Face-to-face conversation

    The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

  • Working software

    7. Working software

    Working software is the primary measure of progress.

  • Constant pace

    8. Constant pace

    Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

  • Technical excellence & Good design

    9. Technical excellence & Good design

    Continuous attention to technical excellence and good design enhances agility.

  • Simplicity

    10. Simplicity

    Simplicity--the art of maximizing the amount of work not done--is essential.

  • Self-organizing teams

    11. Self-organizing teams

    The best architectures, requirements, and designs emerge from self-organizing teams.

  • Reflect and adjust

    12. Reflect and adjust

    At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.