12 Principles of Agile Methodology

Revision as of 17:02, 28 May 2018 by Rasimsen (talk | contribs) (Created page with " The Agile Manifesto lists [http://agilemanifesto.org/principles.html 12 principles] to guide teams on how to execute with agility. These are the principles: *Our highest pri...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The Agile Manifesto lists 12 principles to guide teams on how to execute with agility. These are the principles:

  • 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 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 done -- is 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.