Skip to main content

Due to the Russian invasion of Ukraine, we have paused all purchases and training in and from Russia.

What practices emerged out of the 12 Agile Principles?

Last post 09:20 am May 30, 2017 by Balachandra sekhar Manchikanti
No replies yet
09:20 am May 30, 2017

We have 12 agile principles stated in the agile manifesto. We should be appreciating the way these principles made an impact on a lot of practices that emerged changing the entire world of building software. Appreciate if you can map the principles to emerged practices.

  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.


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.